From: Laszlo Ersek <lersek@redhat.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] pxe boot problems
Date: Wed, 29 Jan 2014 14:01:10 +0100 [thread overview]
Message-ID: <52E8FB96.2010801@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F755935FEE9@lisa.maurer-it.com>
On 01/29/14 12:49, Dietmar Maurer wrote:
> A bisect points to the following patch:
>
> # git bisect bad
> c45e5b5b30ac1f5505725a7b36e68cedfce4f01f is the first bad commit
> commit c45e5b5b30ac1f5505725a7b36e68cedfce4f01f
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date: Tue Feb 26 17:46:11 2013 +0100
>
> Switch to efi-enabled nic roms by default
>
> All PCI nics are switched to EFI-enabled roms by default. They are
> composed from three images (legacy, efi ia32 & efi x86), so classic
> pxe booting will continue to work.
>
> Exception: eepro100 is not switched, it uses a single rom for all
> emulated eepro100 variants, then goes patch the rom header on the
> fly with the correct PCI IDs. I doubt that will work as-is with
> the efi roms.
>
> Keep old roms for 1.4+older machine types via compat properties,
> needed because the efi-enabled roms are larger so the pci rom bar
> size would change.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
>
>
>> pxe boot does not work with qemu 1.7 (also tested with latest code from
>> master).
>>
>> # kvm -m 1024 -net nic -net tap
>>
>> simply hangs at:
>>
>> iPXE (PCI 00:03.0) starting execution.
>>
>> and I get the following output:
>>
>> # kvm -m 1024 -net nic -net tap
>> KVM: unknown exit, hardware reason 80000021
>> EAX=00000011 EBX=00000000 ECX=00000030 EDX=00007baa
>> ESI=c00e006a EDI=00098bf0 EBP=00000000 ESP=00007baa
>> EIP=00000215 EFL=00010006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
>> ES =0030 0009cf30 ffffffff 0000f300 DPL=3 DS16 [-WA]
>> CS =9c7c 0009c7e0 0000ffff 00009b00 DPL=0 CS16 [-RA]
>> SS =0000 00000000 0000ffff 00009300 DPL=0 DS16 [-WA]
>> DS =0030 0009cf30 ffffffff 0000f300 DPL=3 DS16 [-WA]
>> FS =0030 0009cf30 ffffffff 0000f300 DPL=3 DS16 [-WA]
>> GS =0030 0009cf30 ffffffff 0000f300 DPL=3 DS16 [-WA]
>> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
>> TR =0000 feffd000 00002088 00008b00 DPL=0 TSS32-busy
>> GDT= 0009cf40 00000037
>> IDT= 00000000 0000ffff
>> CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
>> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
>> DR3=0000000000000000
>> DR6=00000000ffff0ff0 DR7=0000000000000400
>> EFER=0000000000000000
>> Code=66 0f 01 16 10 00 66 0f 01 1e 48 00 0f 20 c0 0c 01 0f 22 c0 <66> ea a4 00
>> 00 00 08 00 0f 20 c0 24 fe 0f 22 c0 ff 2e 4e 00 2e a1 ac 06 8e d8 8e c0 8e e0
>>
>> this is using RHEL6 kernel 358.23.2.el6
>>
>> any ideas?
Does it work with TCG? If so, what host CPU do you have?
Also, can you try with a NIC model different from the default e1000?
Thanks
Laszlo
next prev parent reply other threads:[~2014-01-29 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 11:49 [Qemu-devel] pxe boot problems Dietmar Maurer
2014-01-29 13:01 ` Laszlo Ersek [this message]
2014-01-29 17:34 ` Laszlo Ersek
2014-01-29 17:47 ` Paolo Bonzini
2014-01-29 18:09 ` Laszlo Ersek
2014-01-29 18:13 ` Paolo Bonzini
2014-01-30 0:07 ` Laszlo Ersek
2014-01-30 6:37 ` Dietmar Maurer
2014-01-30 11:38 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2014-01-29 7:59 Dietmar Maurer
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=52E8FB96.2010801@redhat.com \
--to=lersek@redhat.com \
--cc=dietmar@proxmox.com \
--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).