From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bandan Das Subject: Re: Windows-10 virtualization and nested virtualization Date: Mon, 04 Apr 2016 17:35:42 -0400 Message-ID: References: <1459800526.3392.19.camel@nacon.com> Mime-Version: 1.0 Content-Type: text/plain Cc: "qemu-discuss\@nongnu.org" , "kvm\@vger.kernel.org" To: Jeff Forbes Return-path: Received: from mx1.redhat.com ([209.132.183.28]:47344 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754311AbcDDVfq (ORCPT ); Mon, 4 Apr 2016 17:35:46 -0400 In-Reply-To: <1459800526.3392.19.camel@nacon.com> (Jeff Forbes's message of "Mon, 4 Apr 2016 20:08:46 +0000") Sender: kvm-owner@vger.kernel.org List-ID: Jeff Forbes writes: > We have a Windows-10 application which uses a virtual as part of the > process. I am trying to get the application to work in a virtual > environment, which of course will require nested virtualization. > > Using a libvirt xml description for a RHEL virtual where nested > virtualization works, I installed windows-10, Hyper-v and the > application software under the latest updates of Fedora 22. > Windows-10 works great; however, VMBus device required for Hyper-V to > work would not start and was flagged in the Device Manager. Trying to > start a virtual resulted in the error that a component required by > Hyper-V failed to start. > > I then ported the VM to VMWare Workstation 12 and in this environment t > he VMBus device starts and nested virtuals start as expected. These > results indicated that the VM was working correctly and the problem was > likely with the QEMU-KVM hypervisor. > > Reading recent messages on the KVM and QEMU mail lists indicated that > there were many KVM updates made to the 4.6.0-rc1 kernel, so I > download, compiled and installed this kernel. I also cloned the latest > version of qemu. When I run my Windows-10 VM in this environment with > the latest updates. the VMBus device starts and there are not warnings > in the Device Manager; however, the nested VMs do not start and the > same error about a component required by Hyper-V failed to start. > > Do I need to turn something on to get this to work or is the Hyper-V > support still under development? I am not sure if anyone has been successful with running Hyper-V nested. The first obstacle I remember is Hyper-V refusing to run when it finds the "hypervisor" flag in guest cpu. If you are past that step, maybe the vmbus dependency is something else. > Please advise. > > > Best, > > Jeff-- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html