VMware Horizon Community
Cronistar
Contributor
Contributor
Jump to solution

Multiple VM's Being Locked

Using View 4 here, and every day when I come in, there's at least one user that cannot access their VM, "the assigned desktop source is not available...".

Our View setup currently has just a standalone ESX 4 box that handles these View clients. We have other View clients on a cluster and we haven't seen this issue, but the clients on the cluster aren't used as often as the standalone box.

So, once again, this is the classic "the vm is locked" issue.

Here's what I've done thus far:

1. Open the VM in the vSphere client: "unable to connect to the mks: vmx connection handshake failed."

2. vmware-cmd -s unregister

-tired registering in vSphere again, no love, same error...

12. Gave up, rebooted the ESX box, fixedit!!!

-but now another machine is showing the same problems... Sigh...

Any help/advice would be great...

Reply
0 Kudos
1 Solution

Accepted Solutions
Icereval
Contributor
Contributor
Jump to solution

You didn't mention what patch level you on, however this sounds like the issue we were experiencing prior to loading the latest ESX patches.

Be sure you've patched your ESX servers up to March 2010 rollup:

http://kb.vmware.com/kb/1018403

Specifically KB1017465 fixes a Dev Tap issue with PCoIP and resolution changes that would cause the VM to crash (http://kb.vmware.com/kb/1017465).

View solution in original post

Reply
0 Kudos
2 Replies
Icereval
Contributor
Contributor
Jump to solution

You didn't mention what patch level you on, however this sounds like the issue we were experiencing prior to loading the latest ESX patches.

Be sure you've patched your ESX servers up to March 2010 rollup:

http://kb.vmware.com/kb/1018403

Specifically KB1017465 fixes a Dev Tap issue with PCoIP and resolution changes that would cause the VM to crash (http://kb.vmware.com/kb/1017465).

Reply
0 Kudos
Cronistar
Contributor
Contributor
Jump to solution

Icereval,

Thanks for the tip! Being an "educational security lab" we have it completely isolated so we kind of ignored the whole patching issue.

I must say, we all felt kind of foolish when it was just an update that fixed our problem...

Thanks again!

Reply
0 Kudos