Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 27, 2014 8:21 PM
Hi there,
I have a customer hyper-v guest server (Main), and whenever I try and shut it down, it does not shut down, instead it goes into a "Stopping-Critical" state, and just says there. The only way to get the server off is to Taskkill the hyper-v service, and then reboot the Host server. If I just try and reboot the host, it will freeze at 'shutting down the hyper-v service', and then at that point we have to pull the power out of it to get it to turn off!
They had a couple of power cuts over a few days, and then this Stopping-Critical problem started happening.
If I do a restart on the hyper-v guest server (Main), it will restart fine, and it is running fine also. It is running Active Directory and also Exchange.
How can I find out what is causing this Stopping-Critical message?
Thanks in advance,
Steve.
Steve
All replies (11)
Wednesday, November 5, 2014 10:02 AM ✅Answered
Hi Steve ,
Please try to install it with offline state :
Best Regards
Elton Ji
Monday, October 27, 2014 8:38 PM
How much disk space do you have on the drive that hosts the virtual machine configuration and virtual hard drives? Are you using dynamic disks?
What you are relating can sometimes occur due to lack of storage for the VM.
. : | : . : | : . tim
Monday, October 27, 2014 8:46 PM
What do you find in the Hyper-V event logs?
Events -> Applications and Services -> Microsoft -> Windows -> Hyper-V *
Check for worker logs, the VMMS, and other related logs to find the event.
It could be the storage volume to save the state is missing, your OS disk is fill of 'stuff', who knows.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Monday, October 27, 2014 9:02 PM
On the Host machine there is 209GB free on the C:, and 33GB free on the E: where the VHDX files are. This E: is 558GB in size.
On the problematic guest server there is 19GB (of 149) free on the C: and 76GB (of 299) free on the E:
However on the guest server, at the time when the problems started, we got to about 2GB free on the C:, and I've seen it dip as low as 77MB(!) free.
Can past storage issues still give problems into the future?
Steve
Monday, October 27, 2014 9:18 PM
The event that looks the most like the one is:
"Worker process health is critical for this virtual machine." From Hyper-V VMMS Admin. -This is about the time when we started having problems. But what does that even mean? It's about as vague as 'Stopping-Critical'.
And then this 10 minutes later: "Virtual Machine Management service is shutting down while some virtual machines begin running. All running virtual machines will remain running with no management access."
There is some of these in Hyper-V worker Admin:
The 'Microsoft Synthetic Display Controller' device in 'OPMain' virtual machine is loaded and the protocol version is negotiated to the most recent version.
And this also in Hyper-V worker Admin:
Device 'Microsoft Synthetic Display Controller' in 'OPMain' is loaded but has a different version from the server. Server version 3.3 Client version 3.2. The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
Lots of the other Hyper-V sections have no events in them.
Steve
Monday, October 27, 2014 9:32 PM
Are the integration components up to date in the VM?
What is the default stop action?
What happens when the VM is shut down from within the VM OS? (Does the OS in the VM think it can shut down properly)
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Tuesday, October 28, 2014 2:46 AM
Hi there,
In the problematic guest, I have this message:
Hyper-V Data Exchange connected to virtual machine 'OPMain', but the version does not match the version expected by Hyper-V (Virtual machine ID 11B4A9D2-4330-4725-93A7-D6B543EB1C82). Framework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (4.0) - Expected (5.0). This is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
...so I would think the integration components are not up to date. The host is running Server 2012 R2, and there are two guests. The problem one is running 2012 (can't upgrade to R2 due to Exchange), and the other has 2012 R2 also. Can I update the integration components if the guest is running a lesser OS than the host?
The default stop action for both Guests is Save.
When you try and shut the problematic guest down, it goes alll the way to the 'shutting down' screen, and then the Host says 'Stopping-Critical'. The other guest is fine.
Steve
Tuesday, October 28, 2014 3:00 AM
Your error message tells you exactly what to do to upgrade the integration components.
This is not an os upgrade.
Can you shut down the vm while logged in to the vm? (not using Hyper-V manager)?
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Tuesday, October 28, 2014 3:23 AM
About shutting down the VM while inside it, actually now that you say that, I don't know. I've always shut it down from the Hyper-V console.
Thanks,
Steve.
Steve
Tuesday, October 28, 2014 12:32 PM
Hi Steve,
>>Can I update the integration components if the guest is running a lesser OS than the host?
It is needed to install integration services if the Guest OS is older than HOST .
After installing it , the issue still persists ?
Best Regards
Elton Ji
Monday, November 3, 2014 8:11 PM
Hi there,
We've tried to install the Integration Services disk, and the server looks like it's done it, and then it restarts and says: (in startup – white text on the blue screen) Applying Updates…, 0% Update…, Update Failed…
We've tried this a couple of times, and it won't install.
I've looked in the event logs after this, and there is no mention of this update failing, but there is the one above about the Integration Services needing to be updated still, and also it's there in Hyper-V console itself saying "Update Required".
How do I get this Integration Services installed? Is there another way?
Thanks in advance.
Steve