I've seen rare instances where even Linux guests get hung shutting down. Especially if you're trying to shut them down when there is a process hung on the guest. Most of the time a "kill" works fine with no lasting issue with the guest.
I have had one instance in which a guest refused to do this. In this case I did the following from the CLI
try to delete a lock
/usr/sbin/ovs-agent-dlm --unlock --uuid "uuid of the vm guest"
ls -ltr /dlm/ovm
Force lock remove by deleting it.
rm -f /dlm/ovm/"uuid of the vm guest"
You also use the xm command to kill a VM guest from the CLI of the VM Server
xm list will list domains(VM Guests that are running)
xm stop uuid of the guest will stop a running XM
xm destroy uuid of the guest will "kill" a running XM.
The one time I had this happen I was getting NFS errors on the shared NFS repo.
Thanks a ton for that information! That is going to help us in the long run so we don't have to physically reboot the blade and kill everything!
I read on another Oracle forum post that someone had mentioned that NFS could be causing some hangs in OVM/OVS...did you ever figure out what errors were being caused in NFS? We are using it for two of our repositories. Thanks again!
I can't remember exactly what the error was but it wasn't generated in any log on the VM Server but I could see it on the VM guest through the VNC console.... post unmount of logical disks. Seems like it had unmounted the repo but was still trying to access something within the repo. Seems like it was throwing stale NFS handle errors. Don't quote me. My memory isn't what it use to be.