Stuck with Citrix XenServer internal error? We can help you.
At times after failing the operation to Move VM, Copy VM, or Export VM on a Virtual Machine (VM) it will not start. Furthermore, it ends up with an Internal error.
Here at Bobcares, we often handle requests from our customers to fix similar errors as a part of our Server Management Services. Today we will see how our support engineers fix this for our customers.
What causes Citrix XenServer internal error
Before going into the steps for fixing this error we will see what causes this error.
Cause for the error
This error occurs when the Control Domain on XenServer that runs VM, attaches Virtual Disk Image (VDI) of VM to Control Domain.
The Control Domain uses this disk to perform the operations that have been initiated on the VM.
If any operation fails, the VDI will still have an attachment to the control domain through a Virtual Block Device. We have to destroy the connection.
The Control Domain connection can be seen on the disk by selecting the Storage Repository Object. This can be seen on the Left Pane of the XenCenter, in the Storage Tab.
How to fix this error
We can use the following steps to fix this error:
- First, we need to open the Console to the XenServer that is hosting the VM.
- And run the following command:
#list_domains - Then we have to copy the UUID corresponding to id=0.
This is the UUID of the Control Domain. - After that we need to run the following command to obtain the UUID of the VBD (Virtual Block Device) object linking the Control Domain:
#xe vbd-list vm-uuid= - Finally, we need to run the following commands to unplug and destroy the VBD:
#xe vbd-unplug uuid=
#xe vbd-destroy uuid=
[Still stuck with the error? We can help you]
Conclusion
To conclude, we saw how our Support Techs fix Citrix XenServer internal error for our customers.
0 Comments