ventoy/pxe

The open source part of iVentoy.

Ventoy

Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files.
With ventoy, you don't need to format the disk over and over, you just need to copy the image files to the USB drive and boot it. You can copy many image files at a time and ventoy will give you a boot menu to select them.
You can also browse ISO/WIM/IMG/VHD(x)/EFI files in local disk and boot them.
x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI and MIPS64EL UEFI are supported in the same way.
Both MBR and GPT partition style are supported in the same way.
Most type of OS supported(Windows/WinPE/Linux/Unix/ChromeOS/Vmware/Xen...)
1200+ ISO files are tested (List). 90%+ distros in distrowatch.com supported (Details).

Official Website: https://www.ventoy.net

Tested OS

Windows
Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, WinPE

Linux
Debian, Ubuntu, CentOS(6/7/8/9), RHEL(6/7/8/9), Deepin, Fedora, Rocky Linux, AlmaLinux, EuroLinux(6/7/8/9), openEuler, OpenAnolis, SLES, openSUSE, MX Linux, Manjaro, Linux Mint, Endless OS, Elementary OS, Solus, Linx, Zorin, antiX, PClinuxOS, Arch, ArcoLinux, ArchLabs, BlackArch, Obarun, Artix Linux, Puppy Linux, Tails, Slax, Kali, Mageia, Slackware, Q4OS, Archman, Gentoo, Pentoo, NixOS, Kylin, openKylin, Ubuntu Kylin, KylinSec, Lubuntu, Xubuntu, Kubuntu, Ubuntu MATE, Ubuntu Budgie, Ubuntu Studio, Bluestar, OpenMandriva, ExTiX, Netrunner, ALT Linux, Nitrux, Peppermint, KDE neon, Linux Lite, Parrot OS, Qubes, Pop OS, ROSA, Void Linux, Star Linux, EndeavourOS, MakuluLinux, Voyager, Feren, ArchBang, LXLE, Knoppix, Calculate Linux, Clear Linux, Pure OS, Oracle Linux, Trident, Septor, Porteus, Devuan, GoboLinux, 4MLinux, Simplicity Linux, Zeroshell, Android-x86, netboot.xyz, Slitaz, SuperGrub2Disk, Proxmox VE, Kaspersky Rescue, SystemRescueCD, MemTest86, MemTest86+, MiniTool Partition Wizard, Parted Magic, veket, Sabayon, Scientific, alpine, ClearOS, CloneZilla, Berry Linux, Trisquel, Ataraxia Linux, Minimal Linux Live, BackBox Linux, Emmabuntüs, ESET SysRescue Live,Nova Linux, AV Linux, RoboLinux, NuTyX, IPFire, SELKS, ZStack, Enso Linux, Security Onion, Network Security Toolkit, Absolute Linux, TinyCore, Springdale Linux, Frost Linux, Shark Linux, LinuxFX, Snail Linux, Astra Linux, Namib Linux, Resilient Linux, Virage Linux, Blackweb Security OS, R-DriveImage, O-O.DiskImage, Macrium, ToOpPy LINUX, GNU Guix, YunoHost, foxclone, siduction, Adelie Linux, Elive, Pardus, CDlinux, AcademiX, Austrumi, Zenwalk, Anarchy, DuZeru, BigLinux, OpenMediaVault, Ubuntu DP, Exe GNU/Linux, 3CX Phone System, KANOTIX, Grml, Karoshi, PrimTux, ArchStrike, CAELinux, Cucumber, Fatdog, ForLEx, Hanthana, Kwort, MiniNo, Redcore, Runtu, Asianux, Clu Linux Live, Uruk, OB2D, BlueOnyx, Finnix, HamoniKR, Parabola, LinHES, LinuxConsole, BEE free, Untangle, Pearl, Thinstation, TurnKey, tuxtrans, Neptune, HefftorLinux, GeckoLinux, Mabox Linux, Zentyal, Maui, Reborn OS, SereneLinux , SkyWave Linux, Kaisen Linux, Regata OS, TROM-Jaro, DRBL Linux, Chalet OS, Chapeau, Desa OS, BlankOn, OpenMamba, Frugalware, Kibojoe Linux, Revenge OS, Tsurugi Linux, Drauger OS, Hash Linux, gNewSense, Ikki Boot, SteamOS, Hyperbola, VyOS, EasyNAS, SuperGamer, Live Raizo, Swift Linux, RebeccaBlackOS, Daphile, CRUX, Univention, Ufficio Zero, Rescuezilla, Phoenix OS, Garuda Linux, Mll, NethServer, OSGeoLive, Easy OS, Volumio, FreedomBox, paldo, UBOS, Recalbox, batocera, Lakka, LibreELEC, Pardus Topluluk, Pinguy, KolibriOS, Elastix, Arya, Omoikane, Omarine, Endian Firewall, Hamara, Rocks Cluster, MorpheusArch, Redo, Slackel, SME Server, APODIO, Smoothwall, Dragora, Linspire, Secure-K OS, Peach OSI, Photon, Plamo, SuperX, Bicom, Ploplinux, HP SPP, LliureX, Freespire, DietPi, BOSS, Webconverger, Lunar, TENS, Source Mage, RancherOS, T2, Vine, Pisi, blackPanther, mAid, Acronis, Active.Boot, AOMEI, Boot.Repair, CAINE, DaRT, EasyUEFI, R-Drive, PrimeOS, Avira Rescue System, bitdefender, Checkra1n Linux, Lenovo Diagnostics, Clover, Bliss-OS, Lenovo BIOS Update, Arcabit Rescue Disk, MiyoLinux, TeLOS, Kerio Control, RED OS, OpenWrt, MocaccinoOS, EasyStartup, Pyabr, Refracta, Eset SysRescue, Linpack Xtreme, Archcraft, NHVBOOT, pearOS, SeaTools, Easy Recovery Essentional, iKuai, StorageCraft SCRE, ZFSBootMenu, TROMjaro, BunsenLabs, Todo en Uno, ChallengerOS, Nobara, Holo, CachyOS, Peux OS, Vanilla OS, ShredOS, paladin, Palen1x, dban, ReviOS, HelenOS, XeroLinux, Tiny 11, chimera linux, CuteFish, DragonOs, Rhino Linux, vanilladpup, crystal, IGELOS, MiniOS, gnoppix, PikaOS, ......

Unix
DragonFly, FreeBSD, pfSense, GhostBSD, FreeNAS, TrueNAS, XigmaNAS, FuryBSD, OPNsense, HardenedBSD, MidnightBSD, ClonOS, EmergencyBootKit

ChromeOS
FydeOS, CloudReady, ChromeOS Flex

Other
VMware ESXi, Citrix XenServer, Xen XCP-ng

Tested Image Report

【How to report a successfully tested image file】

Ventoy Browser

With Ventoy, you can also browse ISO/WIM/IMG/VHD(x)/EFI files in local disk and boot them. Notes

VentoyPlugson

A GUI Ventoy plugin configurator. VentoyPlugson

Features

• 100% open source
• Simple to use
• Fast (limited only by the speed of copying iso file)
• Can be installed in USB/Local Disk/SSD/NVMe/SD Card
• Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
• Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk
• No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
• MBR and GPT partition style supported (1.0.15+)
• x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
• IA32/x86_64 UEFI Secure Boot supported (1.0.07+)
• Linux Persistence supported (1.0.11+)
• Windows auto installation supported (1.0.09+)
• Linux auto installation supported (1.0.09+)
• Variables Expansion supported for Windows/Linux auto installation script
• FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
• ISO files larger than 4GB supported
• Menu alias, Menu tip message supported
• Password protect supported
• Native boot menu style for Legacy & UEFI
• Most types of OS supported, 1200+ iso files tested
• Linux vDisk boot supported
• Not only boot but also complete installation process
• Menu dynamically switchable between List/TreeView mode
• "Ventoy Compatible" concept
• Plugin Framework and GUI plugin configurator
• Injection files to runtime environment
• Boot configuration file dynamically replacement
• Highly customizable theme and menu
• USB drive write-protected support
• USB normal use unaffected
• Data nondestructive during version upgrade
• No need to update Ventoy when a new distro is released

Installation Instructions

See https://www.ventoy.net/en/doc_start.html for detailed instructions.

Compile Instructions

Please refer to BuildVentoyFromSource.txt

Document

Title	Link
Install & Update	https://www.ventoy.net/en/doc_start.html
Browse/Boot Files In Local Disk	https://www.ventoy.net/en/doc_browser.html
Secure Boot	https://www.ventoy.net/en/doc_secure.html
Customize Theme	https://www.ventoy.net/en/plugin_theme.html
Global Control	https://www.ventoy.net/en/plugin_control.html
Image List	https://www.ventoy.net/en/plugin_imagelist.html
Auto Installation	https://www.ventoy.net/en/plugin_autoinstall.html
Injection Plugin	https://www.ventoy.net/en/plugin_injection.html
Persistence Support	https://www.ventoy.net/en/plugin_persistence.html
Boot WIM file	https://www.ventoy.net/en/plugin_wimboot.html
Windows VHD Boot	https://www.ventoy.net/en/plugin_vhdboot.html
Linux vDisk Boot	https://www.ventoy.net/en/plugin_vtoyboot.html
DUD Plugin	https://www.ventoy.net/en/plugin_dud.html
Password Plugin	https://www.ventoy.net/en/plugin_password.html
Conf Replace Plugin	https://www.ventoy.net/en/plugin_bootconf_replace.html
Menu Class	https://www.ventoy.net/en/plugin_menuclass.html
Menu Alias	https://www.ventoy.net/en/plugin_menualias.html
Menu Extension	https://www.ventoy.net/en/plugin_grubmenu.html
Memdisk Mode	https://www.ventoy.net/en/doc_memdisk.html
TreeView Mode	https://www.ventoy.net/en/doc_treeview.html
Disk Layout MBR	https://www.ventoy.net/en/doc_disk_layout.html
Disk Layout GPT	https://www.ventoy.net/en/doc_disk_layout_gpt.html
Search Configuration	https://www.ventoy.net/en/doc_search_path.html

FAQ

See https://www.ventoy.net/en/faq.html for detail

Forum

https://forums.ventoy.net

Donation

It would be much appreciated if you want to make a small donation to support my work!
Alipay, WeChat Pay, PayPal and Bitcoin are available for donation. You can choose any of them.

Alipay	WeChat Pay

PayPal
You can transfer to my paypal account [email protected] or just click https://www.paypal.me/ventoy

Bitcoin
Bitcoin Address 19mZDWzZgzkHCi9YX9H3fYCUuCHq3W6wfT

pxe's Issues

Debian Installer can not find CDROM after iventoy boot

Please add this to compatibility list as failure.

https://downloads.raspberrypi.com/rpd_x86/images/rpd_x86-2022-07-04/2022-07-01-raspios-bullseye-i386.iso

8th gen Intel and Up, WIN 11 setup doesn't find drivers

On Dell, Lenovo, and HP 8th gen and up Intel when loading WIN 11 setup from ISO missing drivers.
Same ISO booting off USB and entering setup without issue.
Doesn't happen with WIN 10 iso on same machines.

how change the logo of iventoy to our custom logo & sending stmp server mail after sucessful os installed

hello
i there any possible of changing logo&sending stmp server mail after sucessful os installed

pfsense and opnsense not working (FreeBSD)

When I choose iso pfsense or opnsense iventoy shuts down. ISO files for Windows, Ubuntu, Proxmox work fine.

pfsense (https://www.pfsense.org/download/)
opnsense (https://opnsense.org/download/)

Unterminated quoted string in /lib/iventoy

Operating system: Ubuntu 22.04.2 (also replicated on vanilla Debian 10.4)
Release: 1.0.08 and 1.0.09
Command: sudo bash iventoy.sh start
Error message:
/iventoy-1.0.08/lib/iventoy: 14 Syntax error: Unterminated quoted string
iventoy start FAILED

Description: When attempting to start iventoy from an ubuntu server virtual machine the an error occurred and iventoy did not start. The error is reproducible on two different linux distros and on different releases of iventoy (both 1.0.08 and 1.0.09). Note that the error message is the same for 1.0.09 but is on line 11.

status and stop command flags do not generate an error.

[Feature Request] Specify/Change ISO Folder

I would like the idea to change the location of my ISO folder. I would like it to be outside of the iVenToy folder structure and would like to see if configurable within the interface, if possible.

Cannot start pxe server in Proxmox 8 LXC (debian 12)

Hi,

I'm running Proxmox 8 with an iventoy in an LXC and have been able to get the webgui to show up and the iso directory mounted via nfs correctly. I have set the network to "externalnet" and when i go to start the pxe server i get the following error:

2023/12/05 04:39:05.861 [HTTP] API request: <{"method":"start_server","ip":"192.168.1.75","mask":"255.255.255.255","gw":"192.168.1.1","pool_begin":"255.255.255.255","pool_end":"255.255.255.255","dns_server":""}>
2023/12/05 04:39:05.861 [PXE] 1 invalid para <255.255.255.255>

I am running pfsense on my gateway 192.168.1.1 and the LXC has a local ip of 192.168.1.75

Any thoughts on what causes this issue? Thanks in advance.

Enable proxy dhcp to work with currently present and existing dhcp servers on the network.

I have a router providing dhcp, and would like iventoy to use proxy dhcp instead of changing dhcp server every time i use iventoy.

Support for Autopilot Intune?

Hello,

I saw this and thought i'd be the perfect solution if this would be implemented.
Autopilot uses a Json file on a formatted USB stick with 2 partitions to install Windows using intune.

Would it be possible to get support that you have a "intune" folder in the iVentoy structure with a intune install .img file?

Faulting kernelbase.dll

Iventoy version 1.0.18 on Windows Server 2022 running in a VM will not run or start. Nothing is displayed on screen.

Can these missing Visual C++ libraries be included in the iventoy build, or at least present an error message and link do download them from MS?

I resolved the issue by installing:
Microsoft Visual C++ 2015 Redistributable Update 3 RC
https://www.microsoft.com/en-US/download/details.aspx?id=52685

Windows Event Viewer

No only Bios boot mode possible

When I try to boot via Bios (Legacy) and I turn off the UEFI support I get the error message:
Nothing to boot and I get no boot file.

iVentoy Free Version 1.0.19P1

[Feature Request] Integration with Ventoy

Thanks for this useful project, is there any plan to integrate it with Ventoy, both Ventoy and iVentoy on a same USB ?

fuzzy screen over iventoy 1.0.17

hi
i use windows distro
actually when i boot different os over iventoy, the display screen will be fuzzy or squad!
i tried 800600 or 1024768, in any device result is different! in some laptops it's Ok in some of them it's again fuzzy
i read that ventoy have the plugin that we can change the resolution auto, does iventoy have this feature and where is it to change it or do you have any update and solutions???
@ventoy

Dracut-initqueue timeouts - no network

Occurs on both 1.0.11 & 1.0.12.
machines are VM's inside Proxmox8. iventoy server is RockyLinux, multiple clients have been tested with various settings; bios and uefi mode, virtio and E1000 NIC's.

iventoy boots and displays iso's as expected.
Select the supported 'Fedora-Workstation-Live-x86_64-38-1.6.iso' and after 140 secs of a black screen, i will start to see the console fill up with the following screenshot.
after 320 secs it will drop down to emergency/maintenance prompt. Notice that there is no ip address.

ISO Storage a Nas

Hi

How do you default location on windows to look smb share i have setup with all iso files

WONT open in windows VM

cant get this to open on a windows vm will get security warning then click yes then nothing open Both Windows server 2019 and windows 10 fully update if you need remote access let me know

Requesting ip address (BIOS) after this pxe freez

PXE error on boot

I am trying to boot into the PXE ventoy, and I get this error:
PXE -> EB: !PXE at 9D95:0070, entry point at 9D95:0186
UNDI code segment 9D95:2020, data segment 944A:94D0 (593-639kB)
UNDI device is PCI 02:00.0, type DIX*+002.3
593kB free base memory after PXE unload

*I am not lying

I tried using both the CLI and GUI boot background modes at 800x600, different DHCP server modes, and all 3 EFI boot files, also tried to fiddle with the MAC Filter, and it did show me ONCE that it wasn't a PXE client, even though I know that it is.

专业版是否能支持国产化CPU平台，比如飞腾腾锐D2000？

专业版是否能支持国产化CPU平台，比如飞腾腾锐D2000？

iVentoy for Synology

Are there plans to create a .psk build for Synology?

iVentoy Crashing during client machine boot

Hi there!
I've installed iVentoy today in VM on my server. Setted up DHCP server on my Mikrotik. And when new guest VM trying to get file via tftp from iVentoy VM, program crashes. Logs are clear, without any errors.

Technical information

Network

Vendor: Mikrotik
Model: RB951
Network: 172.16.0.0/24
Gateway: 172.16.0.1
DNS: 172.16.0.1
Next Server: 172.16.0.5
Boot File Name: iventoy_loader_16000

iVentoy 1.0.17

Type: VM
CPU: 1
RAM: 2Gb
Storage: 256Gb
IP: 172.16.0.5
OS: Fedora Server 38
User: root
Firewall: disabled
DHCP Server Mode: External

Client Machine

Type: VM
CPU: 1
RAM: 2Gb
Storage: 32Gb
IP: 172.16.0.15 (DHCP)
BIOS: SeaBIOS

Logs

2023/07/27 22:35:21.007 [PXE]  ==========================================================
2023/07/27 22:35:21.007 [PXE]  ##########################################################
2023/07/27 22:35:21.007 [PXE]  ##################### IVENTOY RUN ########################
2023/07/27 22:35:21.007 [PXE]  ##########################################################
2023/07/27 22:35:21.007 [PXE]  ==========================================================
2023/07/27 22:35:21.064 [PXE]  ##################### IVENTOY [Linux 64] ################
2023/07/27 22:35:21.064 [PXE]  Module <Log> init start ...
2023/07/27 22:35:21.064 [PXE]  Module <Log> init OK ...
2023/07/27 22:35:21.064 [PXE]  Module <Plat> init start ...
2023/07/27 22:35:21.064 [UTIL] Old system max open files: [1024     524288]
2023/07/27 22:35:21.064 [UTIL] New system max open files: [32768    32768]
2023/07/27 22:35:21.064 [PXE]  Module <Plat> init OK ...
2023/07/27 22:35:21.064 [PXE]  Module <Cfg> init start ...
2023/07/27 22:35:21.064 [PXE]  Module <Cfg> init OK ...
2023/07/27 22:35:21.064 [PXE]  Module <MAC> init start ...
2023/07/27 22:35:21.065 [PXE]  mac addr db init ...
2023/07/27 22:35:21.221 [PXE]  mac addr db init OK, total 49002 records
2023/07/27 22:35:21.221 [PXE]  Module <MAC> init OK ...
2023/07/27 22:35:21.221 [PXE]  Module <Tarfs> init start ...
2023/07/27 22:35:21.287 [PXE]  iventoy.dat <8033336> <15042560> <1eb6c319>
2023/07/27 22:35:21.846 [PXE]  Extract iventoy.dat success.
2023/07/27 22:35:21.847 [PXE]  ======= iVentoy 1.0.17 ========
2023/07/27 22:35:21.847 [PXE]  tarfs find 179 files
2023/07/27 22:35:21.847 [PXE]  Module <Tarfs> init OK ...
2023/07/27 22:35:21.847 [PXE]  Module <OS> init start ...
2023/07/27 22:35:21.847 [PXE]  cpio buf:0x7f3a071a7410 len:4409344 fixoff:343888
2023/07/27 22:35:21.847 [PXE]  Module <OS> init OK ...
2023/07/27 22:35:21.847 [PXE]  Module <IMG> init start ...
2023/07/27 22:35:21.847 [PXE]  Scan iso directory for all image files ...
2023/07/27 22:35:21.847 [PXE]  Add ISO <iso/Rocky-8.5-x86_64-dvd1.iso> size:10716446720 type:0
2023/07/27 22:35:21.848 [PXE]  [1] Phase1 parse image <iso/Rocky-8.5-x86_64-dvd1.iso> <ISO> 0 starting...
2023/07/27 22:35:21.861 [PXE]  [1] img <iso/Rocky-8.5-x86_64-dvd1.iso> <ISO> OS type:Linux
2023/07/27 22:35:21.861 [PXE]  [1] Check linux arch type for <iso/Rocky-8.5-x86_64-dvd1.iso>
2023/07/27 22:35:21.861 [PXE]  [1] Find x86_64, </EFI/BOOT/grubx64.efi>
2023/07/27 22:35:21.861 [PXE]  [1] collect initrd for <iso/Rocky-8.5-x86_64-dvd1.iso> ...
2023/07/27 22:35:21.861 [PXE]  [1] parse loader cfg </isolinux/isolinux.cfg> for <iso/Rocky-8.5-x86_64-dvd1.iso> 
2023/07/27 22:35:21.861 [PXE]  [1] new isolinux initrd </isolinux/initrd.img>
2023/07/27 22:35:21.861 [PXE]  [1] isolinux cfg: </isolinux/initrd.img> DirentOffset:72378 FileOffset:738867200 FileSize:79894932
2023/07/27 22:35:21.861 [PXE]  [1] parse loader cfg </boot/grub/grub.cfg> for <iso/Rocky-8.5-x86_64-dvd1.iso> 
2023/07/27 22:35:21.861 [PXE]  [1] <boot/grub/grub.cfg> not found in ISO file.
2023/07/27 22:35:21.861 [PXE]  [1] parse loader cfg </EFI/BOOT/grub.cfg> for <iso/Rocky-8.5-x86_64-dvd1.iso> 
2023/07/27 22:35:21.861 [PXE]  [1] new grub2 initrd </images/pxeboot/initrd.img>
2023/07/27 22:35:21.861 [PXE]  [1] grub2 cfg: </images/pxeboot/initrd.img> DirentOffset:69962 FileOffset:738867200 FileSize:79894932
2023/07/27 22:35:21.861 [PXE]  [1] [INITRD 0] /isolinux/initrd.img
2023/07/27 22:35:21.861 [PXE]  [1] [INITRD 1] /images/pxeboot/initrd.img
2023/07/27 22:35:21.861 [PXE]  [1] collect initrd for <iso/Rocky-8.5-x86_64-dvd1.iso> finished.
2023/07/27 22:35:21.861 [PXE]  [1] Find <images/install.img> for <iso/Rocky-8.5-x86_64-dvd1.iso>
2023/07/27 22:35:21.862 [PXE]  [1] Phase1 parse image <iso/Rocky-8.5-x86_64-dvd1.iso> finished success
2023/07/27 22:35:21.862 [PXE]  ================= PXE IMG DUMP =================
2023/07/27 22:35:21.862 [PXE]  [1] <Rocky-8.5-x86_64-dvd1.iso> <10716446720> <ISO> <Linux> <x86_64> <Initrd:2>
2023/07/27 22:35:21.862 [PXE]  ================================================
2023/07/27 22:35:21.862 [PXE]  Module <IMG> init OK ...
2023/07/27 22:35:21.862 [PXE]  Module <DHCP> init start ...
2023/07/27 22:35:21.862 [PXE]  Module <DHCP> init OK ...
2023/07/27 22:35:21.862 [PXE]  Module <TFTP> init start ...
2023/07/27 22:35:21.862 [PXE]  Module <TFTP> init OK ...
2023/07/27 22:35:21.862 [PXE]  Module <HTTP> init start ...
2023/07/27 22:35:21.869 [HTTP] HTTP API service is running on 0.0.0.0:26000 ...
2023/07/27 22:35:21.920 [PXE]  Module <HTTP> init OK ...
2023/07/27 22:35:21.920 [PXE]  Module <NBD> init start ...
2023/07/27 22:35:21.920 [PXE]  Module <NBD> init OK ...
2023/07/27 22:35:21.920 [PXE]  <51323974625739754945745754534277636d396a5a584e7a6233493d>
2023/07/27 22:35:21.920 [PXE]  <4d32457a4e7a46684e7a41304e4759324e446b31597a686b4d446b354d6a63784d6d466d4f4463354d54673d>
2023/07/27 22:35:21.920 [PXE]  4efa4cf32f578e84155f56a779c90d035c6cd679b99444b31b185c38bddc1f17
2023/07/27 22:35:21.920 [PXE]  ====================== SYSTEM IP LIST ===================================
2023/07/27 22:35:21.920 [PXE]   [1] 172.16.0.5        255.255.255.0     172.16.0.1        ens18
2023/07/27 22:35:21.920 [PXE]  =========================================================================
2023/07/27 22:35:21.920 [PXE]  PXE cofigure recovery ...
2023/07/27 22:35:21.920 [PXE]  data/config.dat is valid, now recover data ...
2023/07/27 22:35:21.920 [PXE]  Recover: dhcp server mode 1
2023/07/27 22:35:21.920 [PXE]  Recover: boot background mode 1
2023/07/27 22:35:21.920 [PXE]  Recover: efi boot file 0
2023/07/27 22:35:21.920 [PXE]  Recover: boot resolution 1024 x 768
2023/07/27 22:35:21.920 [PXE]  Recover: ip:172.16.0.5 mask:255.255.255.0 gateway:172.16.0.1 pool:[172.16.0.200-172.16.0.219]
2023/07/27 22:35:21.920 [PXE]  Recover: HTTP port:16000 NBD port:10809 TFTP timeout:5 TFTP max-retransmit:3
2023/07/27 22:35:21.920 [PXE]  Recover filter [deny] mode
2023/07/27 22:35:21.920 [PXE]  =============== PXE cofigure recovery finished ===============
2023/07/27 22:35:21.920 [PXE]  iVentoy entering main loop ...
2023/07/27 22:35:25.977 [HTTP] API request: <{"method":"sysinfo"}>
2023/07/27 22:35:26.000 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/27 22:35:26.005 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/27 22:35:27.591 [HTTP] API request: <{"method":"get_config_all"}>
2023/07/27 22:35:29.101 [HTTP] API request: <{"method":"get_img_tree"}>
2023/07/27 22:35:30.194 [HTTP] API request: <{"method":"get_config_all"}>
2023/07/27 22:35:32.399 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/27 22:35:32.408 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/27 22:35:33.224 [HTTP] API request: <{"method":"start_server","ip":"172.16.0.5","mask":"255.255.255.0","gw":"172.16.0.1","pool_begin":"172.16.0.200","pool_end":"172.16.0.219","dns_server":""}>
2023/07/27 22:35:33.225 [PXE]  Update Mask[255.255.255.0 --> 255.255.255.0] GW[172.16.0.1 --> 172.16.0.1]
2023/07/27 22:35:33.225 [PXE]  iVentoy service is starting ...
2023/07/27 22:35:33.226 [PXE]  [1] Phase2 parse image <iso/Rocky-8.5-x86_64-dvd1.iso> <ISO> starting...
2023/07/27 22:35:33.226 [PXE]  [1] <iso/Rocky-8.5-x86_64-dvd1.iso> virt data cpiolen:4409344 extfiles:2048
2023/07/27 22:35:33.226 [PXE]  [1] Virt data ISO file size: 10716446720 10952208384
2023/07/27 22:35:33.226 [PXE]  [1] ================ OVERRIDE DUMP ================
2023/07/27 22:35:33.226 [PXE]  [1]  <0> [ 72378 - 72394 16 ]
2023/07/27 22:35:33.226 [PXE]  [1]  <1> [ 69962 - 69978 16 ]
2023/07/27 22:35:33.226 [PXE]  [1] ================ OVERRIDE DUMP ================
2023/07/27 22:35:33.226 [PXE]  [1] ================ VIRT RANGE DUMP ================
2023/07/27 22:35:33.226 [PXE]  [1]  <iso/Rocky-8.5-x86_64-dvd1.iso> WIM:2/2
2023/07/27 22:35:33.226 [PXE]  [1]  <01> [10716446720 - 10716448768 2048      ] iVentoy Param
2023/07/27 22:35:33.226 [PXE]  [1]  <02> [10716448768 - 10750003200 33554432  ] Zero
2023/07/27 22:35:33.227 [PXE]  [1]  <03> [10750003200 - 10754412544 4409344   ] Memory
2023/07/27 22:35:33.227 [PXE]  [1]  <04> [10754412544 - 10754414592 2048      ] Memory
2023/07/27 22:35:33.227 [PXE]  [1]  <05> [10754414592 - 10834309524 79894932  ] Remap
2023/07/27 22:35:33.227 [PXE]  [1]  <06> [10834311168 - 10834313216 2048      ] iVentoy Param
2023/07/27 22:35:33.227 [PXE]  [1]  <07> [10834313216 - 10867867648 33554432  ] Zero
2023/07/27 22:35:33.227 [PXE]  [1]  <08> [10867867648 - 10872276992 4409344   ] Memory
2023/07/27 22:35:33.227 [PXE]  [1]  <09> [10872276992 - 10872279040 2048      ] Memory
2023/07/27 22:35:33.227 [PXE]  [1]  <10> [10872279040 - 10952173972 79894932  ] Remap
2023/07/27 22:35:33.227 [PXE]  [1]  <11> [10952175616 - 10952208384 32768     ] Zero
2023/07/27 22:35:33.227 [PXE]  [1] ================ VIRT RANGE DUMP ================
2023/07/27 22:35:33.227 [PXE]  [1] Phase2 parse image <iso/Rocky-8.5-x86_64-dvd1.iso> finished success
2023/07/27 22:35:33.227 [PXE]  Update ipxe menu 1 ...
2023/07/27 22:35:33.227 [PXE]  ================= IMG TREE DUMP =================
2023/07/27 22:35:33.227 [PXE]  Rocky-8.5-x86_64-dvd1.iso [1] <images/install.img> <INITRD:2>
2023/07/27 22:35:33.227 [PXE]  ================================================
2023/07/27 22:35:33.228 [HTTP] HTTP PXE service starting ...
2023/07/27 22:35:33.228 [TFTP] TFTP service starting ...
2023/07/27 22:35:33.228 [DHCP] DHCP service starting ...
2023/07/27 22:35:33.228 [UTIL] Bind Socket(172.16.0.5) to Device ens18
2023/07/27 22:35:33.228 [NBD]  NBD service starting ...
2023/07/27 22:35:33.228 [PXE]  Now save iventoy config data ...
2023/07/27 22:35:33.229 [PXE]  iventoy config data (data/config.dat) save OK
2023/07/27 22:35:33.229 [PXE]  ===========================================================
2023/07/27 22:35:33.229 [PXE]         iVentoy 1.0.17 [Linux 64] is running now ...
2023/07/27 22:35:33.229 [PXE]  ===========================================================
2023/07/27 22:35:33.229 [HTTP] NBD service is running on 172.16.0.5:10809 ...
2023/07/27 22:35:33.229 [DHCP] DHCP service is running ...
2023/07/27 22:35:33.230 [TFTP] TFTP service is running ...
2023/07/27 22:35:33.230 [TFTP] TFTP write thread is running 28 ...
2023/07/27 22:35:33.230 [HTTP] HTTP PXE service is running on 172.16.0.5:16000 ...
2023/07/27 22:35:33.235 [HTTP] API request: <{"method":"query_status"}>
2023/07/27 22:35:33.250 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/27 22:35:33.259 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/27 22:35:45.362 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<DISCOVER> ARCH:<Intel x86PC> (nil)
2023/07/27 22:35:45.362 [DHCP] snopping add client 32-4b-54-8f-da-1a
2023/07/27 22:35:46.386 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<DISCOVER> ARCH:<Intel x86PC> 0x7f39e8001a00
2023/07/27 22:35:48.418 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<REQUEST> ARCH:<Intel x86PC> 0x7f39e8001a00
2023/07/27 22:35:48.477 [TFTP] Parse tftp option(blksize,1432)
2023/07/27 22:35:48.477 [TFTP] Parse tftp option(tsize,0)
2023/07/27 22:35:48.477 [TFTP] TFTP RRQ client 172.16.0.13:46546 download <iventoy_loader_16000> start ...
2023/07/27 22:35:48.477 [DHCP] snooping record found 172.16.0.13
2023/07/27 22:35:48.477 [TFTP] DHCP External client 172.16.0.13 should use loader ipxe.bios.0
2023/07/27 22:35:48.477 [TFTP] Start send file iventoy_loader_16000 to 172.16.0.13:46546 with blksize 1432, has oack 1
2023/07/27 22:35:48.494 [TFTP] Finished send file to 172.16.0.13:46546 with blksize 1432 blks 93
2023/07/27 22:35:48.770 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<DISCOVER> ARCH:<Intel x86PC> 0x7f39e8001a00
2023/07/27 22:35:49.791 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<DISCOVER> ARCH:<Intel x86PC> 0x7f39e8001a00
2023/07/27 22:35:51.824 [DHCP] Snooping 32-4b-54-8f-da-1a MSG:<REQUEST> ARCH:<Intel x86PC> 0x7f39e8001a00

Provide Docker image

Is it possible to provide a Docker image? I run all my services through Docker, it's much easier to deploy.

add support for 32bit raspberrypi armel

as the title says, please add it

Change Network Adapter

I have several different network adapters stored in the system and unfortunately iVentory automatically takes the wrong one (VMware Virtual Ethernet Adapter for VMnet1) and not the physical LAN or WLAN interface.

Please add function to change the network interface.

Thanks

new

Malware detected with iVentoy

Hello,

I've added iVentoy to the Chocolatey community repository. I published version 1.0.6 and it was approved today.

The problem though with current versions, is that there are an increasing number of malware detections with iVentoy...

Version 1.0.6 - 12 detections:
https://www.virustotal.com/gui/file/9d3d0a2ad1811eae4fa3f095149f53511e74276993a44f4ff010ec0467b6e266

Version 1.0.8 - 3 detections:
https://www.virustotal.com/gui/file/4cfb8b9fa531622d7a921489e60fb8d66efd1983132d441f9b03ecfb105cc050

Version 1.0.11 - 17 detections:
https://www.virustotal.com/gui/file/a1104207e58b9cbe38a7f23f2cae286b909c61033f36b3f2c94da74176533445

Version 1.0.16 - 20 detections:
https://www.virustotal.com/gui/file/34aeb1e1a1d4a766b2f481e6bd5237e3fcd8effb70768efeaee679fa360ae6a9

Was something added to the code to make these detections show up? I'm sure they are false positives, but something must have changed that is triggering these.

With so many detections, I do not think I will be able to get this approved for the Chocolatey community repository.

Any thoughts? Perhaps some new feature was added that is triggering this.

I'd like to add it to Chocolatey so that users can just type "choco install iventoy".

Alternatively, if you could provide a strong reason to explain the detections, I may be able to get the package manually approved.

From the review team at Chocolatey:
"In order to get this exempted, despite the AV detections, is some sort of official statement from the software author about the detections being expected which can be linked to from the package description."

Can you provide an official statement and have it on iVentoy.com explaining why it may show as a false positive? That would help avoid people thinking that iVentoy contained malicious code.

I went ahead and submitted false positive reports to Avast, AVG, VIPRE, BitDefender, GDATA, and Webroot.

According to the behavior tab of VirusTotal, some program.exe is running from the desktop?
https://www.virustotal.com/gui/file/34aeb1e1a1d4a766b2f481e6bd5237e3fcd8effb70768efeaee679fa360ae6a9/behavior

But according to sysmon monitoring, I don't see that happening. So I think that's one of the reasons it's a false positive.

Maybe there's something extra in the code?

Thank you

[Question]iPXE vs iVentoy ?

Hi, what is the difference between iPXE and iVentoy ?

Is iVentoy a new fork of the old iPXE repo ?

need building guide to build on different arch i wana build for orangepi zero arm64

在xenserver 8.0虚拟机上，创建的磁盘是/dev/xvda发现使用的debian-10.12.0-amd64-DVD-1.iso

在xenserver 8.0虚拟机上，创建的磁盘是/dev/xvda发现使用的debian-10.12.0-amd64-DVD-1.iso的并启用自动化脚本安装后显示一杠

iPXE error c852003

I'm getting error c852003 [https://ipxe.org/err/3c8520] when trying to boot memtest86+ iso on Supermicro X10SRL-F. Tried Intel PXE from firmware and from Debian 11

netboot.xyz does already the same?

Hi,
in my opinion, especially in times where many Projects are in search for maintainers, this project does not make so much sense, as there already is https://netboot.xyz/docs which does it very similar.

Maybe it would be better to talk to them and help or fork?

Kind regards

Mike

Will not start on Windows Server

Hello, I cannot launch the iventoy program on a Clean VM running Windows Server 2022

I click the file but nothing starts.

2023-07-07_23-54-22.mp4

How to run in a systemd service?

I am running the linux version of this software

Due to how the program is started it is difficult to run as a systemd service.
Since the script iventoy.sh starts the iventoy process they have different names and as far as I can tell if using systemd the script cannot be used to start the process

From reading the start script I have been able to determine that as root this will start it.

cd /opt/iventoy/
env IVENTOY_API_ALL=1 IVENTOY_AUTO_RUN=1 /opt/iventoy/lib/iventoy

This works when run manually at the command line.

However If I try to run this as a service the process will not successfully start

[Unit]
Description=Iventoy Service
After=network.target

[Service]
Type=simple
Environment="IVENTOY_API_ALL=1"
Environment="IVENTOY_AUTO_RUN=1"
WorkingDirectory=/opt/iventoy
ExecStart=/opt/iventoy/lib/iventoy
Restart=always

[Install]
WantedBy=default.target

No success with this variation either.

[Unit]
Description=Iventoy Service
After=network.target

[Service]
Type=simple
WorkingDirectory=/opt/iventoy
ExecStart=env IVENTOY_API_ALL=1 IVENTOY_AUTO_RUN=1 /opt/iventoy/lib/iventoy
Restart=always

[Install]
WantedBy=default.target

Below is the output I get from running sudo systemctl status iventoy.service

× iventoy.service - Iventoy Service
     Loaded: loaded (/etc/systemd/system/iventoy.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-08-23 17:12:47 UTC; 952ms ago
    Process: 1438 ExecStartPre=/bin/bash -c cd /opt/iventoy (code=exited, status=0/SUCCESS)
    Process: 1439 ExecStart=/opt/iventoy/lib/iventoy (code=exited, status=127)
   Main PID: 1439 (code=exited, status=127)
        CPU: 3ms

Aug 23 17:12:47 iventoy systemd[1]: iventoy.service: Scheduled restart job, restart counter is at 5.
Aug 23 17:12:47 iventoy systemd[1]: Stopped Iventoy Service.
Aug 23 17:12:47 iventoy systemd[1]: iventoy.service: Start request repeated too quickly.
Aug 23 17:12:47 iventoy systemd[1]: iventoy.service: Failed with result 'exit-code'.
Aug 23 17:12:47 iventoy systemd[1]: Failed to start Iventoy Service.

I definitely feel a product such as iventoy needs a way to be run as a service like this to ensure reliability.

systemd init

in case anyone else needs one like I did. this is working on ubuntu 22.04

[Unit]
Description=iVentoy tftp service
Wants=network-online.target
After=network-online.target
DefaultDependencies=no
Conflicts=shutdown.target
Before=shutdown.target

[Service]
Type=forking
# REPLACE WITH YOUR INSTALL DIRECTORY BELOW
WorkingDirectory=/usr/local/iventoy
ExecStart=bash iventoy.sh -R start
ExecStop=bash iventoy.sh stop

[Install]
WantedBy=multi-user.target

maybe make an examples/init or something similar in the release, for things like this?

Load Driver Issue

Getting Load Driver issue when installing Windows 10 22H2.

Not starting in Debian Bookworm

When using a fresh install of Debian 12.0.1 (Bookworm) iventoy seems to crash after start.

~/iventoy-1.0.17$ sudo bash iventoy.sh start 
iventoy start SUCCESS PID=0

Please open your browser and visit http://127.0.0.1:26000 or http://x.x.x.x:26000 (x.x.x.x is any valid IP address)

~/iventoy-1.0.17$ sudo bash iventoy.sh status
iventoy is not running.

When looking at the log.txt you can see that there seems to be an issue reading a file

2023/07/28 13:05:43.411 [PXE]  ==========================================================
2023/07/28 13:05:43.411 [PXE]  ##########################################################
2023/07/28 13:05:43.411 [PXE]  ##################### IVENTOY RUN ########################
2023/07/28 13:05:43.411 [PXE]  ##########################################################
2023/07/28 13:05:43.411 [PXE]  ==========================================================
2023/07/28 13:05:43.415 [UTIL] Failed to open file <./data/sys/class/dmi/id/product_uuid> errno:13
2023/07/28 13:05:43.415 [UTIL] read sys directory failed 1, errno:13
2023/07/28 13:05:43.417 [PXE]  ### iVentoy start failed. ###

I also tried it as root by using bash inventoy.sh start and the startup also fails in the same way.

Boot from SAN device 0xe0 failed

Intel NUC pc boots to iventoy but can not load any iso files. Other computers on the network boot iso files fine. I tried booting ipxe 1.21.1 from usb with no problems. It boots Iventoy but trying to load iso it shows :
Boot from SAN device 0xe0 failed: Error 0x7f222091
The nic is rtl18168 - the uefi bios shows it is using undi drivers.

display squashed up on some images

I've noticed this on a few test images (reproducible with mt86plus_620_64.iso; https://memtest.org/).

iventoy 1.0.12 (occurs on .11 too).
iventoy using default 1024x768.
Proxmox VM defaults to 1280x800.
^ this is the config used for the below screenshot. I've tried changing resolution to match and other common res's but no solution.

not working pxe client host debian 12

mount directory failed, errno:13

Im trying to start the iVentoy web interface with sudo iventoy.sh start.
I get: iventoy start SUCCESS PID=0 Please open your browser and visit http://127.0.0.1:26000 or http://x.x.x.x:26000 (x.x.x.x is any valid IP address)

but then when i go look into the logs i see this: 2023/10/30 15:48:06.442 [PXE] ========================================================== 2023/10/30 15:48:06.442 [PXE] ########################################################## 2023/10/30 15:48:06.442 [PXE] ##################### IVENTOY RUN ######################## 2023/10/30 15:48:06.442 [PXE] ########################################################## 2023/10/30 15:48:06.442 [PXE] ========================================================== 2023/10/30 15:48:06.442 [UTIL] mount directory failed, errno:13 2023/10/30 15:48:06.442 [PXE] ### iVentoy start failed. ###

please provide CENTOS 7 Image for UEFI

unable to install image in uefi mod e
can please share the image

Launching clonezilla-live-3.1.0-22-amd64 using a customized grub.cfg results in a boot failure.

Launching clonezilla-live-3.1.0-22-amd64 using a customized grub.cfg results in a boot failure, accompanied by the error message "unable to find a medium containing a live file system."

Conversely, when booting the unaltered clonezilla-live-3.1.0-22-amd64.iso, it functions correctly.

Suppose I make adjustments to the grub.cfg file located in \boot\grub, such as muting the beep sound during the clonezilla boot process. In that case, the modified grub.cfg would look like this:

Booting this modified iso results in the boot failure with the following massage as below:

Here are difference noticed in the log file :

• Booting untouched clonezilla iso file

When untouched clonezilla iso is booted it makes a http request as follows
« [HTTP] 200 HEAD /riso/id/1/00:15:5d:f7:21:00 size 414187520 »
which doesn’t happen when booted with a modified grub.cfg

• Booting modified Grub.cfg :

Trust questions: Not fully open source and requires root

Hi,

Just found out about iVentoy which seemed very promising. Until i tried to start it and it said:

$ ./iventoy.sh
Please use sudo or run the script as root

So I've got three major doubts about this program which stopped me from running it for now:

1. It is not fully open source.
2. It requires to start the program with elevated privileges.
3. Ultimately, it is developed from China, which becomes a problem because of the two previous points and the security risks involved with this country known to hack basically anything that can be hacked.

I'm not the only one thinking that way as the most upvoted answer warns about it here: https://www.reddit.com/r/selfhosted/comments/14ifnii/iventoy_is_out_now_ease_of_ventoy_with_just_on_pxe/ and the most upvoted answer to it says "Too many red flags for my self hosted environment. I'll keep an eye on it but I won't install it until a lot of that changes" and has almost as many upvotes.

So I've seen there was a paid version which might explain why it isn't fully open source. However I don't imagine people using such a tool recompiling it or using unofficial sources just to avoid paying a reasonable price of $49 when needing the pro version.

So, why is it not open source?
And why does this need elevated privileges? For example game servers provide listening services that don't require root privileges at all and have been working well for years that way.
And how can we trust this program to not add backdoors or other unwanted scripts/programs to the hosting system or to machines installed using it?

Thank you

Error opcode pkt while connecting to ventoy

Hi,
I am unable to load files from iventoy.
I receive the following error:

2023/11/29 19:59:20.241 [TFTP] DHCP External client 192.168.1.10 should use loader ipxe.bios.0
2023/11/29 19:59:20.241 [TFTP] Start send file iventoy_loader_16000 to 192.168.1.10:1183 with blksize 1468, has oack 1
2023/11/29 19:59:20.242 [TFTP] Recv an ERROR opcode pkt from client 192.168.1.10:1183.
2023/11/29 19:59:20.244 [TFTP] Parse tftp option(blksize,1468)
2023/11/29 19:59:20.244 [TFTP] TFTP RRQ client 192.168.1.10:1184 download <iventoy_loader_16000> start ...
2023/11/29 19:59:20.244 [DHCP] snooping record not found 192.168.1.10
2023/11/29 19:59:20.244 [TFTP] Client 192.168.1.10 not found in nodhcp iventoy_loader_16000
2023/11/29 19:59:20.244 [TFTP] DHCP External client 192.168.1.10 should use loader ipxe.bios.0
2023/11/29 19:59:20.244 [TFTP] Start send file iventoy_loader_16000 to 192.168.1.10:1184 with blksize 1468, has oack 1
2023/11/29 19:59:20.274 [TFTP] Finished send file to 192.168.1.10:1184 with blksize 1468 blks 91

I try this for the first time using my notebook. I want to install Debian. I tried UEFI and Legacy in BIOS.. both lead to the same problem. Soon as I start connecting my notebook, I receive a successfull download message, while it's freezing at the same time until the notebook self-reboots...

I use v1.0.19

无法设置自动安装脚本

已解决 关闭状态下才可设置自动安装脚本

Edit, figured it out, delete me

Figured it out after some trial and error

iventoy能否支持在树莓派上搭建PXE服务器

我正在研究使用树莓派搭建PXE服务器，看到iventoy方案比较方便就尝试了一下，但是使用官方的文件包还是尝试使用源码，都没有安装成功，请给一个解决方案，谢谢

iVentoy Autostart

As far as I can tell, there is no realistic way of launching iVentoy at boot as of right now. In my case, and likely in many other people's case, my server goes down overnight to save energy, and when it comes up in the morning I have no way of starting iVentoy other than to SSH in, and then go to the webpanel to start the DHCP. It would be cool to see the integration of a SystemD and OpenRC script which can automatically start the iVentoy service and DHCP server. This would also make it handy if any servers go offline at any point, and when they come back online the PXE services do not have to be started again manually.

Not really an issue, more of a suggesdtion but still.

iVentoy using Chrome instead of default browser

I'm using Brave Browser as my default, but have Chrome installed.

When iVentoy launches, it opens Chrome instead of my default browser.

Windows 11, iVentoy 64-bit.

Thank you 😊

debian screen

The screen appears correctly in the ISO selection menu, and when selecting Debian, the installation menu loads correctly. However, once "install" is clicked, either with or without a GUI, the screen seems to shrink and becomes squashed against the upper edge of the monitor, occupying only 1 or 2 cm of the screen.