This issue happens from time to time, I’ve had the problem a number of times in our Demo Center at Arrow ECS in Norway. It’s often hassle to find out why it happens, but here is how you can shut down a virtual machine, which is in an amber state from XenServer control domain.
First off – Select the virtual machine in XenCenter and check the general tab to obtain the UUID of the virtual machine, which is in an unresponsive state!

Like this:

Run the following command to check the dom-id of the virtual machine in the XenServer control domain:
list_domains | grep <UUID from step1>
Following is a sample of the preceding command:
[root@XenServer1 ~]# list_domains | grep 37b55208-3db7-b160-4e90-c458b9ce9c37
Output :
51 | 37b55208-3db7-b160-4e90-c458b9ce9c37 | H
51 – the dom-id of the VM
37b55208-3db7-b160-4e90-c458b9ce9c37– UUID of the VM
H – state of the virtual machine (H indicates that this is a HVM guest, typically it means this is a Windows virtual machine.)
Run the following command to destroy the dom-id of the virtual machine:
destroy_domain –<dom-id from step2>
Following is a sample of the preceding command:
/opt/xensource/debug/xenops destroy_domain –51

 

TIP! Check out the Citrix.com Knowledge Center article CTX127896 – How to Use the XenServer Xentop Utility for more information about Virtual Machine states.

 

{loadposition content_starwind600}