From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Direct guest device access from nested guest
Date: Wed, 28 Aug 2013 18:48:53 +0200 [thread overview]
Message-ID: <521E29F5.3070000@siemens.com> (raw)
In-Reply-To: <87sixtsxdj.fsf@fimbulvetr.bsc.es>
On 2013-08-28 16:28, Lluís Vilanova wrote:
> Hi,
>
> I want to get the following setup, but don't know how (or if it's even
> possible):
>
> * A guest VM with two AHCI controllers, with one device each. One of the AHCI
> controllers provides the VM's disk ("system"), while the other provides
> another disk ("nested") and uses a different emulation driver in QEMU (ahci2):
>
> host$ qemu-system-x86_64 -enable-kvm \
> -drive id=system,file=system.img,if=none \
> -device ahci,id=ahci \
> -device ide-drive,drive=system,bus=ahci.0 \
> -drive id=nested,file=nested.img,if=none \
> -device ahci2,id=ahci2 \
> -device ide-drive,drive=nested,bus=ahci2.0
>
> * A nested guest VM using the guest's (its host) AHCI2 controller.
>
> I've tried assigning the AHCI2 device to the nested guest using "pci-assign"
> and "vfio", but without any luck.
>
> The culprit of the problem seems to be I cannot get the nested guest to have
> an IOMMU.
>
> Is it possible to give a nested guest direct access to a device on the guest?
> (more specifically, an AHCI controller).
Nope, we are lacking support for emulating or (securely) forwarding
VT-d/IOMMU features to the first level guest. Would be cool to have,
just not yet there. But I've talked to Intel people recently, and they
are considering to support some nested VT-d with KVM.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-08-28 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 14:28 [Qemu-devel] Direct guest device access from nested guest Lluís Vilanova
2013-08-28 16:48 ` Jan Kiszka [this message]
2013-08-28 18:12 ` Lluís Vilanova
2013-08-28 18:18 ` Jan Kiszka
2013-08-28 19:18 ` Lluís Vilanova
2013-08-29 22:55 ` Aaron Fabbri
2013-08-29 22:58 ` [Qemu-devel] Fwd: " Aaron Fabbri
2013-08-30 5:27 ` [Qemu-devel] " Muli Ben-Yehuda
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=521E29F5.3070000@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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;
as well as URLs for NNTP newsgroup(s).