Re: [RFC 00/55] Nested Virtualization on KVM/ARM

[My previous reply had HTML subpart, which made the e-mail look terrible and being rejected from mailing lists. So, I'm sending it again. Sorry for the inconvenience] Hi Christoffer, On Wed, Feb 22, 2017 at 1:23 PM, Christoffer Dall wrote: > Hi Jintack, > > > On Mon, Jan 09,

Re: [RFC 00/55] Nested Virtualization on KVM/ARM

Hi Christoffer, On Wed, Feb 22, 2017 at 1:23 PM, Christoffer Dall wrote: > Hi Jintack, > > > On Mon, Jan 09, 2017 at 01:23:56AM -0500, Jintack Lim wrote: > > Nested virtualization is the ability to run a virtual machine inside > another > > virtual machine. In other words,

Re: [RFC 00/55] Nested Virtualization on KVM/ARM

Hi Jintack, On Mon, Jan 09, 2017 at 01:23:56AM -0500, Jintack Lim wrote: > Nested virtualization is the ability to run a virtual machine inside another > virtual machine. In other words, it’s about running a hypervisor (the guest > hypervisor) on top of another hypervisor (the host hypervisor).

Re: [RFC 00/55] Nested Virtualization on KVM/ARM

On Mon, Jan 9, 2017 at 10:05 AM, David Hildenbrand wrote: > >> Even though this work is not complete (see limitations below), I'd >> appreciate >> early feedback on this RFC. Specifically, I'm interested in: >> - Is it better to have a kernel config or to make it configurable at

Re: [RFC 00/55] Nested Virtualization on KVM/ARM

Even though this work is not complete (see limitations below), I'd appreciate early feedback on this RFC. Specifically, I'm interested in: - Is it better to have a kernel config or to make it configurable at runtime? x86 and s390x have a kernel module parameter (nested) that can only be

[RFC 00/55] Nested Virtualization on KVM/ARM

Nested virtualization is the ability to run a virtual machine inside another virtual machine. In other words, it???s about running a hypervisor (the guest hypervisor) on top of another hypervisor (the host hypervisor). This series supports nested virtualization on arm64. ARM recently announced an