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.

@acebmxer There are older versions of the guest tools still available on Github.

@acebmxer said in Host compatibility:

Maybe if i shutdown the vms and boot backup all will be good?

This is generally correct. If the VMs haven't been migrated or rebooted since the additional host was added to the pool, then you can encounter this situation due to CPU masking.

See the docs for an explanation of Homogeneous vs Heterogeneous Pools.

@Pilow said in Network Management lost, No Nic display Consol:

you can try the command on MASTER host, you should see

master:ip_of_the_master

Slight correction. On the master, you should only have

master

without the colon and IP address.

@DustinB said in Recommended DELL Hardware ?:

Doesn't using non-shared storage ultimately cause the VM to be started on the other host?

No. Live migration can occur between hosts even if:

• the VDI are located on non-shared storage
• the hosts are in completely different pools

For the cross pool migration to succeed, both pools need to support a common instruction set. Otherwise, use the Warm Migration feature that does reboot the VM so that it is running the correct instruction set on the destination host.

@DustinB said in Recommended DELL Hardware ?:

With local storage on each hosts, you won't be able to live migrate from 1 host to the other.

That's incorrect. The migrations will take significantly longer because the VDI will be migrated along with the VM's memory, but you can live migrate VMs between hosts even if the VDI are stored on local storage.

@olivierlambert New thread is here

It is difficult to know the source of the problem without more details from your logs. Can you run the following commands on your XCP-ng host and then attach the generated files here?

grep -A 15 -B 15 -i error /var/log/xensource.log/xensource > xensource.txt
grep -A 15 -B 15 -i exception /var/log/SMlog > smlog.txt
dmesg -T|grep -Eiv 'guest|capacity|promiscuous' > dmesg.txt

Hi @Tristis-Oris Have you tried this option on the secondary menu?

What OS are you running on the VMs? Do you have the guest tools installed on them?

@markxc I don't think this is possible yet with the REST API. However, you should be able to do it using xo-cli:

xo-cli vm.setBootOrder vm=<string> order=<string>