Bug 735931

Additional info:
This issue *doesn't* happen on 82576

(In reply to comment #0)
> Created attachment 521594 [details]
> intel 82576L nic card, lspci info
         ^^^^^^
should be intel 82574L nic card

Created attachment 521597 [details]
boot menu

Created attachment 521598 [details]
press "1" to boot from disk

Created attachment 521600 [details]
hang at booting from pxe

It looks like the guest is loading an option ROM from the NIC. I don't know if there's a way to disable that in the hardware itself or on some device-assignment command-line option. Reassigning to Don so he can take a look.

Is the qemu-kvm cmdline handcrafted, or is it the log of what virsh create generates with a defined guest.xml ?

Please provide guest.xml definition file (virsh dumpxml <guestname>).

rombar=0 option for pci-assign will skip loading the physical option rom.

Well, I see this in the cmdline too:

-boot order=c

maybe it should be =1 or =0 ?

(In reply to comment #8)
> Is the qemu-kvm cmdline handcrafted, or is it the log of what virsh create
> generates with a defined guest.xml ?
> 
> Please provide guest.xml definition file (virsh dumpxml <guestname>).

It is handcrafted.

(In reply to comment #9)
> rombar=0 option for pci-assign will skip loading the physical option rom.

Yes, after adding rombar=0, this issue disappeared

(In reply to comment #10)
> Well, I see this in the cmdline too:
> 
> -boot order=c
> 
> maybe it should be =1 or =0 ?

I don't follow you here, what do you mean?

Look at the qemu-kvm cmdline you provided in Description:

# /usr/libexec/qemu-kvm -M rhel6.2.0 -enable-kvm -m 4096 -smp
4,sockets=1,cores=4,threads=1 -name rhel6.1.z -uuid `uuidgen` -rtc
base=utc,clock=host,driftfix=slew -boot order=c,menu=on -drive
                                  ^^^^^^^^^^^^^


setting boot order to 'c'; shouldn't it set it to the order number,
which would be 1 if it starts counting at 1, or 0 if 0-based indexing
used.

I removed "order=c" option, and added "bootindex=1" to disk image, issue exists

for my sanity, could your provide the entire qemu-kvm cmdline used to start the guest? thanks.

(In reply to comment #16)
> for my sanity, could your provide the entire qemu-kvm cmdline used to start the
> guest? thanks.

# /usr/libexec/qemu-kvm -M rhel6.2.0 -enable-kvm -m 4096 -smp 4,sockets=1,cores=4,threads=1 -name rhel6.1.z -uuid `uuidgen` -rtc base=utc,clock=host,driftfix=slew -boot menu=on -drive file=/root/rhel6.1.z-x86_64.qcow2,if=none,id=drive-virtio-0-0,media=disk,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio-0-0,id=virt0-0-0,bootindex=1 -net none -usb -device usb-tablet,id=input1 -spice port=9000,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -monitor stdio -balloon none -device driver=pci-assign,host=06:00.0,id=hostnet1,iommu=1

c#9 and c#12 list the solution -- rombar=0 must be added.

If reporter agrees, please close this bz;
if not, please indicate why it does not.

According to Comment #12, closing as WORKSFORME