Bug 694417 - [SR-IOV] Can not generate virtual functions using 82576 *2 ports* NIC card
Summary: [SR-IOV] Can not generate virtual functions using 82576 *2 ports* NIC card
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-07 10:06 UTC by koka xiong
Modified: 2011-04-12 04:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-12 04:57:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description koka xiong 2011-04-07 10:06:14 UTC
Description of problem:
I want to test SR-IOV with a 82576 NIC card. But, unfortunately failed to
generate virtual functions.
The install tree of my host:
http://download.englab.nay.redhat.com/pub/rhel/nightly/RHEL5.7-Server-20110330.1.n/tree-x86_64/

Version-Release number of selected component (if applicable):
kvm-83-229.el5
libvirt-0.8.2-18.el5
kernel-2.6.18-252.el5


How reproducible:
100%


Steps to Reproduce:
1.Enable VT-d and VT-x in an Intel host and make sure there is a 82576 NIC card
available.
2.Issue command in the terminal: #rmmod igb, modprobe igb max_vfs=1
3.#lspci | grep 82576

Actual results:
No virtual function generated.

Expected results:
Can generate virtual function.


Additional info:
It is supported on RHEL5.6 before,but when I now test this on the nightly build 5.7,the VF can't be generated now.

Comment 1 dyuan 2011-04-08 11:01:14 UTC
Could you please paste the related log in /var/log/messages and then check it with the kernel version in 5.6 release os tree ?

Comment 2 wangyimiao 2011-04-12 04:57:32 UTC
After reinstall that tree and can not reproduce that problem.

Version-Release number of selected component :
kvm-83-229.el5
libvirt-0.8.2-18.el5
kernel-2.6.18-252.el5


Note You need to log in before you can comment on or make changes to this bug.