iPXE discussion forum

Full Version: Kernel panic after iPXE - Kernel handover when using EFI iPXE
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I am currently playing with UEFI and wanted to make my installer UEFI-ready. For that I compiled a fresh ipxe.efi from the git repo (g761e) and compiled it like this:

/ipxe/src$ make bin-x86_64-efi/ipxe.efi

The ISC-DHCPd is set up like this:

host testvmcent.training.mucre1.retloc{
  hardware ethernet 00:11:22:33:44:55;
  option host-name "testhost";
  if exists user-class and option user-class = "iPXE" {
      filename "http://otherhost/ipxe/menu.ipxe";
  } else {
      if option client-arch = 00:00 {
        filename "/undionly.kpxe";
      } elsif option client-arch = 00:07 {
        filename "/ipxe.efi";

This way UEFI correctly hands over to iPXE.

I am then presented my menu.ipxe, of which entries I choose for example to boot an live debian buster (but the problem exists as well with CentOS 7/8 and different Ubuntu versions):

kernel http://otherhost/ipxe/buster-live/linux
initrd http://otherhost/ipxe/buster-live/initrd
imgargs linux boot=live config hooks=filesystem noautologin noeject fetch=http://otherhost/ipxe/buster-live/filesystem.squashfs
boot || goto failed

Half a second into the booting process the system produces a kernel panic as shown in the screenshot.


(Not embedding due to privacy and bandwidth reasons.)

Quote:No filesystem could mount root, tried:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Why does this happen? It works fine with the same version of iPXE in BIOS-mode. Th
e EFI is the emulated VMware one.

(I know that this most likely is not iPXE-related, but I also know that here I will find the people who have extensive knowledge into the topic, even after the iPXE -> Linux handover.)
Reference URL's