Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Hi Roel, Rain Maker writes: > Thanks again Bandan. > > One more question for you. In the KVM source tree (arch/x86/kvm) of > kernel 4.3-rc4, I see a file "hyperv.c". Comment states: > > * KVM Microsoft Hyper-V emulation > * > * derived from arch/x86/kvm/x86.c > * > *

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Thanks again Bandan. One more question for you. In the KVM source tree (arch/x86/kvm) of kernel 4.3-rc4, I see a file "hyperv.c". Comment states: * KVM Microsoft Hyper-V emulation * * derived from arch/x86/kvm/x86.c * * Copyright (C) 2006 Qumranet, Inc. * Copyright (C) 2008 Qumranet, Inc.

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Rain Maker writes: > The screenshot and weird behavior I posted is within the L1 VM. > > So; > - L0 (host / hypervisor): 0x3a = 5 immediately after boot. L1 VM is > booted WITH -enable-kvm, nested=1, -hypervisor (also tried without > this option), +vmx > > - L1 - Linux (VM

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

The screenshot and weird behavior I posted is within the L1 VM. So; - L0 (host / hypervisor): 0x3a = 5 immediately after boot. L1 VM is booted WITH -enable-kvm, nested=1, -hypervisor (also tried without this option), +vmx - L1 - Linux (VM / "sub-hypervisor"). 0x3a = 0 immediately after boot.

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

> On Oct 6, 2015, at 4:43 PM, Rain Maker wrote: > > Unfortunately, no difference. WIth or without -hypervisor doesn't make > any difference to that flag. > > But, experimenting on, I found something odd. > The 0x3a register is 0 when the VM boots up. > Even when I start

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Qemu on Linux works fine. I did not even have to explicitly set -hypervisor. It simply works. As does VirtualBox FYI. Booting with UEFI didn't make any difference. After A LOT of Googling, I believe that Hyper-V actually checks bit 0x3a of the MSR register (instead of, as the error would . This

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Rain Maker writes: > Qemu on Linux works fine. I did not even have to explicitly set > -hypervisor. It simply works. Sorry, I meant running Linux with "-hypervisor" to see if specifying that is somehow messing with the feature flags. > As does VirtualBox FYI. > > Booting

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

Thanks Bandan. That helped a bit. It got me to the next hurdle, as you suspected. I modified the virsh XML so that -cpu host,+vmx,-hypervisor is passed, and the installation now reports "Hyper-V cannot be installed because virtualization support is not enabled in the BIOS.". I am sure that vmx

Re: [Qemu-discuss] Supported hypervisors running VMs in nested VM

... > Windows 2012 / 2016 technical preview 3 > > The installation via the "default" method of Add/Remove Features does > not work. Hyper-V displays the error message "A hypervisor is already > running". > > This check can be skipped by