로그인
 
홈라이브러리학습다운로드지원커뮤니티포럼
Resources for IT Professionals >
> 
> 
Hyper V Manager - Can't start VMs after removing and virtual network

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

  • 2012년 4월 23일 월요일 오후 2:02
     
     
    로그인하여 투표
    0

    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.

     

모든 응답

  • 2012년 4월 24일 화요일 오전 5:10
    중재자
     
     
    로그인하여 투표
    1
    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

     
  • 2012년 4월 24일 화요일 오전 8:47
     
     
    로그인하여 투표
    0

    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.


    • 편집됨 cpn1976 2012년 4월 24일 화요일 오전 9:02
    •  
     
  • 2012년 4월 24일 화요일 오후 12:20
     
     
    로그인하여 투표
    1

    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.!

     
  • 2012년 4월 24일 화요일 오후 12:43
     
     
    로그인하여 투표
    0

    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

     
  • 2012년 4월 24일 화요일 오후 1:00
     
     
    로그인하여 투표
    0

    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.

     
  • 2012년 4월 30일 월요일 오후 4:14
     
     답변됨
    로그인하여 투표
    0
    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!
    • 답변으로 표시됨 cpn1976 2012년 4월 30일 월요일 오후 4:15
    •