[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AB8F042.4030306@intel.com>
Date: Tue, 22 Sep 2009 08:41:54 -0700
From: Alexander Duyck <alexander.h.duyck@...el.com>
To: Chris Wright <chrisw@...s-sol.org>
CC: "Ronciak, John" <john.ronciak@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>
Subject: Re: igb VF allocation with quirk_i82576_sriov
Chris Wright wrote:
> Is this known to work? During recent virt testing for upcoming Fedora 12,
> a box w/out SR-IOV support in BIOS was using quirk to create VF BAR space,
> VF allocation worked enough to assign a device to the guest, but igbvf
> was not actually functioning properly in the guest.
>
> Is it worth debugging this further, or is it already a known issue?
You could be experiencing one of a couple different issues.
First when you say you started SR-IOV on a box w/out SR-IOV support I
assume you are using "pci=assign-busses" in order to reserve the bus
space for the VFs, is that correct? Also while your system may not
support SR-IOV does it at least support VT-d? Without VT-d support you
won't be able to assign a device to the guest.
My recommendations for further testing would be to test a VF on the host
kernel to see if that works. If it does then you could also try direct
assigning an entire port to see if that works. If the entire port
doesn't work then you probably don't have VT-d enabled.
Thanks,
Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists