Hi Ventoy users,
I've got some trouble with Ventoy actually using 1.096 version.
I did the usb key as usual in linux using the
Ventoy2Disk.sh
script.
So I boot my pc ( Intel desktop I3 8gb RAM 6th gen with Nvidia graph card ) using UEFI
I try to boot .iso from fixed hardisk 3Tb , from a ext4 partition 100Gb
I try to boot
Debian 12 ( result as first.jpg)
Fedora Worksation 39 ( result as 2nd.jpg )
I think those are simple distros to run , but I can't boot them, as normal copying the two isos on usb key,
they run normally.
I hope my debug will help to improve Ventoy success.
Hi, I'm currently trying to get Fedora running with the persistence plugin.
According to the documentation I need to add "selinux=0" in the boot option, but I can't seem to get it to work.
What I tried so far is to add this live in the boot menu but to no avail.
I also tried to change the boot.cfg using the "Boot Conf Replace" plugin, but I was also unable to get Fedora to run.
I attached the first error that shows up every time I try to boot with persistence.( Error 1.jpg "sh:write error: invalid argument") After that, Fedora tries to continue booting unsuccessfully, showing a bunch more error messages.
I also tried to run Fedora without persistence. This works as intended.
My questions are:
Where am I going wrong?
Have I implemented the "selinux" command wrongly? In the wrong location in the boot.cfg?
Am I using one of the plugins wrongly?
Do I maybe have something backwards to begin with? My understanding is that I boot with persistence, install Fedora as usual and in the future always run from that settings, am I wrong with that?
I have attached my boot.cfg as well as my ventroy.json for further diagnostics.
Unsure if this may be a possible bug, but I seem to have an issue when trying to mount an ISO file using the auto injected VTOYMNT.BAT script that calls HttpDisk.
I am using Hirens Boot CD PE as an example here. The programs for this live in the root of the ISO file, so unless mounted, you cannot use them.
As per the documentation on the iVentoy WinPE page, if I try calling "X:\VTOYMNT.BAT Y", I'm greeted with the error message "HttpDisk: Incorrect function".
Checking the built in help of HttpDisk it looks like using "/mount 0" is for .IMG files and "/mount 1" is for .ISO files. After checking the VTOYMNT.BAT file, it indeed uses "/mount 0" by default. If I edit this file, change to "/mount 1" and call "X:\VTOYMNT.BAT Y" again, the ISO file is successfully mounted and I can browse to the Y: drive.
I have attached an image to help explain the process.
Again, I'm unsure if this is a bug that can be fixed in a new release or if I'm missing something obvious, but it may help someone else out.
Hi,
I have an x86 tablet with a 64-bit processor (Z3735F). it has windows 10 32 bit installed on it.
It can boot 64-bit Linux without problem (USB Ventoy or Rufus).
But impossible to boot windows x64 because the bios has UEFI only ia32 (no legacy or SCM). SO: CPU x64bits but bios in UEFI ia32 bios !!
How to config Ventoy to boot a windows x64? is it even possible ?
Thank you all for your responses.
Hey, all. I think I need to chainload (redirect) from my main iPXE server to iVentoy. Basically, there will be a PXE menu entry on Server #1 which needs to direct to Server #2 running iVentoy. I'm not sure what the syntax should be and what specifically within iVentoy I need to be linking to.
1. Manually create partitions on the disk:
1 ... 200GB
2 ... 100MB
3 ... remaining space
2. Delete partition 2
3. Do a non-destructive install: sudo ./Ventoy2Disk.sh -i -n /dev/sdc
Partition 2 is recreated with a size of roughly 32MB
4. Delete partition 3
5. Create partition 3 for the remaining space