qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE


From: Gerhard Wiesinger
Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE
Date: Sat, 7 Jan 2012 23:46:02 +0100 (CET)
User-agent: Alpine 2.02 (LFD 1266 2009-07-14)

On Sat, 7 Jan 2012, Kevin O'Connor wrote:

On Sat, Jan 07, 2012 at 09:35:55AM +0100, Gerhard Wiesinger wrote:
[...]
5. Legacy option rom
6. DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
7. iPXE (PCI 00:00.0)

But there is still the iPXE ROM there (I think I didn't see iPXE
because it is last one displayed and boot screen is fast and will be
cleared afterwards). So something must be wrong. @Gerd: any ideas?
[...]
Checking rom 0x000ce000 (sig aa55 size 17)
Searching bootorder for: /address@hidden/vapic.bin
pmm_malloc zone=0x0ffefe30 handle=ffffffff size=20 align=10 ret=0x0ffe1420 
(detail=0x0ffe1440)
Registering bootable: Legacy option rom (type:129 prio:101 data:ce000003)
Checking rom 0x000d0800 (sig aa55 size 5)
Searching bootorder for: /address@hidden/pxe-pcnet.rom
pmm_malloc zone=0x0ffefe30 handle=ffffffff size=20 align=10 ret=0x0ffe13d0 
(detail=0x0ffe13f0)
Registering bootable: iPXE (PCI 00:00.0) (type:128 prio:9999 data:d0800372)

The iPXE rom is coming from the "genroms" fw_cfg interface instead of
via the pci rom bar interface.  Also, the "legacy option rom" is from
the vapic.bin file (comfing from the same fw_cfg interface) - this rom
is something KVM sets up.

No NIC:
-net none
=> No iPXE ROM (correct).

but with the previously listed config no iPXE ROM should be there. Saw this is done through paravirtualization from Seabios/QEMU or KVM. So there must be a bug with the empty romfile options with net or device (I guess) in QEMU/KVM.

The vapic.bin is ok.

BTW: Will you integrate the boot one liner?

Ciao,
Gerhard

--
http://www.wiesinger.com/



reply via email to

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