[Container-tools] HyperV

[Todd Mancini]

Only 1 Hypervisor can run at a time. If Hyper-V is enabled (and, on most dev machines, it is enabled and it runs at boot time), when you attempt to launch another hypervisor, the other hypervisor will fail to launch, usually with some incomprehensible error message.

We saw this a lot when Visual Studio users first tried to do Android development using the default emulator in the ADK with HAXM. And, due to the terrible error messages, people would struggle for hours if not days to get it to work.

The thing is -- you cannot turn off Hyper-V -- it's a PXE/boot-time service. So even if you stop the service when Windows is running, the virtulization hooks to the processor have already done their business and cannot be undone.

This leaves you with two options -- (1) uninstall Hyper-V, which no dev wants to do because they likely need it for other things or (2) work some crazy magic with BCDEDIT to create a new boot entry so that you can optionally boot Windows without hyper-V. Which means that if you went this route and wanted to do android dev or, in our case, PDK dev, then you'd actually need to reboot first, do your work, and then likely reboot when you were done to get back to your 'normal' state.

Needless to say, pretty much everyone that tried this (myself included) gave up on it after a few days.

   -Todd

----- Original Message -----
From: "Pete Muir" <pmuir at redhat.com>
To: "Langdon White" <langdon at redhat.com>
Cc: "container-tools" <container-tools at redhat.com>, "Todd Mancini" <tmancini at redhat.com>
Sent: Thursday, November 5, 2015 7:11:51 AM
Subject: Re: [Container-tools] HyperV

The comment from Todd was that if yoiu have already installed hyper-v
on Windows, it will then disable all other hypervisors.

@Todd, can you elaborate?

On 4 November 2015 at 18:03, Langdon White <langdon at redhat.com> wrote:
> On another thread, hyper-v was mentioned as the only hypervisor available on
> windows these days. I have installed vbox on windows 10 and used it with
> vagrant just fine.
>
> I would like to see hyper-v as well, but it didn't make the cutoff for this
> release.
>
> langdon
>
>
> On 11/04/2015 01:02 PM, Langdon White wrote:
>>
>> no, not at this time: libvirt/kvm, vmware, virtual box
>>
>> On 11/04/2015 12:51 PM, Pete Muir wrote:
>>>
>>> Can you jog my memory - are we planning to support HyperV in the CDK 2.0?
>>>
>>> _______________________________________________
>>> Container-tools mailing list
>>> Container-tools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/container-tools
>>
>>
>> _______________________________________________
>> Container-tools mailing list
>> Container-tools at redhat.com
>> https://www.redhat.com/mailman/listinfo/container-tools
>
>