[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #41488] x86_64-efi PXE data not populated in some circumstances

From: Joe Mroczek
Subject: [bug #41488] x86_64-efi PXE data not populated in some circumstances
Date: Thu, 06 Feb 2014 23:59:04 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.102 Safari/537.36


                 Summary: x86_64-efi PXE data not populated in some
                 Project: GNU GRUB
            Submitted by: mr_joem
            Submitted on: Thu 06 Feb 2014 11:59:02 PM GMT
                Category: Network
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Joe Mroczek
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 2.02~beta1
         Reproducibility: Every Time
         Planned Release: None




This is my first time posting a bug. I am sure I have missed something. Please
let me know any additional details or testing I can provide.

Issue: In my environment grub shows both server and bootfile to be blank. It
also fails to set root and prefix. 

Client: Intel DC3217IYE in EFI Mode, secure boot disabled ALSO Microsoft
Hyper-V 2012 R2 Gen 2 Virtual machine, secure boot disabled.

Grub Versions tried: Prebuilt grubnetx64.efi from saucy-2.00-ubuntu4,
saucy-2.00-19ubuntu2.1, trusty-2.02~beta2-6. Also multiple images created with
mkimage from saucy-2.00-19ubuntu2 and saucy-2.00-19ubuntu2.1. 

DHCP and PXE are hosted on different servers; both Microsoft. NextServer and
BootFile are NOT in DHCP offer, but they are in the proxy response (aka
altserviceboot or port 4011 response). I am attaching a pcap from Wireshark
1.8.5 that shows the entire conversation. Note that bootnetx64.efi has been
renamed to wdsmgfw.efi to trick WDS into feeding it to the client.

I grepped about in the saucy-2.00-19ubuntu2.1 package. It looks like only DHCP
ACK is examed for boot info. In our environment server and boot file would not
be present there. They should however be in a later field (I don't know how to
examine EFI structures). I am not a real programmer, so I could be way of

Thank you for any attention you can pay this issue. Please let me know
anything I can provide to drive this issue forward.



File Attachments:

Date: Thu 06 Feb 2014 11:59:02 PM GMT  Name: Grub Variables.PNG  Size: 28kB  
By: mr_joem

Date: Thu 06 Feb 2014 11:59:02 PM GMT  Name:
2.00-19Ubuntu2.1-Prebuilt-Boot.pcap  Size: 1018kB   By: mr_joem



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]