From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rose, Gregory V" Subject: RE: SR-IOV problems - HVM cannot access network Date: Tue, 1 Mar 2011 14:41:32 -0800 Message-ID: <43F901BD926A4E43B106BF17856F0755013E8C7783@orsmsx508.amr.corp.intel.com> References: <4D6D49A3.90902@speakeasy.net> <43F901BD926A4E43B106BF17856F0755013E8C762B@orsmsx508.amr.corp.intel.com> <4D6D6C86.10301@speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4D6D6C86.10301@speakeasy.net> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: David White Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org > -----Original Message----- > From: David White [mailto:dwhite@speakeasy.net] > Sent: Tuesday, March 01, 2011 2:05 PM > To: Rose, Gregory V > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] SR-IOV problems - HVM cannot access network >=20 [snip} >=20 > The guest driver does not seem to be the source of this difference, > since these qemu logs are logged before HVM grub menu appears (and hence > before guest kernel is loaded) >=20 > Why would a physical function invoke MSI-X but not a virtual function? A lot of reasons actually :-). SR-IOV is a complete platform solution and = feature. It requires full support from all PCIe devices from the root comp= lex to the endpoint device as well as proper BIOS programming and OS suppor= t. I don't know that Ubuntu actually supports SR-IOV and I don't know which pl= atform you're using and whether it supports SR-IOV. > Is it something that pciback is doing? >=20 > When I bind a PF to pciback, the xen-pciback driver shows: > [ 1390.090693] pciback 0000:04:00.1: seizing device > [ 1390.095417] xen_allocate_pirq: returning irq 17 for gsi 17 > [ 1390.101021] Already setup the GSI :17 > [ 1390.104717] pciback 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> > IRQ 17 > [ 1390.111807] pciback 0000:04:00.1: PCI INT B disabled >=20 > but when I bind a VF to pciback, the driver shows: > [ 1439.411763] pciback 0000:04:10.0: seizing device > [ 1439.416462] pciback 0000:04:10.0: enabling device (0000 -> 0002) >=20 > (note no INT or GSI messages) >=20 > could pciback be the source of the HVM INTx problem? Well it's certainly possible but another good possibility is that the machi= ne doesn't actually implement the SR-IOV feature correctly in the BIOS. Wh= at machine are you using? Is there a BIOS setting to enable SR-IOV and if = so are you sure you've enabled it? Also, would it be possible to get a register dump of the VF device from bot= h the Dom0 host domain and the DomU guest domain using the Intel ethregs ut= ility? You can get that from source forge. - Greg