Hyper-V VMs in Stopping Critical State
-
@Reid-Cooper no, nothing, team viewer only
-
@Alket_tux Can you turn off that service and attempt to reboot?
-
@wirestyle22 it means that the state of the vm is running again, it just does not show the resources allocated to it
-
@wirestyle22 i tried to do that, but it did not stop, it remained in stopping state.. and in the logs it showed that the vm-s were running so this service cannot be stoppoed
-
i have not inserted integration services manually but yesterday everything worked fine..
by the way i have emulex nic's and in google i found that it might be a problem -
@Alket_tux I also found NIC related issues listed
-
@wirestyle22 i found some kb related solutions but haven't applied yet
-
@Alket_tux From what I've been reading they didn't help. Hopefully yours is different. What VM's are you running? OS's and everything
-
@wirestyle22 windows server 2012 r2 my primary server
hyper v role on top of it
6 ws2012 r2 vm's created -
@Alket_tux all working fine until yesterday, when i left my office and let windows update
on all servers -
@Alket_tux said in Hyper-V VMs in Stopping Critical State:
Hello guys,
i ve been in trouble with hyper v on ws 2012 r2.. the issue is that when i restart my server Hyper-v Virtual machine management service takes an eternity to stop, so i hard reboot.. after that my machines are in runnig state.. also when i try to shutdown my vm-s, their state goes to stopping critical.. any ideas would be helpful..
thanksWhen you shut down a Hyper-V server, the default settings for all of your VMs is to save the state of the VM. After that, your server will shut down. Depending on the number of VMs you have, it could take a little bit to save the state of all of them. It has to write the memory to disk, etc. Also, the default startup option is to start the VMs if they were started when they went down, which is why they are back up when you boot up your hypervisor.
If you are killing your server during this process, you are hurting your VMs. This will cause critically stopped states. Hopefully they are .vhdx disks to help prevent corruption.
-
@Tim_G said in Hyper-V VMs in Stopping Critical State:
@Alket_tux said in Hyper-V VMs in Stopping Critical State:
Hello guys,
i ve been in trouble with hyper v on ws 2012 r2.. the issue is that when i restart my server Hyper-v Virtual machine management service takes an eternity to stop, so i hard reboot.. after that my machines are in runnig state.. also when i try to shutdown my vm-s, their state goes to stopping critical.. any ideas would be helpful..
thanksWhen you shut down a Hyper-V server, the default settings for all of your VMs is to save the state of the VM. After that, your server will shut down. Depending on the number of VMs you have, it could take a little bit to save the state of all of them. It has to write the memory to disk, etc. Also, the default startup option is to start the VMs if they were started when they went down, which is why they are back up when you boot up your hypervisor.
If you are killing your server during this process, you are hurting your VMs. This will cause critically stopped states. Hopefully they are .vhdx disks to help prevent corruption.
Oh I misread the OP. I thought he originally shut this down properly. @Alket_tux you just attempted to reboot the hypervisor without shutting down the VM's initially, am I reading that correctly now?
-
@Tim_G i did stop my server forcefully a couple of times,
-
@wirestyle22 yes,, because i could not shut down the vm's as they went in stopping critical state
-
@Alket_tux said in Hyper-V VMs in Stopping Critical State:
@wirestyle22 yes,, because i could not shut down the vm's as they went in stopping critical state
I know it seems like I'm asking the same questions but just bare with me. The order of events are you attempted to stop the VM's and they immediately attempted stopping in a critical state. That's when you rebooted the host server, correct? You did not reboot the host server before the VM's were in a critical state
-
@wirestyle22 no i did not reboot the server before that state..
actually let me explain what happend in the first place:yesterday all things worked fine vswitch etc..
today all the vm's including my host sever had limited network.
i connected a second cable and connected to the host..
i tried to work with my vm's change their network etc.. the vms went in stopping state..
then i tried to change the network setting of the vswitch from static to dynamic IP.. at that moment my host crashed.. i had only the hyper v window open.. all the windows features were gone, like windows explorer had crashed..
at this point i force rebooted my server.. when it went back up, the same things happen, i connect to a vm. i try ti restart it vm hangs and goes in stopping state -
@Alket_tux said in Hyper-V VMs in Stopping Critical State:
@wirestyle22 no i did not reboot the server before that state..
actually let me explain what happend in the first place:yesterday all things worked fine vswitch etc..
today all the vm's including my host sever had limited network.
i connected a second cable and connected to the host..
i tried to work with my vm's change their network etc.. the vms went in stopping state..
then i tried to change the network setting of the vswitch from static to dynamic IP.. at that moment my host crashed.. i had only the hyper v window open.. all the windows features were gone, like windows explorer had crashed..
at this point i force rebooted my server.. when it went back up, the same things happen, i connect to a vm. i try ti restart it vm hangs and goes in stopping state]Yesterday everything worked until you applied updates you said though. I find it difficult to believe there is nothing listed in
event viewerat the very least. Did you attempt to uninstall whatever was installed yesterday or research the updates applied? -
@wirestyle22 updates were applied only in the VM's not the host.. everything is ok, just for a vm an error about integration services
