Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Hyper-V frozen at 2% while taking snapshot

570 views
Skip to first unread message

nhekman

unread,
Feb 9, 2009, 5:38:39 PM2/9/09
to
Hello.

I have a virtual server in a hung state. I tried to take a snapshot
of it, but it got 2% of the way through the process and then appears
to be stuck--it hasn't moved in 45 minutes. During the time the Hyper-
V Manager is extremely slow to respond to other requests as well.

I checked the event logs, and there is nothing from around the time I
took the snapshot. About 8 minutes later the Hyper-V-VMMS log gave
this warning: "Worker process health is critical for virtual machine
'<my hung server>' (Virtual machine <guid>)."

Here are my specs:
- Latest version of Hyper-V with all available updates (I think!).
(Hyper-V Manager shows version 6.0.6001.18016)
- 14 GB of RAM free on host machine
- 190 GB free hard drive space on host machine (that's plenty for
the size of the virtual machine)
- Windows Server Datacenter SP1 x64

This is the second time this has happened to me, last time I
"resolved" it by rebooting the host (the virtual server came up fine),
but that's not something I can do lightly. I'm hoping someone can help
me avoid this problem in the future, and/or find me a way to get out
of this state without rebooting the host.

Any solutions or ideas on what else I can look for?

Thanks in advance!

Nate

niksac

unread,
Mar 21, 2009, 5:15:04 PM3/21/09
to

Hi

I am facing the same problem, did you got any solution to this?

-Nik

Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

Nate

unread,
Jun 16, 2009, 10:45:01 AM6/16/09
to
Nope, no solution, and it still happens to me occasionally. As much as
possible I try to shut the server down before taking the snapshot, just to be
safe, but isn't that the whole point of snapshots, that you don't have to?!

Nate

GG

unread,
Jul 28, 2009, 5:46:01 AM7/28/09
to

"Nate" wrote:

quick fix

for each of the virtual processes there is a worker process (vmwp.exe). in
such a case you should notice under processes that the size of worker process
is an enlarged state. you can kill that process and start the virtual machine
again not affecting the other virtual machines hosted.

0 new messages