I'm having a problem with making 'Parted Magic' to make it ' persistence '. I read about it in E2B and the Ventoy latest guide, I probaly missing some point.it always fails ...
can someone give pointers to make it happen.

with kind regards, wivy

Hello, I have an issue with booting the image.

Quick background information: I received several laptops for testing, 2 Lenovos with AMD CPUs and 1 Lenovo with an Intel CPU. The details are in the attachment .

Now, onto my problem. After opening the iVentoy menu and selecting an image, the process gets stuck. I only see "preparing for boot, please wait."
This phenomenon only occurs with the AMD laptops, the Intel device works fine. The BIOS settings are identical.


In the log, there's nothing unusual, except that it eventually times out.
2023/12/13 14:46:46.803 [TFTP] TFTP RRQ client 172.31.2.41:1423 download <iventoy_loader_16000> start ...
2023/12/13 14:46:46.803 [DHCP] snooping record found 172.31.2.41
2023/12/13 14:46:46.803 [TFTP] DHCP External client 172.31.2.41 should use loader ipxe.x64.ipxe.efi.0
2023/12/13 14:46:46.803 [TFTP] Start send file iventoy_loader_16000 to 172.31.2.41:1423 with blksize 1468, has oack 1
2023/12/13 14:46:46.804 [TFTP] Recv an ERROR opcode pkt from client 172.31.2.41:1423.
2023/12/13 14:46:46.809 [TFTP] Parse tftp option(blksize,1468)
2023/12/13 14:46:46.809 [TFTP] Unsupported tftp option windowsize 4
2023/12/13 14:46:46.809 [TFTP] TFTP RRQ client 172.31.2.41:1424 download <iventoy_loader_16000> start ...
2023/12/13 14:46:46.809 [DHCP] snooping record found 172.31.2.41
2023/12/13 14:46:46.809 [TFTP] DHCP External client 172.31.2.41 should use loader ipxe.x64.ipxe.efi.0
2023/12/13 14:46:46.809 [TFTP] Start send file iventoy_loader_16000 to 172.31.2.41:1424 with blksize 1468, has oack 1
2023/12/13 14:46:47.074 [TFTP] Finished send file to 172.31.2.41:1424 with blksize 1468 blks 767
2023/12/13 14:46:53.354 [DHCP] Snooping 74-5d-22-9d-42-fc MSG:<DISCOVER> ARCH:<EFI BC> 0x1237860
2023/12/13 14:46:53.372 [DHCP] Snooping 74-5d-22-9d-42-fc MSG:<REQUEST> ARCH:<EFI BC> 0x1237860
2023/12/13 14:46:54.282 [HTTP] DHCP external  mode notify discovery client 172.31.2.41 ipxe/01-74-5d-22-9d-42-fc/uefi/mask:255.255.0.0/gw:172.31.64.28/dns:172.31.64.4
2023/12/13 14:46:54.282 [PXE]  Client 74-5d-22-9d-42-fc start PXE install in UEFI X64 mode.
2023/12/13 14:47:06.172 [HTTP] 200 HEAD /viso/id/4/mac:74:5d:22:9d:42:fc/busCI:01:10:ec:81:68/auto:1 size 2453321728
2023/12/13 14:48:01.808 [HTTP] Client 172.31.2.41:33754 (74) read timeout (close), state=0
2023/12/13 14:48:06.176 [HTTP] Client 172.31.2.41:5089 (75) read timeout (close), state=0

Additionally, I have an HP laptop with an AMD CPU where the iVentoy system works perfectly fine.

I hope you can help me and If you need more information, please let me know.

Attached Files

Thumbnail(s)
       

I already set external dhcp server in iventoy configuraton but I don't see options to set next-server in configuration page.

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.

Gigirock        

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?
  

Attached Files

Thumbnail(s)
   

  ventoy.json.txt (Size: 428 bytes / Downloads: 4)
  grub_fedora.cfg.txt (Size: 1.31 KB / Downloads: 4)

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.

Attached Files

Thumbnail(s)
   

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.

iVentoy PXE allows FATDOG v9xx to boot to desktop.

Might want to add this to the list of tested distros tested.

P.S. These versions ALSO boots via Ventoy as well as via iVentoy.

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.

Any help would be appreciated.

Is anyone able to boot a FreeBSD 14.0 ISO successfully?

It looks as though there is a problem using the latest release. FreeBSD starts to boot, but then stops. 13.1 and 13.2 booted OK.