From: Paolo Bonzini <pbonzini@redhat.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Lai Jiangshan <jiangshanlai+lkml@gmail.com>,
Juergen Gross <jgross@suse.com>,
Rusty Russell <rusty@rustcorp.com.au>,
lguest@lists.ozlabs.org, kvm@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] KVM PV
Date: Mon, 2 Oct 2017 14:17:54 +0200 [thread overview]
Message-ID: <4ba6c3a0-85cd-4297-b4ed-4b859b953345@redhat.com> (raw)
In-Reply-To: <CAFLBxZbU3G8bX6b1XMtFgmYHnQPJiJppUSSrqM7onea3UFaw7Q@mail.gmail.com>
On 02/10/2017 12:36, George Dunlap wrote:
>>> Although I'm not business man, I don't think the top cloud provider[s]
>>> would allow nested virtualization, however mature nested virtualization
>>> is. Even xen-pv is unable to be nested in the aws and azure.
>>
>> Check the contributors to KVM nested virtualization, you might be surprised.
>>
>> Nested Xen PV is not possible because the Xen hypervisor cannot run as a PV guest.>> It's a technical limitation.
>
> Minor correction: Xen can't run on AWS as a PV guest, but it can run
> as an L1 hypervisor inside any "fully virtualized" VM (as both AWS and
> Azure provide), and provide PV L2 guests.
Yes, that's what I meant.
Thanks George!
Paolo
next prev parent reply other threads:[~2017-10-02 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 15:47 KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support) Lai Jiangshan
2017-09-29 16:39 ` Paolo Bonzini
2017-09-30 0:04 ` Lai Jiangshan
2017-09-30 3:39 ` Paolo Bonzini
2017-10-02 10:36 ` [Xen-devel] " George Dunlap
2017-10-02 12:17 ` Paolo Bonzini [this message]
2017-10-02 19:11 ` [Xen-devel] KVM PV Nadav Amit
2017-10-06 7:47 ` Wanpeng Li
2017-10-02 10:18 ` [Xen-devel] KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support) George Dunlap
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=4ba6c3a0-85cd-4297-b4ed-4b859b953345@redhat.com \
--to=pbonzini@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=george.dunlap@citrix.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jiangshanlai+lkml@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®