The heart of my homelab is XCP-ng, a hypervisor running multiple VMs. Once in awhile (maybe three or four times a year) the server hardware powers down, whether due to utility issues or me doing maintenance.
XCP-ng uses a client controller called XOA, which I have configured as one of the VMs in XCP-ng. I have it configured to auto power on when the XCP-ng pool starts running – which is also set to auto power on.
Nevertheless, it sometimes doesn’t. When this is the case I need to be able to manually start that VM, which in turn runs the UI for easier management.
To do this, you need to login as root at the XCP-ng terminal (or remotely if you have that configured).
Then from the terminal:
xe vm-list
will show you the available VMs and their current state.
In this list, you will always see XCP-ng running as the host.
Then it’s simply a matter of picking which VM to start. In my case it’s named XOA.
xe vm-start vm=XOA
And that’s it! Give it awhile to boot and login at your configured IP.
Of course, you can start any VM listed this way if you want to get them up and running without waiting for the UI.