From: Chris Wright <chrisw@sous-sol.org>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: pci-stub error and MSI-X for KVM guest
Date: Mon, 21 Dec 2009 11:19:23 -0800 [thread overview]
Message-ID: <20091221191923.GA5979@sequoia.sous-sol.org> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E6D718922FC@GVW1118EXC.americas.hpqcorp.net>
* Fischer, Anna (anna.fischer@hp.com) wrote:
> I am running Fedora Core 12 with a 2.6.31 kernel. I use the Intel
> 82576 SR-IOV network card and want to assign its Virtual Functions (VFs)
> to separate KVM guests. My guests also run Fedora Core 12 with a 2.6.31
> kernel. I use the latest igb driver in the host OS and load it with 2
> VFs activated. Then I assign those to my KVM guests. I use virt-manager
> to do this which then takes care of configuring pci-stub.
By 2.6.31 are you referring to the stock Fedora 12 kernel package?
> This works fine in principle and I can see the PCI device in the
> guest under lspci. However, the 82576 VF driver requires the OS
> to support MSI-X. My Fedora installation is configured with MSI-X,
> e.g. CONFIG_PCI_MSI is 'y'. When I load the driver it tells me it cannot
> initialize MSI-X for the device, and under /proc/interrupts I can see
> that MSI-X does not seem to work. Is this a KVM/QEMU limitation? It works
> for me when running the VF driver under a non-virtualized Linux system.
No, this should work fine. QEMU/KVM supports MSI-X to guest as well as
VFs.
> Also, when I do an lspci on the KVM guest, that is fine, but when I
> do an lspci -v then the guest crashes down. In the host OS under dmesg
> I can see this:
>
> pci-stub 0000:03:10.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100004)
>
> Is this a known issue? My qemu-kvm version is 2:0.11.0.
No, I've not seen the crash before. What do you mean "the guest crashes
down"?
This looks like a Fedora specific version (rpm version). Can you verify
this is from Fedora packages vs. upstream source? If it's Fedora,
would be useful to open a bug there.
thanks,
-chris
next prev parent reply other threads:[~2009-12-21 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 18:15 pci-stub error and MSI-X for KVM guest Fischer, Anna
2009-12-21 19:19 ` Chris Wright [this message]
2009-12-21 19:34 ` Fischer, Anna
2009-12-21 19:58 ` Chris Wright
2010-01-04 11:37 ` Fischer, Anna
2010-01-04 15:16 ` Chris Wright
2010-01-05 10:25 ` Fischer, Anna
2010-01-08 0:50 ` Chris Wright
2010-01-08 11:04 ` Daniel P. Berrange
2010-01-08 18:03 ` Chris Wright
2010-01-04 11:42 ` Fischer, Anna
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=20091221191923.GA5979@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=anna.fischer@hp.com \
--cc=kvm@vger.kernel.org \
/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