MikroTik CHR on Citrix XenCenter - 100% CPU utilization. How to fix XenCenter VM if it’s stuck (yellow).

This morning I got the same problem AGAIN. This is why I put it here…

MikroTik CHR 6.42.6 running on Citrix XenServer 7.2 (a cluster) suddenly became unreachable for remote management (SSH, Winbox, …), but was still pingable. I logged in to Citrix XenCenter and checked VM console and it was fine. Moreover, I was able to log in using RADIUS-authenticated user. I was not able to find what’s wrong with this VM other than CPU utilization was 100% flat.

I decided to reboot the VM. Normally, reboot process is really fast, but this time it took few minutes. Here is what I’ve see in the console:

[admin@MikroTik] > /system reboot
Reboot, yes? [y/N]:
system will reboot shortly

Stopping services...
failed to stop ipsec: std failure: timeout (13)
failed to stop ppp: std failure: timeout (13)
failed to stop dhcp: std failure: timeout (13)
failed to stop hotspot: std failure: timeout (13)

The process was too slow and I decided to power “Shut Down” the VM via XenCenter. Well, I tried and it went yellow and got stuck in that state. That means I was not able to stop or start the VM.

The solution for that issue is to log in to XenServer via SSHQ and restart the XenServer management toolstack (also known as xapi) by command as it’s listed here:

[root@localhost ~]# xe-toolstack-restart
Executing xe-toolstack-restart
[root@localhost ~]#

After that VM turned red (it was powered down), but it allowed me to power it on.

Good luck!

Add comment

Fill out the form below to add your own comments

User data

Add your comment

Admin area