On 06/04/2016 19:45, Jeff Forbes wrote:
> I was responding to Bandan Das' comment about Hyper-v NOT running when
> the hypervisor flag is present. What I observed was just the opposite.
> With "-cpu host,+vmx" Hyper-V will try to start the VM and then report
> that a component required by Hyper-V
I was responding to Bandan Das' comment about Hyper-v NOT running when
the hypervisor flag is present. What I observed was just the opposite.
With "-cpu host,+vmx" Hyper-V will try to start the VM and then report
that a component required by Hyper-V failed to start. The end result is
the same; how
On 06/04/2016 17:27, Jeff Forbes wrote:
> When I use "-cpu host,+VMX,-hypervisor", Hyper-V gives this error
> when trying to start a VM: Virtual Machine could not be started
> because the hypervisor is not running.
>
> So with the latest kernel and qemu-kvm, the hypervisor flag is
> needed.
Tha
When I use "-cpu host,+VMX,-hypervisor", Hyper-V gives this error when trying
to start a VM:
Virtual Machine could not be started because the hypervisor is not running.
So with the latest kernel and qemu-kvm, the hypervisor flag is needed.
On Mon, 2016-04-04 at 17:35 -0400, Bandan Das wrote:
J
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
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 nestedvirtualization.
Using a libvirt xml description for a RHEL virtual where nested
virtualization work
