From: ewheeler <kvm@ew.ewheeler.org>
To: kvm@vger.kernel.org
Subject: KVM + VTd on a DX58SO reports No IOMMU found.
Date: Mon, 28 Jun 2010 21:49:11 -0700 [thread overview]
Message-ID: <1277786951.14444.13.camel@geektop> (raw)
Hello,
I have been scouring mailing lists, the wiki, and talked with iggy on
freenode/#kvm who suggested that I ask on the list. KVM reports that I
do not have an IOMMU, however, dmesg reports both DMAR and IOMMU. In
addition, I know that this board supports VT-d.
Something of note, "ldd qemu-system-x86_64" does not list libpci.x.so,
however, configure reports that kvm-device-assignemnt is enabled.
I have tried using today's git tree and the 0.12.3 that ships with
Ubuntu 10.04 using 2.6.35-6-server and 2.6.34-5-server.
Any information you can offer to help would be greatly appreciated.
Specific details are available here:
http://pastebin.com/dp1tb5bf
Cheers,
Eric
--
www.PortLandLinuxSupport.com
next reply other threads:[~2010-06-29 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 4:49 ewheeler [this message]
2010-06-29 9:42 ` KVM + VTd on a DX58SO reports No IOMMU found Avi Kivity
2010-06-29 14:11 ` ewheeler
2010-06-29 14:49 ` Avi Kivity
2010-06-29 14:53 ` ewheeler
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=1277786951.14444.13.camel@geektop \
--to=kvm@ew.ewheeler.org \
--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