From: Anthony PERARD <anthony.perard@citrix.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: PXE boot with e1000 using OVMF
Date: Thu, 20 Sep 2018 12:33:42 +0100 [thread overview]
Message-ID: <20180920113342.GC2244@perard.uk.xensource.com> (raw)
In-Reply-To: <CABfawh=r2Y4nVPcgzSHBzk9Vg9UWQPdU-hQka0DaEbgvAX99+g@mail.gmail.com>
On Wed, Sep 19, 2018 at 11:04:22AM -0600, Tamas K Lengyel wrote:
> On Wed, Sep 19, 2018 at 10:36 AM Wei Liu <wei.liu2@citrix.com> wrote:
> >
> > On Wed, Sep 12, 2018 at 11:54:02AM -0600, Tamas K Lengyel wrote:
> > > HI all,
> > > I'm experimenting with OVMF and I checked to see if OVMF can do PXE
> > > boot out-of-the box with a e1000 emulated network interface and was
> > > surprised to find that it does not. After reading some of the prior
> > > discussions on the topic (https://lists.gt.net/xen/devel/382432 and
> > > https://lists.xenproject.org/archives/html/xen-users/2015-09/msg00059.html)
> > > I was able to get the menu options to show up by copying efi-e1000.rom
> > > that gets installed by Xen's QEMU build into the disk of the VM and
> > > then loading with loadpcirom manually in the EFI shell. From the prior
> > > discussions it sounds to me like this option rom should have been
> > > automatically served by QEMU to OVMF when the VM started as an
> > > OptionROM. So is this a bug or what's missing?
> >
> > Doesn't QEMU load the option ROM automatically when you specify e1000?
> >
> > I _think_ it loads option ROM automatically because I have seen complain
> > that if you configure too many emulated NICs the guest runs out of
> > memory.
>
> I compiled QEMU with DEBUG_PCI enabled in hw/pci/pci.c and then the
> log shows efi-e1000.rom being loaded. However, AFAICT since PCI
> enumeration is disabled in OVMF when running under Xen (I'm not
> exactly sure why) the option rom never gets executed as it only gets
It's because hvmloader (which is runned before OVMF start) takes care of
enumerating the PCI bus. OVMF only has to read the information:
via OvmfPkg/Library/PciHostBridgeLib/XenSupport.c
I can try to find out what's needed in order to load an option rom, or
ask on edk2-devel.
> called from the enumeration route
> (https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Bus/Pci/PciBusDxe/PciEnumerator.h#L63).
> At least that's my current understanding of how option roms work under
> OVMF.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-20 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 17:54 PXE boot with e1000 using OVMF Tamas K Lengyel
2018-09-19 16:36 ` Wei Liu
2018-09-19 17:04 ` Tamas K Lengyel
2018-09-20 11:33 ` Anthony PERARD [this message]
2018-09-20 13:58 ` Tamas K Lengyel
2018-09-20 16:08 ` Wei Liu
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=20180920113342.GC2244@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=tamas.k.lengyel@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).