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.

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.

@julien-f Ahh.. perfect! This a huge help until the other matter can be dealt with. I see it now and the testing is successful with this change. Thank you again to you and the team!

Indeed, as per @Danp Xen Orchestra provides an OVA importer. Since VMware decided to play dumb and not supporting OVA exports, you have 2 options: create an OVA yourself, it's trivial: it's a tarball with the OVF and VMDK disks. XO is capable on reading the OVA, prepare the VM metadata and then will import the VMDK import the VMDK in XO directly, and create the VM metadata yourself (I think we could easily add OVF metadata read import in XO since we already do it with OVA) I really do not understand why (well I think I did) Vmware removed the OVA export feature despite it's a lot easier to deal with.

@DustinB Not sure if there is a good way to do this, IMO though it's worth learning the number row on the top for touch typing. Not that that is a solution for you lol, but I personally used to be a 10 key only person and decided to force myself to learn the number row and I'm nearly as fast on it as I was on the 10 key and now I don't have to have a 10 key anywhere. But as far as I know there isn't a way to pass that through (at least that isn't easy, I'm sure it's technically possible)

@rtjdamen Copying my reply to your official support ticket (any reason for duplicating support tickets on the forum as well?): given XOA is built on standard debian, you can assign multiple IPs to the same interface quite easily by just duplicating another "iface eth1 inet static" line. Also keep in mind XOA does not add extra interfaces under the main /etc/network/interfaces file, but in files under the /etc/network/interfaces.d/ directory. So in your case given it was eth1 you wanted a second IP on, you can add your required second IP in this file like so: [09:43 12] xoa:~$ cat /etc/network/interfaces.d/eth1 allow-hotplug eth1 iface eth1 inet static address 192.168.1.80 netmask 255.255.255.0 #second IP iface eth1 inet static address 172.16.100.5 netmask 255.255.255.0

If it's enabled, the Audit Log is a nice feature (look under Settings > Audit).

@Danp said in No Xen Tools Detected: @DustinB Have you tried the usual suspects? Restart the drivers Restart the VM Uninstall / reinstall the VM tools Break out the sledge hammer Yes Can't during normal business hours No, see above It may not matter if I can consolidate this VM in the near future, but yes maybe... lol...

@DustinB We are using "local" XOA-accounts, but: I was able to find the right syntax: xo-cli user.set id=xxx-xxx-xxx preferences='json:{"otp":"JVTXXXXXXXXX"}' I am able to set a fixed OTP