Forum wide moderators
@marcoi Hard to say because you haven't really given us much to go on. There are various things you could try --
Deploy a new VM with XO from sources and see if you get the same behavior
Investigate the XO tasks to see if you can find some commonality
You can wait to see if others start reporting this same issue
What version of Node is installed on this VM?
@marcoi You will likely need to do some more investigation on your side as I'm not able to reproduce it here.
@manilx Is yours booting in BIOS or UEFI mode?
@Thunder-Cloud Have you checked to see that the BIOS / firmware is fully updated? Are there any crash logs in /var/crash?
@AlbertK That would be a business decision above my pay grade. IMO that doesn't make sense because that page is showing the VMS bundles, which includes support for both XO and XCP-ng.
You can find some of the information discussed above in the XO docs. For example --
https://docs.xen-orchestra.com/xoa
https://docs.xen-orchestra.com/installation#from-the-sources
You can deploy and use XOA Free, which is a scaled down version without support or access to some features like backups. You also can get a free trial of XOA Premium, which allows you to access to all of the features for 30 days without any commitment.
@L1512191 Not entirely correct. XOA (the pre-build appliance from Vates) includes some additional functionality. For example --
Hi,
xo-lite is still a WIP, so there are some features that aren't yet accessible. I suggest that you deploy XOA to fully test the capabilities of XCP-ng.
Dan
