qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC


From: Yongjie Ren
Subject: [Qemu-devel] [Bug 1182716] Re: guest cannot boot up when Intel 82572 NIC assigned
Date: Fri, 14 Jun 2013 09:18:32 -0000

Re-tested this bug with:
kvm.git(next tree):e47a5f5fb715b90b40747e9e235de557c6abd56c
qemu-kvm.git(uq/master tree): 199472259a41677417fb7de168bd8c589383c6de
This bug has been fixed. 

** Changed in: qemu
       Status: New => Fix Committed

** Changed in: qemu
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182716

Title:
  guest cannot boot up when Intel 82572 NIC assigned

Status in QEMU:
  Fix Released

Bug description:
  Environment:
  ------------
  Host OS (ia32/ia32e/IA64):ia32e
  Guest OS (ia32/ia32e/IA64):ia32e
  Guest OS Type (Linux/Windows):linux
  kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3
  qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec
  Host Kernel Version:3.9.0-rc3
  Hardware: IvyBridge-EP

  
  Bug detailed description:
  --------------------------
  When creating a guest with Intel 82572 NIC (e1000e driver) assigned, I will 
get "Invalid ROM contents" error  and the guest cannot boot up.
  This should be a qemu-kvm bug.
  kvm      + qemu-kvm   =  result
  660696d1 + 9953f882   =  bad
  660696d1 + 5098699a   =  good

  note: 
  1. when creating guest with assign a PF of Intel 72576 or Intel I350 (igb 
driver), the PF works fine in guest.
  2. when creating guest with assign a VF of Intel 72576 or Intel I350 or Intel 
82599, the VF works fine in guest.


  Reproduce steps:
  ----------------
  1. start up a host with kvm (commit: 660696d1)
  2. ./pcistub.sh -h 07:00.0   ( to hide a device)
  3. qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device 
pci-assign,host=07:00.0 -net none rhel6u4.img

  Current result:
  ----------------
  the guest cannot boot up.
  address@hidden ~]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -device 
pci-assign,host=07:00.0 -net none /root/rhel6u4.img
  qemu-system-x86_64: -device pci-assign,host=07:00.0: pci-assign: Cannot read 
from host /sys/bus/pci/devices/0000:07:00.0/rom
  Device option ROM contents are probably invalid (check dmesg).
  Skip option ROM probe with rombar=0, or load from file with romfile=
  Segmentation fault (core dumped)

  
  Expected result:
  ----------------
  the guest can boot up, and the device works fine in guest.

  Basic root-causing log:  (some log in 'dmesg')
  ----------------------
  assign device 0:7:0.0
  pci-stub 0000:07:00.0: Invalid ROM contents
  qemu-system-x86[6977]: segfault at 7f59afbffff8 ip 00007f59fe9f46ec sp
  00007fff85f17aa8 error 4 in libc-2.12.so[7f59fe979000+18a000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1182716/+subscriptions



reply via email to

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