* [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr="
@ 2011-08-21 15:23 Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Yongjie Ren @ 2011-08-21 15:23 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Environment:
------------
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel Version:3.0.0+
Hardware: Westmere-EP platform
Bug detailed description:
--------------------------
SR-IOV VF NIC doesn't work in guest when not pinned pci address with "addr=x05". Guest's dmesg shows "Failed to initialize MSI-X interrupts." If not pinned an address with "addr=0x05", the VF will be pinned to "0000:00:03.0" by default, and that doesn't work.
Normal vtd NIC assignment doesn't have this issue.
commit:fda19064e of qemu-kvm.git is good.
commit:44755ea36 of qemu-kvm.git is bad with this issue.
There maybe something wrong between the two commit.
Here's some dmesg info in the guest.
----dmesg in guest------
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
igbvf 0000:00:03.0: setting latency timer to 64
igbvf 0000:00:03.0: Failed to initialize MSI-X interrupts.
igbvf 0000:00:03.0: Intel(R) 82576 Virtual Function
igbvf 0000:00:03.0: Address: da:66:bb:e6:1e:f4
igbvf 0000:00:03.0: MAC: 1
....
igbvf 0000:00:03.0: Unable to allocate interrupt, Error: -1
....
Reproduce steps:
----------------
1.pci-stub the a VF in 82576 NIC
2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow
(if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work)
3.check network in guest
Current result:
----------------
VF doesn't work in guest.
Expected result:
----------------
VF works well in guest.
** Affects: qemu-kvm
Importance: Undecided
Status: New
** Project changed: qemu => qemu-kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/830558
Title:
VF doesn't work in guest when not pinned with "addr="
Status in qemu-kvm:
New
Bug description:
Environment:
------------
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel Version:3.0.0+
Hardware: Westmere-EP platform
Bug detailed description:
--------------------------
SR-IOV VF NIC doesn't work in guest when not pinned pci address with "addr=x05". Guest's dmesg shows "Failed to initialize MSI-X interrupts." If not pinned an address with "addr=0x05", the VF will be pinned to "0000:00:03.0" by default, and that doesn't work.
Normal vtd NIC assignment doesn't have this issue.
commit:fda19064e of qemu-kvm.git is good.
commit:44755ea36 of qemu-kvm.git is bad with this issue.
There maybe something wrong between the two commit.
Here's some dmesg info in the guest.
----dmesg in guest------
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
igbvf 0000:00:03.0: setting latency timer to 64
igbvf 0000:00:03.0: Failed to initialize MSI-X interrupts.
igbvf 0000:00:03.0: Intel(R) 82576 Virtual Function
igbvf 0000:00:03.0: Address: da:66:bb:e6:1e:f4
igbvf 0000:00:03.0: MAC: 1
....
igbvf 0000:00:03.0: Unable to allocate interrupt, Error: -1
....
Reproduce steps:
----------------
1.pci-stub the a VF in 82576 NIC
2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow
(if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work)
3.check network in guest
Current result:
----------------
VF doesn't work in guest.
Expected result:
----------------
VF works well in guest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu-kvm/+bug/830558/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr="
2011-08-21 15:23 [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr=" Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
@ 2011-08-22 12:25 ` Launchpad Bug Tracker
2011-10-17 1:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
2 siblings, 0 replies; 4+ messages in thread
From: Launchpad Bug Tracker @ 2011-08-22 12:25 UTC (permalink / raw)
To: qemu-devel
You have been subscribed to a public bug:
Environment:
------------
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel Version:3.0.0+
Hardware: Westmere-EP platform
Bug detailed description:
--------------------------
SR-IOV VF NIC doesn't work in guest when not pinned pci address with "addr=x05". Guest's dmesg shows "Failed to initialize MSI-X interrupts." If not pinned an address with "addr=0x05", the VF will be pinned to "0000:00:03.0" by default, and that doesn't work.
Normal vtd NIC assignment doesn't have this issue.
commit:fda19064e of qemu-kvm.git is good.
commit:44755ea36 of qemu-kvm.git is bad with this issue.
There maybe something wrong between the two commit.
Here's some dmesg info in the guest.
----dmesg in guest------
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
igbvf 0000:00:03.0: setting latency timer to 64
igbvf 0000:00:03.0: Failed to initialize MSI-X interrupts.
igbvf 0000:00:03.0: Intel(R) 82576 Virtual Function
igbvf 0000:00:03.0: Address: da:66:bb:e6:1e:f4
igbvf 0000:00:03.0: MAC: 1
....
igbvf 0000:00:03.0: Unable to allocate interrupt, Error: -1
....
Reproduce steps:
----------------
1.pci-stub the a VF in 82576 NIC
2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow
(if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work)
3.check network in guest
Current result:
----------------
VF doesn't work in guest.
Expected result:
----------------
VF works well in guest.
** Affects: qemu
Importance: Undecided
Status: New
--
VF doesn't work in guest when not pinned with "addr="
https://bugs.launchpad.net/bugs/830558
You received this bug notification because you are a member of qemu-devel-ml, which is subscribed to QEMU.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] [Bug 830558] Re: VF doesn't work in guest when not pinned with "addr="
2011-08-21 15:23 [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr=" Yongjie Ren
@ 2011-08-22 12:25 ` Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] [NEW] " Launchpad Bug Tracker
2011-10-17 1:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
2 siblings, 0 replies; 4+ messages in thread
From: Yongjie Ren @ 2011-08-22 12:25 UTC (permalink / raw)
To: qemu-devel
** Project changed: qemu-kvm => qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/830558
Title:
VF doesn't work in guest when not pinned with "addr="
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 (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel Version:3.0.0+
Hardware: Westmere-EP platform
Bug detailed description:
--------------------------
SR-IOV VF NIC doesn't work in guest when not pinned pci address with "addr=x05". Guest's dmesg shows "Failed to initialize MSI-X interrupts." If not pinned an address with "addr=0x05", the VF will be pinned to "0000:00:03.0" by default, and that doesn't work.
Normal vtd NIC assignment doesn't have this issue.
commit:fda19064e of qemu-kvm.git is good.
commit:44755ea36 of qemu-kvm.git is bad with this issue.
There maybe something wrong between the two commit.
Here's some dmesg info in the guest.
----dmesg in guest------
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
igbvf 0000:00:03.0: setting latency timer to 64
igbvf 0000:00:03.0: Failed to initialize MSI-X interrupts.
igbvf 0000:00:03.0: Intel(R) 82576 Virtual Function
igbvf 0000:00:03.0: Address: da:66:bb:e6:1e:f4
igbvf 0000:00:03.0: MAC: 1
....
igbvf 0000:00:03.0: Unable to allocate interrupt, Error: -1
....
Reproduce steps:
----------------
1.pci-stub the a VF in 82576 NIC
2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow
(if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work)
3.check network in guest
Current result:
----------------
VF doesn't work in guest.
Expected result:
----------------
VF works well in guest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/830558/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] [Bug 830558] Re: VF doesn't work in guest when not pinned with "addr="
2011-08-21 15:23 [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr=" Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] [NEW] " Launchpad Bug Tracker
@ 2011-10-17 1:25 ` Yongjie Ren
2 siblings, 0 replies; 4+ messages in thread
From: Yongjie Ren @ 2011-10-17 1:25 UTC (permalink / raw)
To: qemu-devel
this bug doesn't exist in the latest qemu tree.
** Changed in: qemu
Status: New => 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/830558
Title:
VF doesn't work in guest when not pinned with "addr="
Status in QEMU:
Fix Released
Bug description:
Environment:
------------
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel Version:3.0.0+
Hardware: Westmere-EP platform
Bug detailed description:
--------------------------
SR-IOV VF NIC doesn't work in guest when not pinned pci address with "addr=x05". Guest's dmesg shows "Failed to initialize MSI-X interrupts." If not pinned an address with "addr=0x05", the VF will be pinned to "0000:00:03.0" by default, and that doesn't work.
Normal vtd NIC assignment doesn't have this issue.
commit:fda19064e of qemu-kvm.git is good.
commit:44755ea36 of qemu-kvm.git is bad with this issue.
There maybe something wrong between the two commit.
Here's some dmesg info in the guest.
----dmesg in guest------
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
igbvf 0000:00:03.0: setting latency timer to 64
igbvf 0000:00:03.0: Failed to initialize MSI-X interrupts.
igbvf 0000:00:03.0: Intel(R) 82576 Virtual Function
igbvf 0000:00:03.0: Address: da:66:bb:e6:1e:f4
igbvf 0000:00:03.0: MAC: 1
....
igbvf 0000:00:03.0: Unable to allocate interrupt, Error: -1
....
Reproduce steps:
----------------
1.pci-stub the a VF in 82576 NIC
2.create a guest: qemu-system-x86_64 -m 1024 -smp 2 -device pci-assign,host=01:10.0 -net none -hda /root/rhel6.qcow
(if using '-device pci-assign,host=01:10.0,addr=0x5, the VF will work)
3.check network in guest
Current result:
----------------
VF doesn't work in guest.
Expected result:
----------------
VF works well in guest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/830558/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-10-17 2:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-21 15:23 [Qemu-devel] [Bug 830558] [NEW] VF doesn't work in guest when not pinned with "addr=" Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
2011-08-22 12:25 ` [Qemu-devel] [Bug 830558] [NEW] " Launchpad Bug Tracker
2011-10-17 1:25 ` [Qemu-devel] [Bug 830558] " Yongjie Ren
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.