Restart the toolstack on each server.

You should be able to delete the snapshots without causing any harm. A couple of things to keep in mind --

• If the snapshot is associated with an existing backup job, then the next run of that job will result in a full backup instead of a delta

• It may take some time for the snapshots to coalesce following deletion, so this could still affect your backups until they are completely removed

• If you want to delete the backups associated with the old job, then you can from the Backup > Health tab in XO

It is also possible to perform this activity from within XO as described here. There are some prerequisites for performing this action that you should review -- https://docs.xcp-ng.org/installation/requirements/#-pool-requirements

I would setup a Continuous Replication backup job to create a duplicate VM on the new storage repository. When you are ready to perform the cutover, shutdown the original VM, perform one final run of the CR job, and then start the new VM on the new pool.

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.

The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.

@JoyceBabu They are now available at https://www.xenserver.com/downloads

@jr-m4 Yes, it seems that all dropdown lists are broken by a recent dependency update. XO team has been notified.

@BrianDLC The error ""EACCES: permission denied" should have pointed you to a permissions error to begin with.

Since we have no knowledge of how that script operates, it often makes more sense to refer you to their repo for help rather than us guessing at the reason for the issue.

@Ascar I suspect that Olivier means to register with the XO instance using this syntax --

xo-cli register [--allowUnauthorized] [--expiresIn <duration>] [--otp <otp>] <XO-Server URL> <username> [<password>]

You can run xo-cli without any parameters to get the full usage text.

@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?

https://docs.xcp-ng.org/troubleshooting/log-files/

@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

https://docs.xen-orchestra.com/community

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 --

• Built in updater with the ability to select from several release channels
• Ability to deploy / manage proxies
• Ability to deploy / manage XOSTOR instances
• Support related features (tunnel, 16 point check, ability to restart xo-server from the UI)
• Cloud based XO config backup

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 Glad you got it all sorted out.

@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.