public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: David Brown <dmlb2000@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm pci passthrough
Date: Thu, 30 Oct 2008 14:26:50 +0200	[thread overview]
Message-ID: <20081030122650.GI7208@il.ibm.com> (raw)
In-Reply-To: <9c21eeae0810291744x7f59c17y27cbbda759080308@mail.gmail.com>

On Wed, Oct 29, 2008 at 05:44:54PM -0700, David Brown wrote:

> I was wondering what the status of kvm pci passthrough is?
> Especially the kind where I don't have vt-d? Where are the parts to
> play with? Is there any documentation you can point me to?

Hi David,

The kind where you *do* have VT-d is now included in the kernel and
userspace trees, and should "just work" (tell us if it doesn't). You
should clone the kernel and userspace trees, verify that the device
assignment patches are included in the userspace tree (they were
applied just now and may take some time to sync) and then run the
guest with:

-pcidevice host=bus:dev.func

Where the bus, dev, and func are what lspci shows you for the device
(on the host). You should also make sure that the device isn't used by
any driver on the host first.

For the other kinds (pvdma-without-iommu and reserved mem) I don't
know of the latest status.

Cheers,
Muli
-- 
The First Workshop on I/O Virtualization (WIOV '08)
Dec 2008, San Diego, CA, http://www.usenix.org/wiov08/
                       <->
SYSTOR 2009---The Israeli Experimental Systems Conference
http://www.haifa.il.ibm.com/conferences/systor2009/

  reply	other threads:[~2008-10-30 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  0:44 kvm pci passthrough David Brown
2008-10-30 12:26 ` Muli Ben-Yehuda [this message]
2008-10-30 15:42   ` David Brown
2008-10-30 16:09     ` Muli Ben-Yehuda
2008-11-04 22:20   ` Chris Jones
2008-11-05  5:36     ` Amit Shah
     [not found] <1242916455.20551277.1386180154132.JavaMail.zimbra@innovot.com>
2013-12-04 18:08 ` KVM & PCI Passthrough Phil Daws
2013-12-04 18:46   ` Alex Williamson
2013-12-04 19:09     ` Phil Daws

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=20081030122650.GI7208@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=dmlb2000@gmail.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