VMM 3.5 and ESX (3.5 update 1) File locking Issue

[Eric Stocker]

We ran into an issue with VMM 3.5 running on HPSIM 5.2 SP1. We had a VM that had multiple virtual drives and was experiencing an issue with losing it's drives (except c drive). One of the engineers stopped the vm and tried to delete all the files thinking he may have to restore the VM. Upon trying to delete the files we discovered that the VMM agent had a lock on the VM's files and we couldn't delete them. We stopped the VMM client daemon on the ESX server and started the VM up and discovered that the other virtual drives were now corrupt.

Has anyone else run into this issue or know why the VMM Agent put a lock on the VM's files?

[Rob Buxton]

What kind of corruption did you experience?

[Eric Stocker]

Basically the VM no longer recognized the vmdk files so we could not see the drives. We tried to just remove it from the VM and re-add it but the VM threw and error stating corrupted disk.

VMWare support had us restore from backup.