Added e1000-devel list to see whether this's a known issue.
Best Regards,
Yongjie (Jay)
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of [email protected]
> Sent: Monday, April 22, 2013 10:41 PM
> To: [email protected]
> Subject: [Bug 56981] New: [SR-IOV] Intel I350 NIC VF cannot work in a
> Windows 2008 guest.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=56981
>
> Summary: [SR-IOV] Intel I350 NIC VF cannot work in a
> Windows
> 2008 guest.
> Product: Virtualization
> Version: unspecified
> Kernel Version: 3.9.0-rc3
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: kvm
> AssignedTo: [email protected]
> ReportedBy: [email protected]
> Regression: No
>
>
> 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
>
> --
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are watching the assignee of the bug.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
