Open sitolam opened 2 years ago
Did you use fixed size vdi type or dynamic size vdi type? Ventoy only support fixed size vdi type. That is to say, if you create a 16GB virtual disk in the VM then the vdi file must be exactly 16GB size.
You can compress and share me the vdi file for analyze
Did you use fixed size vdi type or dynamic size vdi type? Ventoy only support fixed size vdi type. That is to say, if you create a 16GB virtual disk in the VM then the vdi file must be exactly 16GB size.
You can compress and share me the vdi file for analyze
I used fixed size. My vdi file is 400gb so that was difficult to forward. So I made a smaller one of 16gb and it worked. I would like to have a vdi file of 400gb how can I solve this? With the 400gb vdi file I already had the vdi file on my ventoy ssd during installation with virtualbox could that be the problem?
It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.
So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.
It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.
So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.
Ok, I will try
It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.
So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.
I have recreated the 400gb vdi file. And when I boot it I get the same error.
It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.
So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.
I have recreated the 400gb vdi file. And when I boot it I get the same error. The vdi file is on my ventoy ssd during the installation of the 400gb vdi file because I don't have enough space on my computer for a 400gb file. At the 16gb it was on my computer. Could that be the problem?
Please do more test for 64GB/100GB/200GB/300GB... to see which is the smallest capacity that get the error.
You don't need to really boot the VM and install OS into it.
Just after you create the vdi file, then you can boot it by Ventoy, because we just want to see that whether it will report the Unsupported vtoy type
error and the content inside the vdi file has no relationship with this error.
Please do more test for 64GB/100GB/200GB/300GB... to see which is the smallest capacity that get the error. You don't need to really boot the VM and install OS into it. Just after you create the vdi file, then you can boot it by Ventoy, because we just want to see that whether it will report the
Unsupported vtoy type
error and the content inside the vdi file has no relationship with this error.
Ok I will try that
I did what you suggested but then even with the 16gb I got the same error message.
That is to say if you create the 16GB vdi file in your local disk and copy to Ventoy, then it boot OK. But if you create the 16GB vdi file in the Ventoy disk, then it boot fail?
Create a new an empty 16GB vdi file in your local disk and copy to Ventoy and boot. If it can boot OK. then compress the two 16GB vdi files and share with me for analyze. The two 16GB vdi files are empy, so they should be very small after compress.
I created the local vdi file and tried to boot it but then I also got the error. Could it be that I need to turn on EFI first? https://mega.nz/file/FopDlTKR#utsN7ShylR2YcvSZTm5fuyj8SZ_N3dNH_DvxFAEnBUchttps://mega.nz/file/0hQDiAYD#Fq3ouzHTgerXdwPuwOqIwpT7jIyQodSIRXLnpRG8SjE
Must I try VHD?
I have the same issue and have tried the following...
Linux Mint - VDI - Fixed - 50GB Linux Mint - VDI - Fixed - 100GB Linux Mint - VDI - Fixed - 200GB Linux Mint - VDI - Fixed - 300GB Linux Mint - VDI - Fixed - 460GB Linux Mint - VDI - Fixed - 920GB
The only ones that booted up were 200GB and lower. Anything above 200GB will not boot. However I was able to created fixed VHD drives and they will work no matter the size it will seem. I was able to make a 920GB VHD which did boot in Ventoy.
There is something wrong with ventoy when it comes to booting large VDI drives.
i have the same problem.400GB
Same issue, 24gb vdi
i also have the same problem. And i made a 35GB VDI and the only difference between it and the 400GB is that the size is different The 35GB VDI boot up successfully
i have the same problem,and i have another error :error disk hd1,1 not found unspported vtoy type unknown.i found i have another disk so the system can recognize it , i unplug the USB flash drive and it is ok.
I have a tiny suspicion that our EFI might be causing this (very likely wrong) Could some of you reply with the EFI version of your device? Can be found in the information page of Ventoy.
For me the issue was on a Macbook Air 2015 which I no longer have, it had UEFI v1.1 with parts of UEFI v2 and no CSM. Maybe the lack of CSM?
The same problem here(archlinux,512gb). any updates?
I encountered the same problem with Ubuntu24 vdi 40G
I think this problem should be documented in Ventoy official website. I encounter exactly the same problem: A 300GB vdi will not boot but a 300GB vhd file can. Even this is a non-fixable bug, it should inform the user in the website.
I have encounted the same issue ,its better to be documented on the website i guess?
遇到了同样的问题,尝试了ubuntu24.04.1、ubuntu20.04、ubuntu20.04.6,都是Unsupported vtoy type
same issue.
The same problem here(archlinux,20gb).
I have an external SSD. That's where I set up Ventoy. I then followed the instructions of linux vdisk but I got this error.