Online
@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
@roaringsilence Are you using XOA or XO from sources? Have you tried using xo-lite to start a VM? Did you check any of the logs as shown in the link I posted previously?
I assumed that you had an instance of XO up and running. If so, then you should find the error logs under Settings > Logs.
If you are starting from the CLI, then often there is some error information output directly in the console. Otherwise, check the log files.
@roaringsilence Please share with us one of the logs where the VM start task fails. Are the hosts showing as connected on the SR's Host tab?
Dan
@thedobe Have you checked the VM's Advanced tab to make sure the Prevent migration option is disabled?
@acebmxer It looks like you've resolved the first issue by binding the trial license. You haven't yet purchased support, so you won't be able to bind licenses to your XCP-ng hosts. This has no effect on the functionality of the hosts.
Hi @Andrew,
Thanks for the report. I'm seeing the same on my end, so I'll pass this along to the developers.
Dan
@olivierlambert Correct, it switches to Enterprise and then locks up because there isn't a license attached. Switching to the Stable release channel resolves the issue so that it is again running a valid XOA Free.
FWIW, I've verified this bug on XOA Free when on the Latest release channel.
@Lhoust I checked but was unable to locate a new ticket from you. I recommend going to https://vates.tech/contact/ and submit your inquiry from there. Be sure to provide the support tunnel ID if possible.
Have you tried resetting the VM's power state?
xe vm-reset-powerstate uuid=<UUID_of_the_VM> --force
There was a change a while back with the way Node handles timeouts, which affected instances of XOA where both IPv4 and IPv6 were assigned.
Temporarily adding the following entry to /etc/hosts will likely resolve the issue --
185.78.159.93 xen-orchestra.com
Hi Dustin,
Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it.
Dan
