import of Ubuntu

Danp

And under advance I have tried to change the NIC type to Intel E 1000

This will only have an effect if you don't have the VM tools for XCP installed, which isn't recommended.

bdacasc

bdacasc

@Danp So the VM tools for XCP isn't recommended ?
Why ?
Is that not recommended for all OS or just Ubuntu?
That was the first thing I did when it was not working.

gskger

@bdacasc I think @Danp meant it is not recommended to not install the XCP guest tools. So installing the XCP guest tools is recommended an all OS. In that case (guest tools installed) you can keep Realtek as the NIC type, which is the default for the Ubuntu template.

bdacasc

@Danp I have done the following:
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

And still no IP

Danp

@gskger said in import of Ubuntu:

I think @Danp meant it is not recommended to not install the XCP guest tools.

Correct

@bdacasc So, you've removed the vmware tools and installed the xcp tools? Have you rebooted the VM after uninstalling the vmware version?

gskger

@bdacasc Are the IPs set static at OS level of the VMs or granted via DHCP?

bdacasc

@gskger Fixed IP via netplan

imaginapix

@bdacasc
You have to change the interface name from ens160 to eth0 after migrating a Ubuntu VM from ESXi to XCP-NG.

The file yopu need to edit is /etc/netplan/00-installer-config.yaml

After that type:

sudo netplan apply

With that the network should work again

gskger

@bdacasc You need to update the interface name to eth0 as shown by ip a.

gskger

To slow @imaginapix already answered

bdacasc

@imaginapix

And the deed is done !

bdacasc

Plenty Thx u all !

I can now ping !
Now You have teached me something !

Most greatfull for your help

imaginapix

@bdacasc

Glad to see everything is working now.

Just as a little background:
This problem is caused by the different way ESXi and XCP-NG handled devices. For Ubuntu this causes a difference in the network interface name, for other Linux variants this causes the disk device name to change from something like /dev/sda to /dev/xvda .

olivierlambert

Another win for our awesome community Thanks everyone, I'm really glad to see I'm less and less needed to get threads solved! It's a very good sign

edit: fear not, I'll be always around here