My use case for iVentoy is to manage and install Virtual Machines in my Hyper-V lab configuration. Unfortunately, everything I have tried with these Gen1 Hyper-V machines running a Legacy BIOS have been unsuccessful in booting iVentoy, I believe the issue is with iVentoy but I'm happy to troubleshoot further.
Additionally, I am able to EFI boot my iVentoy configuration on both my Hyper-V Gen2 Lab VMs, and my own personal computer outside of the lab environment is also able to EFI boot.
I've tried numerous options in the configuration, switching to a lower resolution, swapping to CLI - unfortunately does not work.
The iVentoy console is able to see the Hyper-V machine, but is not able to get past HTTP start 200 [/ipxe/01-00-15-5d-01-17-10]
The best description of the error message is " Could not configure console. " which when searching this forum, I did find some references to it with how the solution is compiled or something along those lines and some older devices losing compatibility along the way.
I believe this issue should be repeatable by anyone running Windows 10/11 Pro or above and using the Hyper-V service that is included with the Operating System to simply create a Gen1 Virtual Machine with any specs and attempting to LAN boot (assuming your machine is also bridged to your local network or able to connect to iVentoy depending on your network).
I've attached two screenshots - the machines that are mentioned in the console are both throw-away test Virtual Machines I've created under Hyper-V.
Edit 2: Here are some additional resources and reports I found on the forum of people reporting similar issues, I'd be very happy to assist in troubleshooting here and getting this resolved once and for all. https://forums.ventoy.net/showthread.php?tid=2636
Ventoy 1.0.97 is not working or booting on Dell Latitude 5440 laptops.
Is there any way to add support for new devices in a future update?
I use ventoy daily for work, that is until the latest Dells just came in.
Thank you,
I have installed Ventoy on one of my HDDs. I then partitioned the rest space and can boot different ISOs from Ventoy. So far so good.
Could Ventoy be used to boot a Debian Live Persistent set up?
There are certain aspects in the said page that needs to be addressed. For example,
Quote:We can use:
FAT partition with boot flag,
ext4 partition with label persistence. The label "persistence" is mandatory.
I will have to ask the Wiki editors as to why a FAT partition with boot flag will be a necessity, or whether a FAT partition will be mandatory, or any other partition, like the ext4 partition will also do.
BTW, there is a detailed page in Unix & Linux Stack Exchange with the topic: How to create a Debian live USB with persistence? which is very complex to execute for non-programmers who use computers for purpose other than hard core programming.
I've successfully expanded the DAT file for the persistence of my Linux Mint distro. Before the expansion, everything was working correctly. I used the default caspar-rw 4GB DAT file provided by Ventoy, hosted on an 64GB USB stick. Note that all hardware remained the same in this whole issue.
To do the expansion, I used the "expansion script" provided by Ventoy, targeting the existing DAT file. The expansion took quite a while -- about 30 mins -- as I brought the DAT from 4GB to 24GB. It completed successfully, although I remember there was some warning about "unmatching sectors" or something like that, but then the script prompted me for a final verification, after which it returned a "success" message.
After the expansion, I can boot to Linux Mint, but it immediately crashes to Fallback mode. LM immediately asks if I want to restart the GUI, and if I do, it immediately crashes again to fallback mode. If I keep using fallback mode, I can see that the persistence seems to have retained all my data and programs, but I cannot access basic system settings and the experience is far from ideal.
What's the best course of action here? I don't have any important data in the persistence, so I would be ok with starting from scratch, but I do need a DAT larger than the default ones -- I only wonder if I won't end up in the same situation if I try again the expansion. Is there a way to recover the existing persistence DAT to a working state (I don't have time snapshots unfortunately)? What's the best way to start with a stable, large DAT file targeting Linux Mint?
On Ventoy GHub CI release on 3 April , it always shows ‘‘Alloc magic broken’’ somewhy, but i expect that to install FreeBSD 14.x-STABLE and that Ventoy release is the minimum Ventoy release in order to boot the FreeBSD installer that release in order of that FreeBSD to be installed
for the most part ventoy did work very fine but there is a weird issue and I am unable to track it down further.
If I connect the stick to the computer I created it with the Ventoy volume takes a long time to appear and something USB related is delayed until it's there. For example I pulled the wire from my mic while it was "hanging" and it still showed as connected device until the USB drive was properly recognized. Also the Windows disk management hangs. It takes pretty much the same time every time - about a minute and then working fine as far I can see.
It's only happening to the Ventoy USB stick and only on my main computer. I tried it on a couple of other machines no problem.
I am getting the following events logged in event viewer after connecting the Ventoy stick.
17.04.2024 22:27:51 Der E/A-Vorgang an der logischen Blockadresse "0x773ad288" für den Datenträger "3" (PDO-Name: \Device\0000016c) wurde wiederholt.
17.04.2024 22:28:07 Ein Zurücksetzen auf Gerät "\Device\RaidPort11" wurde ausgegeben.
17.04.2024 22:28:07 Der E/A-Vorgang an der logischen Blockadresse "0x800" für den Datenträger "3" (PDO-Name: \Device\0000016c) wurde wiederholt.
17.04.2024 22:28:21 Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst WSearch erreicht.
17.04.2024 22:28:21 Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst Backupper Service erreicht.
after these it takes additional 20 seconds but then I can use it without a problem
Since I am using ventoy for a long time I cannot really tell when it was the first time. Also it sometimes does not happen. I have absolutely no idea how to troubleshoot further.
Ideas very much appreciated. Thank you
Lol I just found a clue. If I use the safe remove feature in Windows it seems to be fine at the next time. But I don't get these 2 things together. Caching is disabled for the USB sticks aswell. As far I know this was/is only needed if caching for the USB stick is enabled to prevent data loss
