Created a simple bash script to remove VMware Tools;

sudo apt remove open-vm-tools

sudo rm -r /etc/vmware-tools
sudo rm /etc/systemd/system/open-vm-tools.service
sudo rm /etc/systemd/system/vmtoolsd.service 
sudo rm -r /etc/systemd/system/open-vm-tools.service.requires
sudo rm -r /etc/vmware-tools

sudo apt autoremove

@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

I have checked this with XOA and XO Sources (latest)

When you select and delete one template at a time, everything works and it is removed from the list of templates.

If you select multiple templates, it looks like nothing happens - the templates are not removed from the list, although the tick marks are removed.

When you then try to delete one of the templates again, you get this error log:

vm.delete
{
  "id": "a194633f-b946-0f9e-50d0-3022366b4eaf-f873abe0-b138-4995-8f6f-498b423d234d"
}
{
  "code": "HANDLE_INVALID",
  "params": [
    "VM",
    "OpaqueRef:b8aef32a-bb91-41a7-bf73-7748e5e8cb55"
  ],
  "call": {
    "method": "VM.get_record",
    "params": [
      "OpaqueRef:b8aef32a-bb91-41a7-bf73-7748e5e8cb55"
    ]
  },
  "message": "HANDLE_INVALID(VM, OpaqueRef:b8aef32a-bb91-41a7-bf73-7748e5e8cb55)",
  "name": "XapiError",
  "stack": "XapiError: HANDLE_INVALID(VM, OpaqueRef:b8aef32a-bb91-41a7-bf73-7748e5e8cb55)
    at Function.wrap (file:///home/vmin/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at file:///home/vmin/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:35:21"
}

if you list the templates with

xe template-list

the templates are still in the listed

For now, a work-around is to only delete one template at a time

Created a simple bash script to remove VMware Tools;

sudo apt remove open-vm-tools

sudo rm -r /etc/vmware-tools
sudo rm /etc/systemd/system/open-vm-tools.service
sudo rm /etc/systemd/system/vmtoolsd.service 
sudo rm -r /etc/systemd/system/open-vm-tools.service.requires
sudo rm -r /etc/vmware-tools

sudo apt autoremove

I have a number of Ubuntu 22.04LTS vm's to migrate.

All of them are running VMware Tools version 12325 and are guest-managed.

From Google, I learned that you need to run:

sudo vmware-uninstall-tools.pl

to uninstall VMware tools.

Except there is no such script anywhere on my Ubuntu vm.

Any advice how to do this removal?

@olivierlambert

If I may ask a question here - is there a way to "clean up" the NFS SR folder on the NAS to get rid of orphaned uuid entries no longer linked to XO?

@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

@DustinB

Let me try that ...

@DustinB

I have tried XOA and the latest community edition (build it today).

I imported the the vm's powered on and when switched off.

Once in XO, I install guest-tools and change the nic name. I tried installing guest-tools and rebooting the vm, but there is still no IP record. I have to change the name before it works.

I first suspected that it was just an XO problem not reporting the IP record with the old ens33 name, but you also can't ping the vm, so it definitely does not have a valid ip.

@DustinB

I use the Import from VMware option in XO to connect to VMware host to import

This is what the Netplan config file looks like before change:

I noticed that when I import a vm from VMware running Ubuntu 22.04, I have to change the name of the nic from

ens33

to

eth0

If I don't do this, XO reports

no IPV4 record found

Although easy to do, it is a painful process if you have a large number of vm's to import.

Is there a way around this renaming step when import vm's?