All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Kenni Lund <kenni@kelu.dk>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Brian Jackson <iggy@theiggy.com>,
	Yigal Korman <ykorman@gmail.com>,
	kvm@vger.kernel.org
Subject: Re: PCIe device pass-through - No IOMMU, Failed to deassign device error
Date: Mon, 25 Jan 2010 17:43:44 -0800	[thread overview]
Message-ID: <20100126014344.GC13518@sequoia.sous-sol.org> (raw)
In-Reply-To: <3b1f68ef1001251718n165edc96v138c4006a6ca37ae@mail.gmail.com>

* Kenni Lund (kenni@kelu.dk) wrote:
> 2010/1/26 Kenni Lund <kenni@kelu.dk>:
> > 2010/1/26 Chris Wright <chrisw@sous-sol.org>:
> >>
> >> Again, VT (or VT-x) isn't the same as VT-d.  So to be sure, you can
> >> grep dmesg for DMAR and IOMMU to verify that the chipset actually has
> >> VT-d support, that it's enabled, and that it's not broken (there are
> >> quite a few broken BIOS out there that case the IOMMU to be unusable).
> >
> > dmesg | egrep (DMAR|IOMMU)
> > This information should _really_ be added to the wiki at
> > http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
> >
> > Knowing this, it's quite easy for a user to determine if his system
> > has VT-d support, _before_ following the guide, compiling own kernel,
> > setting up qemu-kvm, unbinding and rebinding PCI devices, just to have
> > qemu-kvm 0.12.2 tell him that the system has no IOMMU (much better
> > than 0.12.1, agreed, but it's a bit late in the process to find out
> > :))
> 
> Doh, I didn't consider if the kernel compilation probably were needed
> to give any output - nevertheless, I still think this should be added
> to the wiki, even if it's the case. Perhaps a short text describing
> what you should look for.

Sure, I added a short snippet.

thanks,
-chris

  reply	other threads:[~2010-01-26  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ebd70761001230316v3615a3cas97645682460ef04e@mail.gmail.com>
2010-01-23 11:20 ` PCIe device pass-through - No IOMMU, Failed to deassign device error Yigal Korman
2010-01-23 19:10   ` Brian Jackson
2010-01-26  0:07     ` Chris Wright
2010-01-26  1:11       ` Kenni Lund
2010-01-26  1:18         ` Kenni Lund
2010-01-26  1:43           ` Chris Wright [this message]
2010-01-26  6:23         ` Avi Kivity
2010-01-26 21:19           ` Yigal Korman

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=20100126014344.GC13518@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=iggy@theiggy.com \
    --cc=kenni@kelu.dk \
    --cc=kvm@vger.kernel.org \
    --cc=ykorman@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.