One of my development server was not
accessible. It’s a VM under Xenserver and trying to fix things through
XenCenter was quite a deadend. The console was not accessible from
XenCenter, there was only a blank white screen.
When the VM was being forced to shutdown, it gave an error message
“Another operation involving the object is currently in progress class: VM“.
There’s some discussion and proposed solution from on internet. Here’s quote from one of the post that finally fix it for me (you need to login to server’s shell to execute the below command):
1 – Type “xe vm-list” to get the uuid of the VM that is hung
2 – Type “list_domains” to list the domain uuid’s so you can determine the domain # of the VM above by matching the uuids from this output with the uuid for your VM from the previous command.
3 – Type “/opt/xensource/debug/destroy_domain -domid XX” where XX is the domain number from the previous command
4 – Type “xe vm-reboot uuid=XXXX –force” where XXXX is the uuid from the first vm-list command for your VM. (name-label may work but didn’t work this time for me so I used the uuid)
When the VM was being forced to shutdown, it gave an error message
“Another operation involving the object is currently in progress class: VM“.
There’s some discussion and proposed solution from on internet. Here’s quote from one of the post that finally fix it for me (you need to login to server’s shell to execute the below command):
1 – Type “xe vm-list” to get the uuid of the VM that is hung
2 – Type “list_domains” to list the domain uuid’s so you can determine the domain # of the VM above by matching the uuids from this output with the uuid for your VM from the previous command.
3 – Type “/opt/xensource/debug/destroy_domain -domid XX” where XX is the domain number from the previous command
4 – Type “xe vm-reboot uuid=XXXX –force” where XXXX is the uuid from the first vm-list command for your VM. (name-label may work but didn’t work this time for me so I used the uuid)
No comments:
Post a Comment