[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJhGHyAETM7NiHT-jFJPXakYE55vc0HegPxdDLD18wNi+Y1uZQ@mail.gmail.com>
Date: Sat, 30 Sep 2017 08:04:15 +0800
From: Lai Jiangshan <jiangshanlai+lkml@...il.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org,
xen-devel@...ts.xenproject.org, x86@...nel.org,
lguest@...ts.ozlabs.org,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
Rusty Russell <rusty@...tcorp.com.au>,
Juergen Gross <jgross@...e.com>
Subject: Re: KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support)
On Sat, Sep 30, 2017 at 12:39 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> On 29/09/2017 17:47, Lai Jiangshan wrote:
>> Hello, all
>>
>> An interesting (at least to me) thinking came up to me when I found
>> that the lguest was removed. But I don't have enough knowledge
>> to find out the answer nor energy to implement it in some time.
>>
>> Is it possible to implement kvm-pv which allows kvm to run on
>> the boxes without hardware virtualization support, so that
>> qemu/kvm can be used on clouds such as aws, azure?
>
> No, please don't. :) Even Xen is moving from PV to PVH (paravirtualized
> hardware with event channels, grant tables and the like, but still using
> hardware extensions for MMU).
>
> Rather, cloud providers should help getting nested virtualization ready
> for production use. At least for KVM it's not that far.
>
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.
Thanks,
Lai
>
Powered by blists - more mailing lists