@olivierlambert Ok, will do. Thanks!

I used the XO "Import From VMware" tool. I performed this on 3 VMs with no issues encountered during import. But, post-import, there are some as noted in the following:

1. On 2 Ubuntu VMs, v22.04 and v24.04, I am unable to boot the VM after import because XO assigns the VMs the "secure boot" option. The VMs are not configured for Secure Boot in VMware. I disable this option in VM > Adv tab, reboot and it then boots ok, but this is an issue which should be addressed. Maybe it's only for UEFI-based VMs?
2. When attempting to install Guest Tools via ISO. I can attach the ISO to the VM, but when I run the "sudo mount /dev/cdrom" cmd, it states "special device /dev/cdrom does not exist".
3. I then try to eject the ISO and receive an error like "<some character string>/vbd.xvdd does not exist in xenopsd."
4. The NIC of these imported Linux VMs is down after import...not sure why. I place it "up", but even so...they do not receive an IP address. I imported a Windows 2022 server and it did get an IP address, but it also has the eject ISO error as well.

Any thoughts on how to resolve these issues. If I choose to migrate from VMware,, this would be a huge deterrent to doing so.
Thanks!

@lawrencesystems @olivierlambert
Thought I'd provide an update here...only fair

After getting everything running again, I was able to add 2 physical XCP Hosts to XO and get things going -> create a Pool; create some VMs; test Live Migration (not VDI-based yet); import from VMW (an issue there with Linux); but overall...able to dive into it a bit deeper and see how things in XCP/XO work vs VMW. So far, after getting through my initial issues...I think it's ok

I think my Host2 network issue may have stemmed from attempting to add it back into XO when I was no longer seeing it in the Settings > Servers area after adding it to a Pool. I wasn't aware it would disappear from that area when adding it to a Pool. I don't think the documentation states this (unless I overlooked it? if not, would be helpful I think). Anyway...thanks to all for chiming in!

@olivierlambert Ok, will do. Thanks!

@olivierlambert No problem at all. I'm documenting as I go. I have some feature requests I think should be added to XO to make it more intuitive. How do I go about doing that? Create a post here or submit somewhere else?
Thanks.

UPDATE: I see in the XO docs on how to:
https://beta.xen-orchestra.com/docs/community.html#feature-requests
Seems it's best to do so here with relevant info. I'll do it in batches so as not to overload on volume of posts

@olivierlambert -
I have resolved the CD device eject error/issue...by guessing To resolve the above error, for any VMware VM that is either migrated (V2V) into XO or imported (via .ova file), do the following:

1. After migration or import, power the VM on if not already.
2. Resolve the NIC issue (for Linux; see the Netplan discussion above) and verify the VM (Windows and Linux) attain an IP
3. Install the XO Guest Tools for Windows downloaded from the Citrix site and via install cmd for Linux (Ubnt = sudo apt install xe-guest-utilities -y) and reboot the VM(s)
4. Once the VM is up and you confirm Tools is installed, simply power down the VM, then power it back on. For Windows VMs, if an ISO was connected when shutting down, it will be disconnected upon startup. You can test connect and disconnect an ISO and it should eject fine; for Linux, if an ISO was connected when shutting down, it will still be connected, but you should now be able to eject the ISO.
5. Also note, I had the mount error in Linux VMs with the /dev/cdrom as well, but that error also gets resolved after performing the VM shutdown

Thanks!

I was able to find a post which discussed the known NIC issue in Linux imported VMs (by Brandon Lee):
https://www.virtualizationhowto.com/2024/02/migrate-from-vmware-to-xcp-ng-a-vsphere-admins-perspective/

It kinda makes sense I guess why this happens -> the NIC is given a static name in Netplan initially when the VM is created. When the VM is migrated/imported into XO, this Netplan NIC name is NOT changed in the Netplan .yml file during migration, thus the OS can't get an IP. To rectify this, change the name XO gives the NIC in the Linux OS (eth0 for Ubnt2204 or enX0 for Ubnt2404) in the .yml file, reboot the VM, then you'll be able to get an IP if you use DHCP. You can then also install Guest Tools by using a pkg mgr (apt for Ubnt).

The only remaining problem I'm having now is the CD eject issue. And again..this is on both imported Linux and Windows VMs.

I did some researching on possible resolutions -> running the xe vm-cd-eject cmd on the XCP Host doesn't work..I get the same error as in XO. I also verified the VMs I migrated from VMW did NOT have an ISO attached to them prior to migration. I should also say I got this same behavior even if I exported the VMW VMs to .ova then import them to XO.

I used the XO "Import From VMware" tool. I performed this on 3 VMs with no issues encountered during import. But, post-import, there are some as noted in the following:

1. On 2 Ubuntu VMs, v22.04 and v24.04, I am unable to boot the VM after import because XO assigns the VMs the "secure boot" option. The VMs are not configured for Secure Boot in VMware. I disable this option in VM > Adv tab, reboot and it then boots ok, but this is an issue which should be addressed. Maybe it's only for UEFI-based VMs?
2. When attempting to install Guest Tools via ISO. I can attach the ISO to the VM, but when I run the "sudo mount /dev/cdrom" cmd, it states "special device /dev/cdrom does not exist".
3. I then try to eject the ISO and receive an error like "<some character string>/vbd.xvdd does not exist in xenopsd."
4. The NIC of these imported Linux VMs is down after import...not sure why. I place it "up", but even so...they do not receive an IP address. I imported a Windows 2022 server and it did get an IP address, but it also has the eject ISO error as well.

Any thoughts on how to resolve these issues. If I choose to migrate from VMware,, this would be a huge deterrent to doing so.
Thanks!

@lawrencesystems @olivierlambert
Thought I'd provide an update here...only fair

After getting everything running again, I was able to add 2 physical XCP Hosts to XO and get things going -> create a Pool; create some VMs; test Live Migration (not VDI-based yet); import from VMW (an issue there with Linux); but overall...able to dive into it a bit deeper and see how things in XCP/XO work vs VMW. So far, after getting through my initial issues...I think it's ok

I think my Host2 network issue may have stemmed from attempting to add it back into XO when I was no longer seeing it in the Settings > Servers area after adding it to a Pool. I wasn't aware it would disappear from that area when adding it to a Pool. I don't think the documentation states this (unless I overlooked it? if not, would be helpful I think). Anyway...thanks to all for chiming in!

@FMOTrust I had this issue as well on a Slave host in my test environment. I was able to do Network Reset from xsconsole, but then after the Host rebooted to finish the reset, the Host reverted back to not having/seeing the Mgmt network, and...like you, I couldn't see any NICs either.

Since this was for testing, and I had no VMs on it, I just reinstalled XCP. I think there's a way to reset XCP I saw in another Forums post by removing the Local SR? Olivier shared that in the post..but I don't remember what post it was.

Not sure if this is a test or prod Host/environment for you...but if you can, unless someone from the Vates team comments, I think all that can be done is reinstall.

@Danp Understood...and that's what I did (in XO). Thanks!

@Danp Ah ok, understood. Does XCP use netplan for Linux networking mgmt? I know how to rename pNics in that. Maybe I just do that and it'd be easier? I rename pNics for other Linux devices I use for Veeam backup components; so it would be no big deal to do here if possible before I even start adding the XCP Hosts to XO. But, I guess as long as "logically" within XO I see the pNic name what I want so I know what it is...all good.
Thanks.