[Qemu-devel] [Bug 799036] Re: NIC assignment order in command line make some NIC can't work

[Yongjie Ren]

Without fixing address of the device, the first device will get 00:03.0 in my 
guest, and the second get 00:04.0.
And when NIC 82576 is in the first order, it will get 00:03.0 in my guest, and 
it will not working.
If I fix 82576 NIC using "addr=0x3" and other using "addr=0x4", 82576 NIC in 
guest will get 00:03.0 and the other will get 04:00.0.
If fixing address, the assignment order doestn't matter the result.  With 
"addr=0x3", NIC 82576 always works well in guest; but with "addr=0x4", 82580 or 
some other NIC will work well in my guest.

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

Title:
  NIC assignment order in command line make some NIC can't work

Status in QEMU:
  New

Bug description:
  Environment:
  ------------
  Host OS (ia32/ia32e/IA64):All
  Guest OS (ia32/ia32e/IA64):ia32e
  Guest OS Type (Linux/Windows):Linux 
  kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158
  qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349
  Host Kernel Version:3.0.0-rc2+
  Hardware: Westmere-EP platform

  Bug detailed description:
  --------------------------
  When using qemu-system-x86_64 to create a linux guest with a 82586 NIC and a 
82572EI NIC statically assigned, the two NIC's order in command line may make 
82586 NIC can't work in guest.
  command1: qemu-system-x86_64  -m 1024 -smp 2  -device pci-assign,host=0e:00.1 
-device pci-assign,host=0c:00.0 -net none -hda qcow-rhel6.img
  command2: qemu-system-x86_64  -m 1024 -smp 2  -device pci-assign,host=0c:00.0 
-device pci-assign,host=0e:00.1 -net none -hda qcow-rhel6.img
  Using command1 to create a guest, both two NICs works well in guest.
  While using command2 to create a guest, 82576(kawela) NIC 0c:00.0 cannot get 
IP in guest.
  BDF 0c:00.0 is a 82576(kawela) NIC, while BDF 0e:00.1 is 82572EI NIC.
  The only difference of the two command lines is the order of NICs assignment. 
  And only the 82576(kawela) NIC have this problem, the other one 82572EI 
always works well.
  And sriov VF doesn't have this issue.  A VF and a 82576 PF assigned to a 
guest always work well.
  I don't know the order of NIC assignment in qemu-system-x86_64 will make this 
difference in guest. Maybe it's a qemu bug ?

  Reproduce steps:
  ----------------
  1.pci-stub the two NIC
  2.create a guest: qemu-system-x86_64  -m 1024 -smp 2  -device
  pci-assign,host=0c:00.0 -device pci-assign,host=0e:00.1 -net none -hda
  qcow-rhel6.img
  (0c:00.0 is a 82576 NIC, and 0e:00.1 is another NIC).

  
  Current result:
  ----------------
  82576 PF and the other NIC in guest will work well regardless of what the 
order of assignment is.

  Expected result:
  ----------------

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