@olivierlambert Interesting, thanks.

@Danp Oh thanks, that makes sense, though I am not sure how I got it to work in the POC... Cold migration will be fine for the time being anyway

@bleader said in Created a new bond interface and lost management connectivity to hosts: The original problem could be a known issue when creating bond including the management interface that we have to investigate. Although the emergency network reset should have fixed that, so maybe it is a mix of the bond creation issue and MTU issue. In the reinstalled pool, did you create the bonds already? If so I would think changing the MTU should be fine, especially as it worked on other PIF, but with MTU issue it is often quite sneaky, so I would not make any promises either. Yes I have recreated them, but I am not game enough yet to change the management interfaces to MTU 9000, though I have done on bridge interfaces for VMs, because I was losing ssh sessions, and this solved the issue. Also, the bonded storage interface is MTU 9000 no problem.

Hello, I suggest you look also for Packer to build ready to use VM templates, with cloud-init, guest tools, and the softwares you'd need. There's a blog post for this https://xcp-ng.org/blog/2024/02/22/using-packer-with-xcp-ng/.

Hi, Indeed, the pre requisite section is pretty clear about it: https://docs.xen-orchestra.com/installation#packages-and-pre-requisites And the error message was clear too: The engine "node" is incompatible with this module. Expected version ">=20.18". Got "18.19.1" However, if you think there's a way to improve this, let us know, we'll be happy to assist

@olivierlambert Thanks!

@olivierlambert Thanks, I see they are there

@olivierlambert Thanks

@Mathieu said in Problem importing ANY ESXi VMDK into Xen Orchestra CE: Just experienced the same issue with a few VMs I imported from VMware. I think it's a Windows issue, from what I can tell. The network adapter type changes after the import in xcp-ng (from VMXNet to XenServer PV), that's normal. Windows do not allow the same IP address to be used automatically for a different type of network adapter, so that's why it reverts to DHCP with the new adapter. You can see that by setting the previous static IP address in the new adapter, it will warn you that the address was used with a previous adapter and asks for confirmation. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/error-message-when-you-set-ip-address No idea if there's a way to avoid that. Yeah same, we're also using VMXNET. When trying to do this manually there's a popup which you have to accept to "force" having the same IP on multiple interfaces. Im sure the IP's are save in registry so deleting the post as part of the process would probably resolve it.

@julien-f Thanks, the VM had been assigned to VIF default with VLAN ID -1, I just had to move it to my Management VLAN VIF : xe vif-move