• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Virtual Machine Manager Error

M

Mabrito

Supreme [H]ardness
Joined
Dec 24, 2004
Messages
7,004
Anyone here familiar with Virtual Machine Manager 2008 R2 for Hyper V environments?

I am having issues with one of our hosts that is managed by VMM and when it runs the refresher task of "Refresh Virtual Machine Properties" on a managed host, its failing. This is causing the VM's on the host to go into a "Host not responding state" If I was to right click the host in VMM and choose "Refresh" in a couple minutes all the VM's return to there proper status of either running, shutdown, saved state, etc.

When this "Refresh Virtual Machine Properties" task runs from what it looks like, every 20-30 minutes, its owner is NT AUTHORITY\SYSTEM and when I right click a host and choose refresh, its task is ran by the domain admin account....so I am wondering if I have some permission issue.

On the host I am trying to manage, the VMM server is part of its local admin group. On all the 4 other hosts that is managed by VMM, this task runs just fine and no issues are encountered, only with this one host.

The only two error messages I see in the event log are:

Event 434: The status of managed computer FQDN of Managed Host changed from Responding to Not Responding.
Event 435: The status of host FQDN of Managed Host changed from Responding to Not Responding.
 
Have you tried reloading the VMM agent on the host to see if it's resolved? How was that host added, the same as the others, via cluster..etc?
 
Vader said:
Have you tried reloading the VMM agent on the host to see if it's resolved? How was that host added, the same as the others, via cluster..etc?
Click to expand...

Yep reloaded the agent yesterday afternoon. I just clicked "Add host" and ran through that Setup utility and it took care of everything. This is how we did it for all the other hosts and they are working fine.

No cluster...we don't have a SAN yet (looking into one...hopefully by end of year), so right now each host is its own storage server too.

It seems what its doing, is it runs that "Refresh Virtual Machine Properties" task and all the VM's go into a "Host not responding" status and then immediately after that task runs and fails, it kicks off again and after another 2 - 5 minutes, VM's are in there proper status.
 
You must log in or register to reply here.
Back
Top