Hyper-V

Enable/Install Hyper-V

Installing Hyper-V Role using ServerManagerCMD.exe

ServerManagerCMD.exe –query -
servermanagercmd.exe -install Hyper-V

Installing Hyper-V Role using PowerShell

Import-Module servermanager
Add-WindowsFeature Hyper-V

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

Installing Hyper-V Role using OCSetup (Packet Manager)

Start /w ocsetup Microsoft-Hyper-V

Enable and Disable Hyper-V using DISM Command at elevated cmd prompt

dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All

Automatic Virtual Machine Activation

Requirments

• The Hyper-V host is a Windows Server 2012 R2 Datacenter Edition.
• The VMs are running Windows Server 2012 R2, thus only the below three editions can get activated by AVMA
  • Windows Server 2012 R2 Standard
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Essentials
• The Hyper-V host is activated. (It can be activated using any of your regular activation mechanisms like MAK, OEM or KMS.)
• The Guest VMs have AVMA client key installed on it

slmgr /ipk <AVMA_key>

AVMA keys

Datacenter Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
Standard   DBGBW-NPF86-BJVTX-K3WKJ-MTB6V
Essentials K2XGM-NMBT3-2R6Q8-WF2FK-P36R2

Force VM to activate

slmgr /ato

References

• Automatic Virtual Machine Activation
• Activating virtual machines via Automatic Virtual Machine Activation in Windows Server 2012 R2
• Running Nested VMs VMware community
• Installing and managing Hyper-V in VMware Workstation 11

Oracle Virtualbox can nest only 32bit systems, therefore you cannot run Hyper-V hypervisor on it. Often this is signalled by following error message "VM-server-X failed to start. Failed to start the virtual machine 'VM-server-X' because one of Hyper-V components is not running."