Article 6QR7J Seeking guidance for UEFI HTTP Boot for -current

Seeking guidance for UEFI HTTP Boot for -current

by
mishehu
from LinuxQuestions.org on (#6QR7J)
I'm trying to get UEFI HTTP booting working, first for some qemu vms, and then later for some physical machines. What I have done is this:

1. Added this stanza to my dhcpd.conf on my dhcp server box, and restarted the service:

class "httpclients" {
match if substring (option vendor-class-identifier, 0, 10) = "HTTPClient";
option vendor-class-identifier "HTTPClient";
filename "http://192.168.0.1/slackware64-current/isolinux/efiboot.img";
}

2. I bind mounted my copy of the slackware64-current repo into a subdir in my htdocs path.

3. Created the new vm in qemu, using the pflash option.

The vm comes up, and after attempting PXE boot on both ipv4 and ipv6, it then tries HTTP Boot, and it succeeds to get the isolinux/efiboot.img over http (httpd logs show this), but I get dropped into a generic grub shell instead of being presented with any menu options in grub. Running "ls" in the grub shell does show an hd0 and an hd1 as existing. I, however, am guessing that I am missing a piece of the puzzle, and I'm not finding anything on google searches. Does anybody know what else i would need to do to get this working? (My -current is synchronized to the latest, and I sync it quite regularly.)
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments