From: Alex Williamson <alex.williamson@redhat.com>
To: Bruce Cran <bruce@cran.org.uk>
Cc: kvm@vger.kernel.org
Subject: Re: Problems using vfio pcie passthrough (pci-assign works)
Date: Thu, 02 Oct 2014 08:25:02 -0600 [thread overview]
Message-ID: <1412259902.7360.253.camel@ul30vt.home> (raw)
In-Reply-To: <542D55A4.6000005@cran.org.uk>
On Thu, 2014-10-02 at 07:39 -0600, Bruce Cran wrote:
> I have a PCIe card that's behind an Intel E3-1200 PCIe x16 controller
> bridge that I want to use in VMs: it works when using the pci-assign
> driver, but something goes wrong when trying to use vfio-pci - my driver
> in the guest gets so far through loading before failing to talk to the
> hardware, so I guess something's not being setup correctly. I'm
> wondering if this is a bug (do vfio and OVMF work together?) or a
> problem with the way I'm setting up vfio-pci. I'm using the script from
> http://www.linux-kvm.org/wiki/images/b/b4/2012-forum-VFIO.pdf page 30 to
> assign the card, but I know it's a fairly old document, and I'm running
> kernel 3.11 on openSUSE: is it still correct? Or should I not try to
> use vfio-pci for now?
What's the device you're trying to assign and the scripts you're using
to do so? vfio-pci is fully supported, but I'd recommend a kernel newer
than 3.11 (maybe a newer QEMU too, you didn't specify a version) unless
openSUSE is specifically pulling vfio features and fixes into their
distro. vfio does work with OVMF, most of the testing of this is with
GPU assignment. It does require an OVMF image built from a fairly
recent tree (not more than a few months old), but if you're getting into
the guest OS you're probably fine. Provide more details and I can try
to help. Thanks,
Alex
next prev parent reply other threads:[~2014-10-02 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 13:39 Problems using vfio pcie passthrough (pci-assign works) Bruce Cran
2014-10-02 14:25 ` Alex Williamson [this message]
2014-10-02 15:42 ` Bruce Cran
2014-10-02 15:54 ` Alex Williamson
2014-10-02 17:03 ` Bruce Cran
2014-10-02 17:05 ` Alex Williamson
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=1412259902.7360.253.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=bruce@cran.org.uk \
--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