[GH-ISSUE #1636] netbootxyz booting on Proxmox VM / Broken menu items #2092

New issue

Open

opened 2026-03-01 18:38:26 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 18:38:26 +03:00

Owner

Originally created by @n3gwg on GitHub (Jun 8, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1636

Anthony, et alia:

Problem 1: Using a Proxmox VM I was unable to get netbootxyz to boot with OVFM firmware, it simply did not work and stated that UEFI QEMU HARD DISK was not found.

Solution 1: A fellow Proxmox user indicated that adding a "vrtio rng device" would fix the issue (it did), but more issues became apparent as follow hereupon.

NOTE: It is imperative to assure that the boot order has the network device listed first and is selected to be booted from in "Boot order" under "Options".

I do not know if it is relevant or not, but the network device I was using was a VirtIO network "card".

Both of these issues are coming from within the "Live CDs" menu.

Issue 1 - Booting Kali Linux

After a lengthly download process (I did not have Kali as a local asset), it errored out. A screenshot has been attached to this message.

Issue 2 - Fedora Linux

I tried to select either Fedora 41 or Fedora 42, neither of which ever even started to boot from the menu. It just stayed right on the menu selection doing nothing.

Stuart

Originally created by @n3gwg on GitHub (Jun 8, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1636 ![Image](https://github.com/user-attachments/assets/a9c01cbb-cef5-45a0-a955-7f42dd6e29a3) Anthony, et alia: Problem 1: Using a Proxmox VM I was unable to get netbootxyz to boot with OVFM firmware, it simply did not work and stated that UEFI QEMU HARD DISK was not found. Solution 1: A fellow Proxmox user indicated that adding a "vrtio rng device" would fix the issue (it did), but more issues became apparent as follow hereupon. NOTE: It is imperative to assure that the boot order has the network device listed first and is selected to be booted from in "Boot order" under "Options". I do not know if it is relevant or not, but the network device I was using was a VirtIO network "card". Both of these issues are coming from within the "Live CDs" menu. Issue 1 - Booting Kali Linux After a lengthly download process (I did not have Kali as a local asset), it errored out. A screenshot has been attached to this message. Issue 2 - Fedora Linux I tried to select either Fedora 41 or Fedora 42, neither of which ever even started to boot from the menu. It just stayed right on the menu selection doing nothing. Stuart

kerem added the

bug

label

2026-03-01 18:38:26 +03:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#2092

No description provided.

Rows
Columns