Just one point here regarding the BIOS configuration: If you enabled VM
Technology in BIOS, you havee to do a COLD boot of your computer. For some
computers and servers, this means to power off the computer, then turn power
on again. Some other servers do actually do a cold boot by themselves.
"msnews.microsoft.com" wrote:
> I got this puzzling message on trying to start a vm
> Hyper-V Manager
> ===============================
> An error occurred while attempting to change the state of virtual machine
> VMAcctg
> "VMAcctg" failed to intialize.
> The virtual machine could not be started becuase the hypervisor is not
> running
>
> "VMAcctg" failed to intialize.(Virtual machine 36.......)
>
> The virtual mahcine could not started becuase the hypervisor is not running
> the following action my help you resolve the problem:
> 1) verify thate the process of the physical computer has a supported version
> of hardware-assisted virtualization
> *I verified the hw ****Does support *** virutalization assitance
> 2) verify that the hardware-assisted virtualization and hardware-assited
> data execution protedtion are enabled in the BIOS of the physcial computer
> and then turn it back on. Resetting the physical computer is not
> sufficient.)
> * verified*
>
> 3) If you have made changes to the Boot Configuration data store review
> these changes to ensure that the hypervisor is configured to automatically
> * don't understand but I have not change the boot configuartion
> since installation *
> ---------------
> Close
> ---------------
> ===============================
>
>
> I also saw services.msc listed hypervisor as running however I did see error
> log has event ID 3040, 3112,
>
>
> event ID 3112
> The virtual machine could not be started because the hypervisor is not
> running. The following actions may help you resolve the problem: 1) Verify
> that the processor of the physical computer has a supported version of
> hardware-assisted virtualization. 2) Verify that hardware-assisted
> virtualization and hardware-assisted data execution protection are enabled
> in the BIOS of the physical computer. (If you edit the BIOS to enable either
> setting, you must turn off the power to the physical computer and then turn
> it back on. Resetting the physical computer is not sufficient.) 3) If you
> have made changes to the Boot Configuration Data store, review these changes
> to ensure that the hypervisor is configured to launch automatically.
>
> Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
> Source: Microsoft-Windows-Hyper-V-Worker
> Date: 09.01.22 12:04:36P
> Event ID: 3112
> Task Category: None
> Level: Error
> Keywords:
> User: NETWORK SERVICE
> Computer: HV01
> Description:
> The virtual machine could not be started because the hypervisor is not
> running. The following actions may help you resolve the problem:
>
> 1) Verify that the processor of the physical computer has a supported
> version of hardware-assisted virtualization.
>
> 2) Verify that hardware-assisted virtualization and hardware-assisted data
> execution protection are enabled in the BIOS of the physical computer. (If
> you edit the BIOS to enable either setting, you must turn off the power to
> the physical computer and then turn it back on. Resetting the physical
> computer is not sufficient.)
>
> 3) If you have made changes to the Boot Configuration Data store, review
> these changes to ensure that the hypervisor is configured to launch
> automatically.
>
>
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-Hyper-V-Worker"
> Guid="{51ddfa29-d5c8-4803-be4b-2ecb715570fe}" />
> <EventID>3112</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8000000000000000</Keywords>
> <TimeCreated SystemTime="2009-01-22T19:04:36.335Z" />
> <EventRecordID>9</EventRecordID>
> <Correlation />
> <Execution ProcessID="2536" ThreadID="3540" />
> <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
> <Computer>HV01</Computer>
> <Security UserID="S-1-5-20" />
> </System>
> <UserData>
> <VmlEventLog
> xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events"
> xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
> </VmlEventLog>
> </UserData>
> </Event>
>
>
>