I'm tryting to get started with iVentoy, (familiar with Ventoy and PXE in general) but I do fail PXE booting using a basic config with only one (tried a second) image:
Is it correct that the image path can be empty or "."?
Code:
iPXE 1.0.0+ -- Open Source Network Boot Firmware -- https://ipxe.org
Features: DNS HTTP iSCSI TFTP VLAN SRP AoE EFI Menu
net11: 50:7c:6f:3d:b2:43 using i350 on 0000:6c:00.3 (Ethernet) [open]
[Link:up, TX:0 TXE:1 RX:0 RXE:0]
[TXE: 1 x "Network unreachable (https://ipxe.org/28086090)"]
Configuring (net11 50:7c:6f:3d:b2:43)...... ok
net11: 192.168.223.200/255.255.255.0 gw 192.168.223.1
net11: fe80::527c:6fff:fe3d:b243/64
Next server: 192.168.223.3
Filename: http://192.168.223.3:16000/ipxe/01-50-7c-6f-3d-b2-43
http://192.168.223.3:16000/ipxe/01-50-7c-6f-3d-b2-43... ok
DxeTpm2MeasureBootHandler: PeCoffLoaderGetImageInfo failed! Status = Unsupported
Image path:
"".
01-50-7c-6f-3d-b2-43 : 2749 bytes [script]
http://192.168.223.3:16000/tarfs/loader/logo_1024x768.png... ok
DxeTpm2MeasureBootHandler: PeCoffLoaderGetImageInfo failed! Status = Unsupported
Image path:
"".
The machine PXE-boots ok from a "normal" PXE server via TFTP.
I Need a specialized setup for a single ISO file such that it can automatically boot instantly when a USB drive is connected to any device. It is essential that this process occurs without showing any pre-boot screens, like those provided by Ventoy, to the end user, ensuring a higher level of security and maintaining the privacy of technical system operations.
Iventoy does not start when the iso folder contains the official Linux Mint 21.2 Cinnamon (Edge) Edition distributiv, downloaded from https://linuxmint.com/edition.php?id=310
Windows logs show error 1000 at startup. Linux version has the same problem.
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.
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.
. 
CI:01:10:ec:81:68/auto:1 size 2453321728