[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ afterfirst boot
Hi Jan, I just wanted to let you know that I applied you patch to pciback and it partially fixes the problem. It seems to me that the Redhat paravirt VM is not properly detaching itself from the VF on clean shutdown or reboot. Redhat have responded and here is the message I left them: I've just finished building pciback from the 247 kernel source with the patch. The patch applied cleanly and partially fixes the problem. Abrupt paravirt VM restart is now OK (eg. xm destroy testvm && xm create testvm now works) Clean restart or clean shutdown of the VM and then xm create of VM still shows the problem. Additional information is appearing in Dom console when the failures occur, the VM has 2 Intel 82576 VF assignments from 2 different Intel 82576 lan chips and the increased info in dom0 console looks like this: 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. unmap irq ff failed unmap irq fe failed unmap irq fd failed unmap irq fc failed unmap irq fb failed unmap irq fa failed What is responsible for un-assigning the MSIX IRQ when the VM is shutdown or rebooted? I'm using the igbvf driver that is included with the 247 kernel. Thanks, Rob Dunkley -----Original Message----- From: Pasi Kärkkäinen [mailto:pasik@xxxxxx] Sent: 17 March 2011 20:43 To: Jan Beulich Cc: Robert Dunkley; xen-devel@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-devel] SR-IOV, Paravirt Guest fails to obtain IRQ afterfirst boot On Thu, Mar 17, 2011 at 02:00:01PM +0000, Jan Beulich wrote: > >>> On 17.03.11 at 13:56, "Robert Dunkley" <Robert@xxxxxxxxx> wrote: > > 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? > > Quite possibly your kernel is missing c/s 1070:2994d2997f9d > (http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/rev/2994d2997f9d). > Robert: Want to open RHEL5 bugzilla entry about this issue? -- Pasi 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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |