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

@nathanael-h Alright...will take a look

@nathanael-h said in Adding Sysprep Capability to VM Creation Using (Windows) Template:

https://docs.xcp-ng.org/compute/#-gpu-passthrough

Ok...so I don't think this'll work for my needs. How I use GPUs - I have Dell PE R740 Hosts, which I pass NVIDA Tesla cards through ESXi. After installing software in ESXi, I can see the cards in my Graphics Hardware section on my ESXi Hosts so I can then assign graphics to VMs. I then configure VMs to use vGPUs of the Tesla cards on the Hosts. The VMs host AutoCAD & other Autodesk software so this is needed. These VMs I host in a VDI setup using Microsoft RDS. But, it looks like what you all do now won't work...unless I'm missing something?

@nathanael-h Thanks Nathanael...I'll check it out. Appreciate it!

@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

And...when I do export, I use some desktop computer to do so. When you run the tool cmd, you are getting prompted for credentials to vCenter? And, it takes like 10mins or so to export your VM?

@astrugatch hmm...something happening during your export then.

@astrugatch Cool...keep us posted!

@olivierlambert Olivier - I have good information outside your Forums post that it's looking like Veeam supporting XCP is actually going to happen. Are you hearing anything on your end?

That said, aside from lack of Veeam support, there are other features you don't have I require before I can even consider migrating to XCP (GPU support for one; but others as well). Though I don't think what I'm needing would be difficult to implement on your end with the Dev talent you have, I think the issue on your end is rather more of the lack of priority of what I assume is a long list of feature sets of what I need compared to what you all are currently working on to get implemented.

@astrugatch Hi there...I just did this same process a wk or 2 ago and had 0 issues. The cmd I ran to create the OVA was like:

"ovftool.exe vi://FQDN-of-vCenter/VM-Folder-View-Path-To-VM-to-Import/<name-of-VM> C:\OVA<name-of-VM>.ova"

I also ran the cmd to create an OVF similar to above:
"ovftool.exe vi://FQDN-of-vCenter/VM-Folder-View-Path-To-VM-to-Import/<name-of-VM> C:\OVF-folder"

URL I used for reference:
https://www.vmwarearena.com/export-vm-to-ova-or-ovf-using-ovf-tool/

Try one of those and see if it works. The OVA import worked great for me when I imported into XO. OVF isn't supported tho, sadly

Best.

@Andrew Gggrrr...you know what's funny about your response?...I was actually just in the Advanced tab and glossed right over that! hahaha Thanks Andrew