From: "Jan Beulich" <JBeulich@novell.com>
To: Robert Dunkley <Robert@saq.co.uk>
Cc: xen-devel@lists.xensource.com
Subject: RE: SR-IOV, Paravirt Guest fails to obtain IRQ after first boot
Date: Thu, 17 Mar 2011 14:00:01 +0000 [thread overview]
Message-ID: <4D8221F10200007800037170@vpn.id2.novell.com> (raw)
In-Reply-To: <C1EAC9C5E752D24C968FF091D446D823995C08@ALTERNATEREALIT>
>>> On 17.03.11 at 13:56, "Robert Dunkley" <Robert@saq.co.uk> 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).
Jan
next prev parent reply other threads:[~2011-03-17 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 17:16 SR-IOV, Paravirt Guest fails to obtain IRQ after first boot Robert Dunkley
2011-03-17 10:20 ` Jan Beulich
2011-03-17 12:56 ` Robert Dunkley
2011-03-17 14:00 ` Jan Beulich [this message]
2011-03-17 20:42 ` Pasi Kärkkäinen
2011-03-18 8:11 ` SR-IOV, Paravirt Guest fails to obtain IRQ afterfirst boot Robert Dunkley
2011-03-18 10:52 ` Robert Dunkley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8221F10200007800037170@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Robert@saq.co.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).