Bug 56981

Summary:	[SR-IOV] Intel I350 NIC VF cannot work in a Windows 2008 guest.
Product:	Virtualization	Reporter:	Jay Ren (yongjie.ren)
Component:	kvm	Assignee:	virtualization_kvm
Status:	CLOSED INVALID
Severity:	normal
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	3.9.0-rc3	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	lspci info of the igbvf in kvm host host dmesg

Description Jay Ren 2013-04-22 14:40:48 UTC

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Windows
kvm.git Commit:79558f112fc0352e057f7b5e158e3d88b8b62c60
qemu-kvm Commit:8912bdea01e8671e59fe0287314379be9c1f40ec
Host Kernel Version:3.9.0-rc3
Hardware: Sandy Bridge - EP


Bug detailed description:
--------------------------
The assigned Intel I350 NIC VF (a igbvf) cannot work in a Windows 2008 guest.

1. If the guest is Windows 7/8/2012 or RHEL6.x , the Intel I350 NIC VF can work fine in the guest.
2. Intel 82576 NIC VF (also igbvf) can work in a Windows 2008 guest.


Reproduce steps:
----------------
1. ./pcistub.sh -h 0b:10.0   ( to hide a device)
2. qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -device
pci-assign,host=0b:10.0 -net none -hda win2k8.img

Current result:
----------------
Intel I350 NIC VF cannot work in win2k8 guest

Expected result:
----------------
Intel I350 NIC VF can work in win2k8 guest

Comment 1 Jay Ren 2013-04-22 14:43:00 UTC

Created attachment 99661 [details]
lspci info of the igbvf in kvm host

Comment 2 Jay Ren 2013-04-22 14:43:25 UTC

Created attachment 99671 [details]
host dmesg

Comment 3 Jay Ren 2013-04-24 06:54:03 UTC

According to the message from Intel igb driver team, Windows 2008 is not supported by Intel I350 driver. I350 VF can work in Windows 2008 R2 (not Windows 2008).

So, I'll close this bug.