Many versions of Windows 10 include the Hyper-V virtualization technology. Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems can be used and managed just as if they were physical computer systems, however they exist in.

1. Enable Hyper-V on Windows 10 Go to Control Panel → Programs → Turn Windows features on or off, check Hyper-V option, make sure all components are selected, and click OK. You may reboot your computer once the Hyper-V feature was added.
2. I'm relatively new to Hyper-V and virtualization. What I would like to know, is the best way to create a Mac OS X VM running in Windows Hyper-V host. I'm currently using a Windows 10 based desktop running Hyper-V to create a test lab. I'd like to run a Mac OS X VM in Hyper-V in my test lab.

According to the Apple support article Turn off Hyper-V to use Windows 10 on your Mac it is not possible to use Hyper-V in Windows 10 on a Mac in Boot Camp. This is a big limitation for me, since also it means it will be impossible to use Docker Windows Containers on a Mac, since they require Hyper-V. Are there any practical workarounds for this? If you are running Windows 10 Version 1607 (Anniversary Edition), the Hyper-V firmware will already have the Windows Server 2016 TP5 boot manager blacklisted. For example, when you set up Hyper-V on a Windows 10 Version 1607-based system, if you then create a Windows Server 2016 TP5-based virtual machine (VM), the VM does not start.

Enable Hyper-V to create virtual machines on Windows 10.
Hyper-V can be enabled in many ways including using the Windows 10 control panel, PowerShell or using the Deployment Imaging Servicing and Management tool (DISM). This documents walks through each option.

Note: Hyper-V is built into Windows as an optional feature -- there is no Hyper-V download.

Check Requirements

• Windows 10 Enterprise, Pro, or Education
• 64-bit Processor with Second Level Address Translation (SLAT).
• CPU support for VM Monitor Mode Extension (VT-c on Intel CPUs).
• Minimum of 4 GB memory.

The Hyper-V role cannot be installed on Windows 10 Home.

Upgrade from Windows 10 Home edition to Windows 10 Pro by opening up Settings > Update and Security > Activation.

For more information and troubleshooting, see Windows 10 Hyper-V System Requirements.

Enable Hyper-V using PowerShell

1. Open a PowerShell console as Administrator.

2. Run the following command:

If the command couldn't be found, make sure you're running PowerShell as Administrator.

When the installation has completed, reboot.

Enable Hyper-V with CMD and DISM

The Deployment Image Servicing and Management tool (DISM) helps configure Windows and Windows images. Among its many applications, DISM can enable Windows features while the operating system is running.

To enable the Hyper-V role using DISM:

1. Open up a PowerShell or CMD session as Administrator.

2. Type the following command:

For more information about DISM, see the DISM Technical Reference.

Enable the Hyper-V role through Settings

1. Right click on the Windows button and select ‘Apps and Features’.

2. Select Programs and Features on the right under related settings.

3. Select Turn Windows Features on or off.

4. Select Hyper-V and click OK.

When the installation has completed you are prompted to restart your computer.

Make virtual machines

Recently I picked up a Mac Book Air. It is a nice device, fast processor, lots of memory and fast hard drives. I am not to keen on using OS X so I decided to install Windows onto it. So I installed windows, loaded the drivers, installed all my applications and then went to install Hyper V to run up VM’s for different reasons. Instead of my smooth install and everything working out fine I get:

Hyper-V Cannot be installed: Virtualization is disabled in the firmware

Surely this is a mistake, I mean the machine is only a few years old, its an Intel MAC and WHAT??!?! So I check the task manager to see the enabled features on the Chip and sure enough the features is there, just disabled.

So close, yet so far away

So like any good IT person I figured a reboot would fix it, hit the reboot button and checked again and the issue remains. I know from previous experience that this usually means the features needs to be enabled in the BIOS, but that might as well be french on a MAC so what was I to do? I turned to Google to help find the answers and this is generally what I found:

• If I installed OS X, the features were enabled. (So it is enabled during the boot process)
• The general way to fix this issue on the internet was to dual boot with OS X. For any cold boot, I would boot into OS X and then use the startup disk facility to warm boot into windows.

Ok, so um, OK. Sometimes I cant get over what seems to be an acceptable solution on the internet. I mean lets stop for a minute and critically think about this. First up Pros and Cons

Pros

Hyper V Windows 10 Bootcamp Activator

• OS X is the best and you need nothing else ever! (Source: Fanboi)

Cons

• I have to configure, update and maintain two Operating systems (Increased attack surface and potential for attack vectors)
• I have to boot two operating systems for any cold boot situation (Double boot time, might as well have stuck with spinning rust)
• I loose 38 – 40 GB of partition in my already small SSD to an operating system that I will rarely use. (That is two extra VM’s)
• I own the hardware so for Apple (or anyone for that matter) to tell me it is only enabled under specific circumstances is garbage.

Right. So as we can see the Cons to this solution seem to be outweighing any OS X is the best argument. So next step in my critical thinking is to assess what I know to be true which is

• I can not enable the feature in BIOS unless I consider using a custom BIOS Firmware (Which I don’t want to do)
• The feature is able to be turned on during the boot process, and under the right circumstances is enabled in Windows (So it isn’t impossible)
• I want to use HyperV and not an alternative like Virtual Box because Hyper V is a type 1 hyper visor. (Its a thing – See http://searchservervirtualization.techtarget.com/tip/Virtualization-hypervisor-comparison-Type-1-vs-Type-2-hypervisors)

I tried may different things to try and resolve the issue including

• Using a non UEFI boot image to see if legacy would enable the feature – Nope
• Looking for a way to turn it on manually once the operating system was booted – Nope
• More research

After some time looking into how it all works I found an alternative boot loader that could be used which promised that it could enable the feature under Windows. I have used alternative boot loaders before (I am looking at you Grub) so I figured it couldn’t hurt and was worth a go. The boot loader was called rEFInd and you can see its Sourceforge page at https://sourceforge.net/projects/refind/ and a great book about it at http://www.rodsbooks.com/refind/

So here are the steps I took to install it

• Install Windows using the whole drive
• Install OS X onto a USB drive
• Boot into a OS X Recovery Environment (I installed OS X onto a USB drive, then held Option during the boot, selected recovery environment)
• In a terminal in the Recover execute

• Next reboot into OSX (You can actually do this via windows as well, more on that later)
• Download rEFInd and modify the refind.conf-sample file that comes with the download and modify the following values