Thanks for your replies. Since the advent of mirror backups I realised there was an opportunity to backup to several different USB disks where each disk is a different remote allowing rotation of the disks. The primary backup goes to additional internal storage which is then mirrored to the USB disks. Only one snapshot per vm is needed regardless of how many USB disks are in use. To do this I need to script the mounting process for these disks and send notification emails when a disk is mounted, unmounted (safe to unplug) or when no disk could be found. This is my use case. Thanks

@OskarNTT Put the snapshot's UUID into the filter at the top right. This should show you all activity involving this snapshot, including when it was created. The vm.snapshot record contains the UUID of the target VM. In the latest releases of XO, you can click the UUID to be taken to the associated object.

@Tomcatter Great!

xe pool-list will give you the UUID of the master host. xe host-list will give you the host name. You can use a combination of xe commands to get the name of the master host -- xe host-param-get param-name=name-label uuid=`xe pool-list | grep master | awk '{print $4}'` Once you bring back up the old server, XO is smart enough to detect that it is no longer the master and will determine the correct host within the pool.

Great!!

@DustinB If I type it in the filter box on the Home page, it is not found. If I type it in the filter box on the Templates page, it is found and Shows Oracle Linux 7 if I list all the templates with xe template-list, it is not in the list

Coalesce isn't instant, and yes, as soon you remove a snapshot, there's some work to do from the storage perspective

@Gheppy A follow up... Patches appeared in XO right after updating the files (prior to an XCP-ng reboot). Just FYI.

FWIW, you can actually create a new VM without a default disk. Then switch to the VM's Disk tab and click the Attach disk button.

I agree the UI is suboptimal. It will be a lot better in the next one Anyway, it works for you, that's what matters

Yes, as long as the SR is not used by any other host/pool, it's safe to remove it. I'm talking about the SR NFS folder created by XCP-ng. Don't touch anything inside the folder except for entire removal of it.

@DustinB I built a new vm from the Ubuntu 22.04.4 template and it picked up an ip address from the DHCP server after boot. Interesting though, the name of the nic in the Netplan config file is now eth0 I noticed that VMware use a virtual nic named VMXNET 3 Maybe Ubuntu then maps that virtual nic to the ens33 nic name I see this issue was identified previously: https://xcp-ng.org/forum/post/68891

@johandr said in Remove and Register VM Again: The visibility problem of inactive vm's we can solve with the filters in XO. By default, you won't see powered off VM's either as the default view shows only running VMs with "power_state:running" You could of course clear that filter, and then see everything powered off, running, templates etc.

this button indead not very visible. Maybe it's worth to make it more like usual button? Paint to blue, or move to other side.

Yes, that was merged 4 days ago: https://github.com/vatesfr/xen-orchestra/pull/7388 julien-f opened this pull request in vatesfr/xen-orchestra closed Fix clone #7388

If the content is only white spaces, indeed it's impossible to edit. We'll fix that, thanks for the report! https://github.com/vatesfr/xen-orchestra/pull/7411 pdonias opened this pull request in vatesfr/xen-orchestra closed fix(xo-web/Text): replace spaces with nbsp so that the text is always clickable #7411

You can change a name anytime, it's just a "label" and won't interfere in any way on the system For example, in the SR view/disk tab, click on the disk name, it will be editable. Same in the VM/disk view.

@mestafin Found my problem - I used node V21 instead of node 18

Hi, This is already possible with XO Lite (pop up console), and we'll do the same for XO 6.