Failed to start the virtual machine because one of the Hyper-V components is not running

I have successfully connected to a new build Hyper-V 2012 R2 server and created a VM. When I try to start the VM I get the message "Failed to start the virtual machine <vmservername> because one of the Hyper-V components is not running"
ClintonKAsked:
Who is Participating?
 
Arjun VyavahareConnect With a Mentor Technical ConsultantCommented:
Hi,

To fix this error you have to edit the VMX configuration file. This VMX configuration file is located at your Virtual Machine's path.
Before edit the configuration file Shutdown the Hyper-V host (Windows Server 2008/2008 R2/2012/2012 R2) from VMWare.

and

Open the VMX file with text editor such as Notepad. And enter the below line at end of the notepad.

hypervisor.cpuid.v0 = "FALSE"

I hope this will resolve your issue.

Regards,
Arjun
1
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Are the virtualization acceleration settings in the BIOS turned on? Reboot the server and verify that all virtualization services are enabled.

You could force-start the Hyper-V service and check the Event Logs as well.
0
 
ClintonKAuthor Commented:
Do you mean the BIOS settings in the Hyper-V server or the VM?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
On the physical host. If the virtualization settings are not turned on Hyper-V services will not start.
0
 
ClintonKAuthor Commented:
It's not quite a physical host. It's a virtual machine running under VMware ESXi 5.5.0
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Unless VMware has some sort of magic to pass the host's virtualization acceleration features through to that VM it is not going to happen.

Hyper-V as a rule needs to run on bare metal with virtualization acceleration features enabled in the BIOS.
0
 
ClintonKAuthor Commented:
This indeed was the solution once I had worked out where the VMX file lived. The Hyper-V host is a virtual server on a ESXi server so it was the VMX file for the server there. I built the Hyper-V server, closed it down and then removed it from the vSphere inventory. I then edited the file by copying it out of the datastore , editing it with the line hypervisor.cpuid.v0 = "FALSE" and the copied it back and added the server back into vSphere. Once I had done this the servers would start OK.
Servers within servers within servers was getting me confused!
0
 
ClintonKAuthor Commented:
In addition to
hypervisor.cpuid.v0 = "FALSE"
it is also necessary to add
vhv.enable = "TRUE"
0
 
Desert Warrior_DZCommented:
@Dear arjun,

the solution working perfect.

@ClintonK,

when u add  vhv.enable = "TRUE" will give you error in the possibility of running the server at all.
did u check it dear. plz advice
and what the use of this instruction.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.