Re: [QUERY] lguest64
From: Mike Rapoport
Date: Wed Jul 31 2013 - 09:07:29 EST
On Wed, Jul 31, 2013 at 3:17 PM, H. Peter Anvin <hpa@xxxxxxxxx> wrote:
> On 07/31/2013 02:39 AM, Mike Rapoport wrote:
>> The use case I had in mind is to use lguest as a nested hypervisor in
>> public clouds. As of today, major public clouds do not support nested
>> virtualization and it's not clear at all if they will expose this
>> ability in their deployments. Addition of 64-bit support for lguest
>> won't require changes to pvops and, as far as I can tell, won't change
>> the number of pvops users...
> "We can add a pvops user and that won't change the number of pvops
> users" What?!
We modify existing pvops user, IMHO. lguest is existing pvops user and
my idea was to extend it, rather than add lguest64 alongside lguest32.
>>> Yes, the subset of x86-64 machines for which there isn't hardware
>>> virtualization support is pretty uninteresting.
>> There are plenty virtual machines in EC2, Rackspace, HP and other
>> clouds that do not have hardware virtualization. I believe that
>> running a hypervisor on them may be pretty interesting.
> The big problem with pvops is that they are a permanent tax on future
> development -- a classic case of "the hooks problem." As such it is
> important that there be a real, significant, use case with enough users
> to make the pain worthwhile. With Xen looking at sunsetting PV support
> with a long horizon, it might currently be possible to remove pvops some
> time in the early 2020s or so timeframe. Introducing and promoting a
> new user now would definitely make that impossible.
I surely cannot predict how many users there will be for nested
virtualization in public cloud from now till the point when public
cloud providers will allow usage of hardware for that purpose.
Nevertheless, I believe that nested virtualization in public clouds is
a real use case which will have real users.
> So it matters that the use case be real.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/