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

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

Click the person icon below the Sign Out option to access the settings for the currently logged in user.

@jebrown For now, there is a limit of 7 network interface on a VM on XCP-ng/Xen Orchestra.

How many network interfaces are defined on this VM?

@fatek No. My understanding was that @ronan-a would be publishing another update soon.

@sb2014 I've encountered this particular issue once before, and these were the steps we used to correct it --

• Shutdown the VM
• Export the snapshot's VDI from the SR's DIsks tab using XVA file format
• Forget the snapshot
• Import the XVA file created in the earlier step
• Attach the newly imported disk to the target VM
• Start the VM to verify that it boots correctly

Regards,
Dan

@fatek Yes

@sb2014 said in VDI migration:

is-a-snapshot ( RO): true

This is the issue. Somehow the VDI has been flagged as a snapshot, so XOA doesn't display it in the VM's Disks tab.

Are you running XCP 8.2 or 8.3?

Please answer this. Also, is your host fully patched? What version of XO are you running?

Are you running XCP 8.2 or 8.3? Is the "missing" VDI still visible in the Disks tab of the SR in XO? If so, then you can obtain it's UUID there and then run this command on your host and post the resulting output here --

xe vdi-list uuid=<UUID> params=all

Having good backups of your VMs would be a smart choice before proceeding.

I confirm this behavior. Checking with the dev team to see if this is by design.

Did you follow the documentation for running as a non-root user?

https://docs.xen-orchestra.com/installation#sudo