[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0385483C-83AB-44F7-AD39-F5BB9A3237F1@gmail.com>
Date: Mon, 2 Oct 2017 12:11:14 -0700
From: Nadav Amit <nadav.amit@...il.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: George Dunlap <george.dunlap@...rix.com>,
Lai Jiangshan <jiangshanlai+lkml@...il.com>,
Juergen Gross <jgross@...e.com>,
Rusty Russell <rusty@...tcorp.com.au>, lguest@...ts.ozlabs.org,
kvm <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
Paolo Bonzini <pbonzini@...hat.com> wrote:
> 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!
BTW: If anyone missed, Google already announced that they started supporting
nested virtualization.
https://cloudplatform.googleblog.com/2017/09/introducing-nested-virtualization-for.html
Nadav
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists