qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Brown <mcb30@ipxe.org>
To: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	ipxe-devel <ipxe-devel@ipxe.org>
Subject: Re: [Qemu-devel] [ipxe-devel] EFI_PXE_BASE_CODE_PROTOCOL
Date: Mon, 07 Sep 2015 15:02:18 +0100	[thread overview]
Message-ID: <55ED98EA.4060101@ipxe.org> (raw)
In-Reply-To: <1441620856.27149.11.camel@redhat.com>

On 07/09/15 11:14, Gerd Hoffmann wrote:
> ipxe just got a EFI_PXE_BASE_CODE_PROTOCOL implementation.  I've updated
> ipxe and commented the EFI_DOWNGRADE_UX define in the qemu config.  If
> you want to test this you can fetch the qemu branch with the updated
> roms here:
>
> https://www.kraxel.org/cgit/qemu/log/?h=rebase/roms-next
>
> Ran a quick test.  The good news are that shim.efi can now fetch files,
> it happily chainloads grub.efi.  The bad news are that grub.efi has
> trouble loading files.  It doesn't present the boot menu but greets me
> with a prompt, which usually happens if grub fails to load the config
> file.  So things have improved, but there still is something broken ...

Thank you for picking this up!

My local grub.efi (built from source) does nothing with 
EFI_PXE_BASE_CODE_PROTOCOL except retrieve the cached DHCP packets.  I 
confirmed that it was doing this by typing "net_ls_addr" within the GRUB 
shell, before instructing GRUB to attempt DHCP.  With iPXE's 
EFI_PXE_BASE_CODE_PROTOCOL enabled, grub.efi did show the correct IP 
address even before attempting DHCP; without iPXE's 
EFI_PXE_BASE_CODE_PROTOCOL, it did not.

I also verified that grub.efi was able to use the exposed 
EFI_SIMPLE_NETWORK_PROTOCOL NIC by typing "net_bootp" within the GRUB 
shell.  This was able to successfully obtain a new DHCP lease.

I find GRUB2 difficult to work with since it seems not to support manual 
creation of configuration files.  Do you have a known-working grub.efi 
configuration (DHCP options, configuration files, etc) that you could 
send me so I can reproduce the problem?

Thanks,

Michael

  reply	other threads:[~2015-09-07 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 10:14 [Qemu-devel] EFI_PXE_BASE_CODE_PROTOCOL Gerd Hoffmann
2015-09-07 14:02 ` Michael Brown [this message]
2015-09-07 14:58   ` [Qemu-devel] [ipxe-devel] EFI_PXE_BASE_CODE_PROTOCOL Gerd Hoffmann
2015-09-10 15:07     ` Michael Brown
2015-09-10 15:20       ` Gerd Hoffmann
2015-09-10 15:29         ` Michael Brown
2015-09-11  8:56           ` Gerd Hoffmann
2015-10-20  8:16             ` Gerd Hoffmann
2015-10-26  0:14               ` Michael Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55ED98EA.4060101@ipxe.org \
    --to=mcb30@ipxe.org \
    --cc=ipxe-devel@ipxe.org \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).