[GH-ISSUE #657] Cannot BIOS boot NixOS #1735

Closed
opened 2026-03-01 18:35:54 +03:00 by kerem · 0 comments
Owner

Originally created by @RaitoBezarius on GitHub (Jun 21, 2020).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/657

Describe the bug
Using netboot.xyz for BIOS (netboot.kpxe), I cannot boot NixOS without a kernel panic failure regarding root block device.

To Reproduce

  1. Configure a KVM guest using QEMU to boot using iPXE (in my case, I'm using TFTP) with ≥ 4 GiB of RAM.
  2. Set it for BIOS booting and not UEFI.
  3. Run any version of NixOS available.
  4. Observe kernel panic.

Expected behavior
Like UEFI, NixOS is supposed to boot properly and reach the stage 1 at least.

Screenshots
Screen Capture_select-area_20200621190232

Additional context

In UEFI, it works fine. I know of #392 and tried even to bump to 8 GiB of RAM, it didn't solve it. I heard of issues on the IRC, in 2018, https://logs.nix.samueldr.com/nixos/2018-05-21 (Ctrl+F "netboot").

Unsure what's going on at all.

Originally created by @RaitoBezarius on GitHub (Jun 21, 2020). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/657 **Describe the bug** Using netboot.xyz for BIOS (netboot.kpxe), I cannot boot NixOS without a kernel panic failure regarding root block device. **To Reproduce** 1. Configure a KVM guest using QEMU to boot using iPXE (in my case, I'm using TFTP) with ≥ 4 GiB of RAM. 2. Set it for BIOS booting and not UEFI. 3. Run any version of NixOS available. 4. Observe kernel panic. **Expected behavior** Like UEFI, NixOS is supposed to boot properly and reach the stage 1 at least. **Screenshots** ![Screen Capture_select-area_20200621190232](https://user-images.githubusercontent.com/314564/85230658-fbba4400-b3f1-11ea-89b7-773ffe7cb0fb.png) **Additional context** In UEFI, it works fine. I know of #392 and tried even to bump to 8 GiB of RAM, it didn't solve it. I heard of issues on the IRC, in 2018, https://logs.nix.samueldr.com/nixos/2018-05-21 (Ctrl+F "netboot"). Unsure what's going on at all.
kerem closed this issue 2026-03-01 18:35:54 +03:00
Sign in to join this conversation.
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#1735
No description provided.