Failed to start VM in my i7-2600K Hyper-V server 2008 R2


MS Hyper-V R2 SP1 (workgroup), Virtual Machine failed to change state

Backgroud:

1. Download Hyper-V R2 SP1 from http://technet.microsoft.com/en-us/evalcenter/dd776191.aspx

2. This server is running in workgroup mode

3. Disable firewall for all profiles

4. Enable all remote access through sconfig

5. Connect through Vista and Win7 in same workgroup with using Administrator account (Same administrator’s password on all machines)

6. hosts file modifed with adding hyper-v server name and IP

7. Windows firewall is disabled on all clients and server.

8. HRremote run to configure anonymous DCOM on client.

9. Remote Management can access to Hyper-V server and create Virtual Machine.

Problem:

When I start Virtual Machine. It has the error message “XXXXX failed to change state”.

I tried to simulate this issue with W2K8 R2 to the same machine. But this issue does not appear in W2K8 R2. I faced this problem in MS Hyper-V R2 SP1 only.

I re-installed 3 times and this issue can be reproduced in my machine.

I tried W2K8 R2 Standard (Full and Server Core) without problem. I can use my Vista to manage it succesfully.

I checked in event viewer. It has an event 3040.

Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 5/4/2011 9:27:08 AM
Event ID: 3040
Task Category: None
Level: Error
Keywords:
User: NETWORK SERVICE
Computer: hyperv
Description:
‘W2K8_R2_Trial’ could not initialize. (Virtual machine ID CEF2E5E4-97A1-4393-9B5D-24805C81BE09)
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>3040</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0×8000000000000000</Keywords>
<TimeCreated SystemTime=”2011-05-04T01:27:08.857Z” />
<EventRecordID>14</EventRecordID>
<Correlation />
<Execution ProcessID=”808″ ThreadID=”2224″ />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>hyperv</Computer>
<Security UserID=”S-1-5-20″ />
</System>
<UserData>
<VmInitialize xmlns:auto-ns2=”http://schemas.microsoft.com/win/2004/08/events” xmlns=”http://www.microsoft.com/Windows/Virtualization/Events“>
<VmName>W2K8_R2_Trial</VmName>
<VmId>CEF2E5E4-97A1-4393-9B5D-24805C81BE09</VmId>
</VmInitialize>
</UserData>
< /Event>

Solution:

Finally, I find out a hotfix which is related to this issue.

KB2517374: “You cannot start virtual machines on a computer that is running Windows Server 2008 R2 and on which a CPU is installed that supports the AVX feature”

http://support.microsoft.com/kb/2517374

After applying this Hotfix, I can start the Virtual Machine.

VN:F [1.9.18_1163]
Rating: 3.0/5 (2 votes cast)
VN:F [1.9.18_1163]
Rating: -1 (from 1 vote)
Failed to start VM in my i7-2600K Hyper-V server 2008 R2, 3.0 out of 5 based on 2 ratings
Total views: 22,651 views

, , , , ,

  1. #1 by buy gold on May 23rd, 2011

    Only recently Microsoft caught up with its feature…Hyper-V Live Migration is undoubtedly the most sought-after feature of Hyper-V because of its ability to move virtual machines VMs between clustered hosts without noticeable service interruption. As an admin you should understand some lesser-known Hyper-V Live Migration terms that help monitor and troubleshoot service interruption. ..Hyper-V event logs contain information about live migration disruptions that can briefly affect VMiss For every VM live migration these logs report three events a brownout event a blackout and dirty-pages event and a summary of the live-migration process.

    VA:F [1.9.18_1163]
    Rating: 0.0/5 (0 votes cast)
    VA:F [1.9.18_1163]
    Rating: 0 (from 0 votes)
(will not be published)

  1. No trackbacks yet.