none
Virtual Machine Fails to start

    Question

  •  

    I get the following error when trying to start a virtual machine

     

    An error occurred while attempting to change the state of virtual machine %VirtualMachineName%

     

    %VirtualMachineName% failed to change state.

     

    any help would be greatly appreciated

    Andy

    Thursday, March 27, 2008 12:23 PM

Answers

  • yea - adding the Hyper-V role is no where near the same as installing Virtual Server.

     

    It is a fundamental modification of the entire server - how it interacts with its hardware and how it even manages itself.

     

    Hyper-V is not a role that should be mixed with other complex / demanding roles (such as a terminal server, domain controller, Exchange server ,etc.).

     

     

     

    Thursday, March 27, 2008 5:03 PM
    Moderator

All replies

  • Have you tried deleting the virtual machine and then recreating it using the same VHD?

     

    (deleting the VM only removes the registration of the VM not the VHDs of the VM)

     

    Thursday, March 27, 2008 3:40 PM
    Moderator
  • thanks for the reply, this is a brand new virtual server i haven't managed to get it to work at all. tried to create a couple of machines now and all with the same error.

    Thursday, March 27, 2008 4:31 PM
  • Is there details associated with the error message?

     

    Cheers,

    Ben

    Thursday, March 27, 2008 4:44 PM
    Owner
  • Brand new Hyper-V server?

     

    1) is it running anything else or is it just to test Hyper-V?

      - what all roles did you add and in what order..

     

    2) are you creating new VMs or trying to migrate in existing VMs?

     

    It sounds as if you have corruption of the vm datastore.

     

    And if this is jsut for evaluating Hyper-V you may want to rebuild the server, add the RC0 upgrade, then add the Hyper-V role and start fresh.

     

    Thursday, March 27, 2008 4:44 PM
    Moderator
  • yes lots of roles, domain services, terminal services, dhcp and more most installed after first install, its all for evaluation so i think i'll take your advice and rebuild the box. (this time i'll only install the one role)

     

    thanks
    Thursday, March 27, 2008 4:56 PM
  • yea - adding the Hyper-V role is no where near the same as installing Virtual Server.

     

    It is a fundamental modification of the entire server - how it interacts with its hardware and how it even manages itself.

     

    Hyper-V is not a role that should be mixed with other complex / demanding roles (such as a terminal server, domain controller, Exchange server ,etc.).

     

     

     

    Thursday, March 27, 2008 5:03 PM
    Moderator
  • Hi Andy,

    This problem presented for me because I had not set the Virtual Server Settings in the Bios of my Dell Box.

     

    • Proposed as answer by pavangm Friday, December 26, 2008 11:24 AM
    Sunday, May 11, 2008 12:29 PM
  • Phew, I must admit i just experienced the same issue.
    Server 2008 Enterprise, Hyper-V RC1

    A major power-outage in the city took down everything.
    When starting the server back up again, the Asus mainboard's BIOS reported that it suspected a overclocking failure (as it use to do when it experiences a unexpected reboot).
    I calmed it down with F1, please continue.

    Server 2008 returned as normal - nothing unusal. A sigh of relief.
    Started the Hyper-V console ... and noticed that I had 6 VM's "in a saved state".
    "Hm. That's new to me - well, let's try to start them then" was my first thought.

    Server 1 starting.
    "Server1 failed to change state".
    Weird. Tried again - same result.
    Tried server #2 to #6. Same.

    Found this thread - started to considering creating new VM's and moving the disks over.
    Just for the heck of it, I rebooted the VM Host again - just to have one more go from scratch.

    Upon startup - bootmanager notifies me of a previou sunexpected boot, and defautls to "Start Windows Normally" with the rest of the repair options.
    Hm, thats odd - the shutdown this time wasnt unexpected - the one before this one was.

    Oh well - let Windows start normally. Logged on.
    Started the Hyper-V console. Lo and behold - all 6 VM's had been autostarted, and running for 1:30 minutes.

    Problem solved itself.

    Note to self 1: Never trust Windows to resume normal operation after a powerfailure, on the first reboot.
    Note to self 2: VM's saved states - if there's something weird, reboot the host server - and then start evaluating the issues at hand, if any.

    Sincerly, Jon E. Carlsen
    • Proposed as answer by Dale Unroe Tuesday, June 17, 2008 3:21 PM
    Monday, June 02, 2008 12:11 AM
  • Jon,

    Went through a similar power outage/reboot -> error issue with Hyper-V RC1 on Core and I followed your advice to reboot.  Voila - all is now well.  Thanks for your help.

    Dale
    Tuesday, June 17, 2008 3:23 PM
  • I have a BRAND NEW Microsoft Windows Server 2008 Enterprise x64 bit system Version 6.0 (Build 6001: Service Pack 1)  (I did all available Microsoft Updates)
    11.5GB RAM  HP ProLiant Server and I did turn on the ability for Hyper-V to work in the BIOS.

    Roles for this Server, 1 of 17 installed, Hyper-V


    These are a few of the errors I get in Event Viewer.  I understand that this is a BETA version, and I am willing to deal, I just want to know if "I" am doing anything wrong.  I am having it point to a Server 2008 x64 bit ISO file that I downloaded from Microsoft Licensing to install our corporate software with.

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          6/19/2008 8:32:34 AM
    Event ID:      18160
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      APP06.SERVER.com
    Description:
    The description for Event ID 18160 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    VSHyperV
    E9F38B3C-4A31-4304-A175-80655FD80F1E
    %%3222072877
    0xC00CEE2D

    The locale specific resource for the desired message is not present

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066f867-7ca1-4418-85fd-36e3f9c0600c}" />
        <EventID>18160</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2008-06-19T12:32:34.345Z" />
        <EventRecordID>59</EventRecordID>
        <Correlation />
        <Execution ProcessID="2072" ThreadID="4632" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>APP06.SERVER.com</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>VSHyperV</VmName>
          <VmId>E9F38B3C-4A31-4304-A175-80655FD80F1E</VmId>
          <ErrorMessage>%%3222072877</ErrorMessage>
          <ErrorCode>0xC00CEE2D</ErrorCode>
        </VmlEventLog>
      </UserData>
    </Event>







    Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
    Source:        Microsoft-Windows-Hyper-V-Worker
    Date:          6/19/2008 8:32:34 AM
    Event ID:      12010
    Task Category: None
    Level:         Error
    Keywords:     
    User:          NETWORK SERVICE
    Computer:      APP06.SERVER.com
    Description:
    'VSHyperV' Microsoft Synthetic Ethernet Port (Instance ID {291F1A6D-1EA3-410A-ACBA-74426FDDAF15}): Failed to power on with Error 'The specified network resource or device is no longer available.' (0x80070037). (Virtual machine E9F38B3C-4A31-4304-A175-80655FD80F1E)
    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>12010</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2008-06-19T12:32:34.095Z" />
        <EventRecordID>22</EventRecordID>
        <Correlation />
        <Execution ProcessID="4112" ThreadID="1328" />
        <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
        <Computer>APP06.SERVER.com</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">
          <VmName>VSHyperV</VmName>
          <VmId>E9F38B3C-4A31-4304-A175-80655FD80F1E</VmId>
          <DeviceName>Microsoft Synthetic Ethernet Port</DeviceName>
          <ErrorCodeString>%%2147942455</ErrorCodeString>
          <ErrorCode>0x80070037</ErrorCode>
          <DeviceInstanceId>{291F1A6D-1EA3-410A-ACBA-74426FDDAF15}</DeviceInstanceId>
          <Param1>
          </Param1>
        </VmlEventLog>
      </UserData>
    </Event>

    Thursday, June 19, 2008 6:47 PM
  • Worked in my situation...Thanks for the input!
    Sunday, October 04, 2015 9:42 AM