I managed to boot iVentoy, but it just refuses to boot any ISO that I have. The screenshot attached is when booting TinyCore-Current.iso. 

In fact, none of the ISO in my list works.

Any ideas?

Attached Files

Thumbnail(s)
       

下载了多个版本的Win7镜像文件放在Ventoy启动盘中尝试去启动，每次启动到Starting Windows界面的时候就卡住不再动了，只能强行按住电源键去关机，再次启动电脑的时候，原Windows10系统会启动检测磁盘文件和修复的任务，其它的镜像文件，像Win10或者Win11或者是Linux和PE的镜像文件都能正常启动起来。

大佬们有什么解决办法吗？

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.

PS :{ "VTOY_DEFAULT_IMAGE": "/iso/myiso.iso" }

this not work

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.

How to make ventoy boot local disk 0 ?

After 30 sec automatic boot  local disk 0.

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: 5)
  grub_fedora.cfg.txt (Size: 1.31 KB / Downloads: 5)