@astrugatch At this point, I'd submit your ova to the Vates team as they requested to have them look inside it to verify you're exporting what is needed to be able to import into XO

@olivierlambert I'll ask for an update in the Forums post and see what they say...

@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!

In the Tasks section of XO (on sources), all tasks displayed show as "Failed", even though quite a few have been successful (VM migrations, for example). How do I display Successful task completions as well (or simply, All tasks)? There is no filter set.

Also, I ran a "Running Pool Update" yesterday afternoon. Thankfully, it seemed to have ran & completed without issues. But in the Tasks area, for this Task it shows the completion bar still. Any idea why?...or what I have yet to do to finalize it? And of course this "task" also shows as failed even though both my XCP Hosts show as current with no patches needing installed.

Thanks!

@ph7 Thanks for the tip! Appreciate it.

@olivierlambert Hey Olivier...I came across another issue today on this XO VM. Not sure if you recall...but a week or so ago I created a post on here on how best to import an XO VM from VMware to XCP. I ended up finding a 'klunky' way to do so using the OVA import process. So this is the issue I encountered -> when I imported this VM, the import process changes a couple things in the guest...the vnic name in the Linux OS gets changed (from like ens# > enX#), and for the VM to see the network, the netplan config file needs to have the nic name/label changed in it. Another issue occurs..and this the main thing I wanted to share here -> the disk device name in the Linux OS changes as well from /dev/sd# (sda1, sdb1...whichever) to /dev/xvda1. Why is this a problem? Well, I was going to do a XO update this morning. Before doing so I thought it would be good to update my Ubuntu 24.04 OS. I ran sudo apt update && sudo apt upgrade -y and it failed. Why? An EFI pkg can't find the boot partition it seems. I get the following error: mount: /var/lib/grub/esp: special device /dev/sda1 does not exist. ; and then dpkg: error processing package grub-efi-amd64-signed (--configure): as well as dpkg: error processing package shim-signed (--configure) The root of those 2 pkg update issue stems I believe from the disk device label/name changing. For anyone who imports Linux VMs and performs an update/upgrade, they'll run into this error and will not be able to update their VM. The server is fine...you can log into it; apps still run; etc....but you can't install any package or update any package. Are you all aware of this?
Thanks.

And again..I expect a momentary "blip" during migration for obvious reasons. But, it should still be able to recover through that and eventually succeed; and realistically, not in several minutes (10+min), but like other VMs...within a minute or 2. But...at some point, I may download a trial of XOA and attempt migration. I just don't have any other phys hosts to test with. I guess I can remove my current ones temporarily from my current Pool and XO then add them briefly to the XOA...we'll see.

@olivierlambert Hmm...ok. Yes, I'm using "sources" version. Why does it matter which? Both are a Linux OS with the XO app on it, correct? It's just one is manually created & other is applianced-based; but you can still SSH into each the same, correct? Of course, I may be way off there

@olivierlambert Yep..agreed. I may test this behavior out again to be sure what I think may have happened...was indeed my issue with regards to the non-tools VMs vs Tools VMs.

For the XO VM though...it would be highly beneficial to have the ability to live migrate that to other XCP Hosts in a pool for obvious reasons (update/maintenance). Can that be looked into, please?
Thanks!

Sorry for all the comments/posts...but I think I may have figured out why the failures occurred. I can again live migrate VMs after I shut down my XO VM then rebooted both of my XCP Hosts. Of course, I've not re-attempted live migrating my XO VM. Too risky! Again, that should be fixed.

One of the requirements of live migration is guest tools needs to be installed, correct? So, it appears..if an attempt is made to live migrate a VM which doesn't have tools installed, it "hangs". I have several VMs like that. They're software appliances and currently I'm prevented from installing tools on them. After the non-tools installed VM hangs attemping a migration, if you attempt to live migrate a VM which does have tools installed, it will also hang...and my guess is because of the failure of the 1st VM without tools installed. Not sure why. If that is the case, that needs to be fixed as well. If this is not accurate, I would like to know why this migration hang/failure behavior occurs. I can re-attempt to live migrating a VM which doesn't have tools installed...but don't want to go through the hassle of powering everything down and rebooting my Hosts to get it working again

Now that my XO VM is back up...I tried to live migrate some of my VMs in my Pool and migrations are failing (Linux & Windows), and I can no longer see the VM's console. They're basically "hung" it seems. And, I can't power them down. The same behavior has now happened to them as my XO VM. Live migrations did work ok before the issue I had with my XO VM.

I got the XO VM back up by rebooting my Pool Master XCP Host which forced the VM to shutdown. Not thrilled this happened. Migrating the XO VM in XO needs work. So, for the process of rebooting XCP Hosts after applying patches, either via RUP or manually, use the following process (Vates Team correct as needed):

1. Apply patches
2. Migrate all VMs off the Master XCP Host. If the XO VM is on
this Host, do not migrate
3. Log out of XO
4. SSH into the XO VM and shut it down
5. SSH into the Master XCP Host and reboot it
6. Log into the Master XCP Host XO-Lite after the Host comes back online
7. Power the XO VM back on via XO-Lite
8. Once XO is up, migrate VMs back to Master XCP Host as needed
9. If Master role changed to another Host, from the Pool >
Advanced tab, change the Master back to desired XCP
Host
10. Reboot other XCP Hosts in Pool to finalize applying
patches. Before doing so, make sure to migrate VMs off

@olivierlambert And, below is the msg I get when I attempt to force shut the XO VM down directly on each XCP host:

xe vm-shutdown name-label=nkc-xo force=true
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Object with type VM and id 95ad90cc-85b0-98c6-d81d-61ba82742947/config does not exist in xenopsd