Hi there,

So I made a ventoy usb, with a couple of ISO, I tried this out on a VM and it seemed to work fine. But when I try on on my physical pc it is just glitched. Look at the top of the screen, this happens after I selected in boot menu the ventoy drive. I dont know how to fix. My specs are: MoBo: MSI Z690-P, i7 12700k, 32GB RAM, MSI RTX 3080TI.

We look forward to your contributions (members) to maintain and develop ventoy more and more.

I followed the instructions for adding a virtualbox machine as vtoy. This is amazing. It does not work in UEFi either but it works splendidly on legacy. I have to wonder if there is a need for linux systems with persistence anymore. I guess if you are cramped for space.

Any thoughts?

Hi, 

Just wondering if anyone has tried using Ventoy to boot the iPXE image? It supports a large range of image options but so far, I haven't had much luck with EFI or USB images to boot without failing and looping back to Ventoy, I'm only speculating but I'm guessing that it could be due to requiring access to the hardware at a lower level when Ventoy is operating out of that already?  

Ideally, I'd prefer to stay in the UFI space without having to manually reconfigure bios etc. 

I've gotten the ISO to boot previously but manually adding the script into the ISO means it isn't dynamic anymore and would need a hard coded script to chainload etc. 

Index of / (ipxe.org)

https://ipxe.org/

Anyway thanks!

i tried updated version 1.0.81, version 1.0.80, version 1.0.79, it break the UEFI detection in boot menu to select boot from UEFI for ventoy drive selection, unable to detect ventoy drive in UEFI mode. in BIOS i already set to UEFI and Legacy, or UEFI only in CSM option, both also unable to detect Ventoy in UEFI selection. Currently falled back to Ventoy version 1.0.45, no issue to boot into UEFI selection in that 2 mode in CSM option. 

I am wondering why the boot process reacted differently in between version 1.0.45 with the recent Ventoy versions.

how to compile ventoy to run on one partition and ventoy and iso

First of all, thanks for releasing this brilliant software/utility - seriously, its exactly what many of us needed.
Now for the problem:

So i have Elementary OS 6.1 installed on a VHD using the latest VirtualBox 6.1
The VHD is 16Gb with a 280 MB EFI and balance Ext4
Ran vtoy shell script and it ran successfully.

OS boots fine and after changing the filename of vhd to *.vhd.vtoy i can copy it to any ventoy usb and boot.

Created vlnk.vtoy to the above vhd saved on my harddisk /SSD (using latest ventioy 1.0.80) and copying that file to any ventoy usb boots the linux vhd from my hard disk.

Added: chainloader (hd0,1)/EFI/vdiskchain vdisk=/VMs/eOS62/eOS62.vhd.vtoy

to grub.cfg using grub-customizer and also by directly typing it on a grub shell or pressing 'e' to edit grub menu during boot.

Now when it boots i get a blank screen. Both vdiskchain & vhd are found and loaded
And on checking the console I can see its not going ahead on:  "loading initial ramdisk ..."

So i ran vtoyboot.sh again. 
Somehow, the grub.cfg on the EFI partition of this VHD shows me different things while the vtoyboot.sh script makes changes in some different grub.cfg

If i run grub-customizer and make some changes then i can see them in grub.cfg but on booting the grub menu that comes up is different (its the one that vtoyboot.sh is editing/creating)

So i have tried a few times to mount the EFI partition and try to see from where the vtoyboot.sh grub.cfg is coming but nothing yet.

Any idea what i should check ?

Versions after 1.7.0 cannot load iso,Where is the problem?

After selecting the ISO and pressing Enter, a black window pops up, and there is no response after a flash.

No problem with 1.7.0

   

Hello,
I always have a mobile hard drive in my luggage when I travel. It contains the most common tools that I may need on a foreign computer: Rescue systems, Windows iso-files, backup system etc.. 
At some point, of course, I replaced the previously used hard disk with a newer one, the new disk has 4TB. And there is my problem: Ventoy always formats the disk in MBR partition style. But that only allows the use of a total of 2TB. Of course you could convert the partition table with various partitioning tools also in GPT to be able to use the full 4TB...but with that Ventoy no longer boots.
Is there a way to use Ventoy on larger disks ?

I still have problems with my usb wireless keyboard not working most times when I boot ventoy in legacy mode. It might work once out of ten tries which is very frustrating. If I boot in UEFI mode the keyboard works every time but I have lots of problems with the files I want to use. Macrium Reflect only works in memdisk mode. many of the iso's just refuse to load. If I choose normal mode I just get a cursor at the top left of the screen and nothing happens. I have tried using a plug in usb keyboard but get the same results. I also have problems with wim files in UEFI also.
Ideal solution for me would be to get the keyboard to work in Legacy. I should also point out that Easy2Boot also has the same problem but I seem to need that less and less.
Any help would be greatly appreciated. I have had this computer for 10 years and this keyboard problem is something that has only started about 2 years ago and only with ventoy/easy2boot.
I was advised before to hold the shift key while booting in easy2boot to load the usb drivers but that does not work either.
I should also mention that there is no bios update for my motherboard, but like I said I never had these problems until lately.

This is what happens when I try to boot and easy2boot drive with ventoy and agfm.
9 times out of 10 in legacy mode the keyboard will not work once the menu easy2boot menu comes up.
Following advice here i have found a work around but is less than ideal.
when the blue easy2boot screen comes up i hold down thew shift key. [must get the timing right]
at first I get this:

INFO: GRUB4DOS USB 2.0 driver (shift key down)
...scanning usb devices..
Then I get this:
INFO: GRUB4DOS USB 2.0 driver (shift key down)
Error 81 no usb device found. Usb enumeration failed try to restart.
I let go of the shift key and the menu loads.
After all that the keyboard will work.

anyway of fixing that somehow?

I did not mean fixing, i meant some kind of command in a startup file that would automatically do this.

I have found a workaround that I can live with. I hate things that do not work but this will do.

I installed Ventoy on easy2boot as well as AGfm. I now boot easy2boot in legacy mode and do like I said above. Once the menu loads I can go to ventoy an use it no problem.

Bothers me that  cannot get a pure ventoy usb to legacy boot but at least I can do something.

On another note. I followed the instructions for adding a virtualbox machine as vtoy. This is amazing. It does not work in UEFi either but it works splendidly on legacy. I have to wonder if there is a need for linux systems with persistence anymore. I guess if you are cramped for space.
Any thoughts.