WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ after first b

To: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ after first boot
From: "Robert Dunkley" <Robert@xxxxxxxxx>
Date: Thu, 17 Mar 2011 12:56:08 -0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 17 Mar 2011 05:56:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1EAC9C5E752D24C968FF091D446D823995BD4@ALTERNATEREALIT> <4D81EE890200007800037068@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvkjNoscsl+uL68TtCumq0SLMdBKAACCYzg
Thread-topic: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ after first boot
Hi Jan,

Centos 5.5 with 2.6.18-247 RHEL kernel with iommu=pv and the 820 red hat
settings among others. Default Centos 5.5 kernel doesn't detect any VF
PCI deviavirt VM. Centos 5.5 with 247 kernel detects and works
perfectly first boot but any subsequent boot gives  error as below:
msix entry 0 for dev 09:10:0 are
not freed before acquire again.
msix entry 1 for dev 09:10:0 are
not freed before acquire again.
msix entry 2 for dev 09:10:0 are
not freed before acquire again.

HVMs are fine with either kernel.

Can you give me any idea where the problem might be? Could this be a
bios ACPI type issue?


Thanks,

Rob


Below is an xmdmesg extract:
[root@missplendid xenvmconfig]# xm dmesg | grep iommu
(XEN) Command line: apic_verbosity=debug dom0_mem=2048M dom0_max_vcpus=1
numa=on guest_loglvl=debug iommu=pv msi=1
(XEN) [VT-D]iommu.c:1731:d32767 DMAR: Forcing write-buffer flush
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 0:0.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:13.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:14.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:14.1
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:14.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:14.3
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.1
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.2
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.3
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.4
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.5
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.6
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf =
0:16.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.4
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.5
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.6
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 1:0.7
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 2:0.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 4:0.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 5:0.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 5:0.1
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 7:0.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 7:0.1
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 9:0.0
(XEN) [VT-D]iommu.c:1233:d32767 domain_context_mapping:PCIe: bdf = 9:0.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:0.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:0.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.4
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:2.5
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:3.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:3.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:3.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:3.4
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:4.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:4.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:4.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:4.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:5.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:5.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:5.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:5.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:6.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:6.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:6.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = ff:6.3
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1240:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.0
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.2
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.4
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.6
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.0
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.2
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.4
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.1
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.3
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.5
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:10.7
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.1
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.3
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 9:11.5
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.0
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.2
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.4
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.6
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.0
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.2
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.4
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.1
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.3
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.5
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:10.7
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.1
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.3
(XEN) [VT-D]iommu.c:1233:d0 domain_context_mapping:PCIe: bdf = 5:11.5


-----Original Message-----
From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx] 
Sent: 17 March 2011 10:21
To: Robert Dunkley
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ
after first boot

>>> On 16.03.11 at 18:16, "Robert Dunkley" <Robert@xxxxxxxxx> wrote:
> Hi Everyone,
> 
> 
> 
> I was wondering if there is a known fix for this issue? HVMs are fine.
> 
> I'm using the IGB driver and after guest reboot and xm destroy and 
> create I get the following error:
> msix entry 0 for dev 05:10:0 are
> not freed before acquire again.
> msix entry 1 for dev 05:10:0 are
> not freed before acquire again.
> msix entry 2 for dev 05:10:0 are
> not freed before acquire again.
> msix entry 0 for dev 09:10:0 are
> not freed before acquire again.
> msix entry 1 for dev 09:10:0 are
> not freed before acquire again.
> msix entry 2 for dev 09:10:0 are
> not freed before acquire again.

You didn't say what kernel you use.

Jan


The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. 
services to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit : 
Backups : Managed Networks : Remote Support.

ISPA Member

Member


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel