All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: Direct guest device access from nested guest
Date: Wed, 28 Aug 2013 21:12:36 +0300	[thread overview]
Message-ID: <87ppsxelbf.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <521E29F5.3070000@siemens.com> (Jan Kiszka's message of "Wed, 28 Aug 2013 18:48:53 +0200")

Jan Kiszka writes:
[...]
>> 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.

Thanks a lot. I've been told there's some patches floating around to add such
support, but I suppose they've been long outdated and only work as POCs.


Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth

WARNING: multiple messages have this Message-ID (diff)
From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Jan Kiszka <jan.kiszka@siemens.com>
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 21:12:36 +0300	[thread overview]
Message-ID: <87ppsxelbf.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <521E29F5.3070000@siemens.com> (Jan Kiszka's message of "Wed, 28 Aug 2013 18:48:53 +0200")

Jan Kiszka writes:
[...]
>> 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.

Thanks a lot. I've been told there's some patches floating around to add such
support, but I suppose they've been long outdated and only work as POCs.


Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth

  reply	other threads:[~2013-08-28 18:12 UTC|newest]

Thread overview: 14+ 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
2013-08-28 16:48   ` [Qemu-devel] " Jan Kiszka
2013-08-28 18:12   ` Lluís Vilanova [this message]
2013-08-28 18:12     ` Lluís Vilanova
2013-08-28 18:18     ` Jan Kiszka
2013-08-28 18:18       ` [Qemu-devel] " Jan Kiszka
2013-08-28 19:18       ` Lluís Vilanova
2013-08-29 22:55         ` Aaron Fabbri
2013-08-29 22:55           ` [Qemu-devel] " Aaron Fabbri
2013-08-29 22:58           ` Fwd: " Aaron Fabbri
2013-08-29 22:58             ` [Qemu-devel] Fwd: " Aaron Fabbri
2013-08-30  5:27           ` [Qemu-devel] " Muli Ben-Yehuda
2013-08-30  5:27             ` 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=87ppsxelbf.fsf@fimbulvetr.bsc.es \
    --to=vilanova@ac.upc.edu \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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 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.