Hyper V Manager - Can't start VMs after removing and virtual network

Answered Hyper V Manager - Can't start VMs after removing and virtual network

  • Montag, 23. April 2012 14:02
     
     

    Hi,

    I had 2 VMs in a Saved state and then carried out the following:

    1. Changed the network on each VMs network adapter to 'not connected'
    2. Removed the Internal network through the Virtual Network Manager and created a new one.
    3. Change the network on each VMs network adapter to the new Virtual Network.

    The VMs will now not start.

    I have tried the following (unsuccessfully):

    deleted the 'saved state' on each VM

    renamed the .bin and .vsv files in the respective machines' snapshot folders to .old.

    I have had this before and managed to fix it but can't remember how!

    Anyone come across this before?

    Thanks.

Alle Antworten

  • Dienstag, 24. April 2012 05:10
    Moderator
     
     
    Hi,

    I reproduced your steps and didn’t get the same issue.

    By the way, delete the ‘saved state’ should resolve the issue. 

    In addition, did you get any errors when you tried to start the virtual machine.


    Vincent Hu

    TechNet Community Support

  • Dienstag, 24. April 2012 08:47
     
     

    Thanks for getting back.  Sorry, I intended to add the error message I am getting:

    "An error occurred when attempting to start the selected virtual machine(s).

    '<machinename>' failed to start."

    Details

    "'<machinename>' failed to start. (Virtual machine ID <guid>"

    In EventVwr there is a bit more detail:

    '<machinename>' failed to start worker process: %%3221225794 (0xC0000142). (Virtual machine ID <guid>)

    Furthermore, if I add a new virtual machine I cannot start that either.  Same message.


    • Bearbeitet cpn1976 Dienstag, 24. April 2012 09:02
    •  
  • Dienstag, 24. April 2012 12:20
     
     

    Please enable Analytic/Debug logs for Hyper-v and repro the issue..

    You may check them to see for any clue..also share with us, to have a look..

    • Open the Event Viewer  (eventvwr.exe)
    • Select "Show Analytic  and Debug Logs" in the View menu
    • Browse to "Applications and Services Logs\Microsoft\Windows"
    • Expand the desired  Hyper-V log (Hyper-v-worker, Hyper-v-vmms, Hyper-v-hypervisor, Hyper-v-config)
    • Rigth click on one of  the listed Debug and/or Analytic channel and click on "Enable Log"
    • Repro the issue
    • Collect logs & share with us.


    Sanjai G [MSFT] This is just a suggestion. Microsoft doesn't own any liability & responsibility for any of my posting.!

  • Dienstag, 24. April 2012 12:43
     
     

    Thanks for the advice.

    The only node that is collecting any data (after enabling all the hyper-v analytic/debug logs) is Hyper-V-VMMS > Analytic.  It is capturing these 2 messages each time I try to start:

    • throw VmException((HRESULT)0xC0000142)
    • VmException caught in VmmsActiveVirtualMachine::StartInternal (HRESULT = 0xC0000142)

    If I re-install Hyper-V will I lose the snapshots I have?  Or, is the best way to export the VMs then import them again?

    Thanks

  • Dienstag, 24. April 2012 13:00
     
     

    Note to Vincent: try taking a snap shot before attempting the steps to reproduce above.

    If I select one of my snapshots >> right click >> settings, the network adapter is showing as a configuration error.  The settings on the actual VM have been reconfigured to a new virtual network.  However, I am unable to change settings on a snap shot.

  • Montag, 30. April 2012 16:14
     
     Beantwortet
    In the end I removed the Hyper-V role and then added it again.  My virtual machines were still present and I was able to start them successfully.  Thanks for the help!
    • Als Antwort markiert cpn1976 Montag, 30. April 2012 16:15
    •