[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ba6c3a0-85cd-4297-b4ed-4b859b953345@redhat.com>
Date: Mon, 2 Oct 2017 14:17:54 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: George Dunlap <george.dunlap@...rix.com>
Cc: Lai Jiangshan <jiangshanlai+lkml@...il.com>,
Juergen Gross <jgross@...e.com>,
Rusty Russell <rusty@...tcorp.com.au>, lguest@...ts.ozlabs.org,
kvm@...r.kernel.org, the arch/x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
xen-devel <xen-devel@...ts.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Xen-devel] KVM PV
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
Powered by blists - more mailing lists