Table of Contents
“Hyper-V cannot be installed: The processor does not have the required virtualization capabilities.”, but does it really not?
Installing Hyper-v in Virtualbox is of course not recommended. You are going to use a virtualization tool and then use another layer of virtualization. For test purposes or just because you can, is it of course possible.
I assume in the blog post below that you already have a virtual machine running Windows OS in VirtualBox. If that is not the case, you can first follow this post.
If you install Hyper-V within VirtualBox you get the following error message:
“Hyper-V cannot be installed: The processor does not have the required virtualization capabilities.”
The problem here is that you want to use virtualization within a host that also uses virtualization, so the virtualization is already occupied by VirtualBox. This makes it impossible to use Hyper-v in Virtualbox.
Fortunately, I have found a solution for this. The manual consists of two parts. The first part is for the system administrators among us with access to PowerShell.
The second part is for end-users who want Hyper-v within VirtualBox. Which is also with PowerShell but explained better including screenshots.
Hyper-v in VirtualBox the basics.
Before we can start we must first verify that virtualization is enabled in VirtualBox.
- Double click the Virtual machine.
- Open the Settings (Gearwheel).
- Go to the tab system.
- Click the tab Acceleration.
- verify if VT-x/AMD-V is enabled.
It may be that this already solves your problem. So you could now check whether you can install Hyper-v in VirtualBox. You can also finish the rest of the tutorial.
Enable Hyper-V with PowerShell.
Start the Virtual Machine and make a remote desktop connection to the Virtual Machine.
Go to start and search for PowerShell.
The brief and to the point part.
Copy / paste the following commands in PowerShell.
It is best to use it per line.
Enable-WindowsOptionalFeature –Online -FeatureName Microsoft-Hyper-V –All -NoRestart Install-WindowsFeature RSAT-Hyper-V-Tools -IncludeAllSubFeature Install-WindowsFeature RSAT-Clustering -IncludeAllSubFeature Install-WindowsFeature Multipath-IO Restart-Computer
The longer but clearer explanation for dummies.
First, do not restart the VM while you are doing this. Do not restart the VM until the end.
Copy / paste the command into PowerShell and wait for the script to finish.
Enable-WindowsOptionalFeature –Online -FeatureName Microsoft-Hyper-V –All -NoRestart
Again, Copy / paste the command into PowerShell and wait for the script to finish.
Install-WindowsFeature RSAT-Hyper-V-Tools -IncludeAllSubFeature
And again, Copy / paste the command into PowerShell and wait for the script to finish.
Install-WindowsFeature RSAT-Clustering -IncludeAllSubFeature
..and again, Copy / paste the command into PowerShell and wait for the script to finish.
At last, Copy / paste the command into PowerShell and wait for virtual machine to re-start.
If you now look in Server Manager at Server Roles, you can see that the Hyper-V role is installed on the Virtual Machine.
The post originally dated from May 28, 2015. I have reviewed the post and thought that it could be worked out better, which is why the post has been re-published on 27-6-2018. The content is still relevant.
Do you have any questions, comments, or other ideas? Then let me know in a comment below.