If XO from sources, double check you are fully up to date in the first place. You maybe used an outdated V2V code that wasn't asking for the template, causing the issue you experience now.

Keep us posted!

@PaulDCL [image: 1757633451167-9eb17eb5-9a99-4743-9df5-51edcc2b1847-image.png] This benchmark was taken inside the Windows Server VM on that iSCSI device. The iSCSI host is a QNAP NAS with Toshiba 18 TB drives configured in RAID-6. I think this is a decent speed for non-flash storage. Both devices are on a 10Gbit network. If you need more specific details, I'll be happy to help.

I had this tab still open which lets me realize that despite we packaged vmfs6-tools and updated the documentation at https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/#local-migration-same-host, we didn't inform you here. Now it's done

@AtaxyaNetwork I appreciate the sentiment. I think this one is all on me as pointed out by @Danp .. My VDI's would not register without this step. I'm unsure as to why because the error logs were completely blank within XO. Your post in conjunction with the docs were extremely helpful though!

Great! Thanks for the feedback

@Greg_E thanks for the clarification.

@olivierlambert Excellent news!!! I will keep my eyes on that, and provide a tests! Thank you!

Yes, even if there no code, there's a lot of pushing on our end to make it happen on their side

Before the end of this month.

On DOM0 (host xcp-ng) traffic is filtered by iptables. So iptables -L will show which ports are open. Everything else will be rejected by default. For testing, you can stop iptables. If that helps, add rules. Keep in mind that XCP-NG is based on CentOS. So you can easily find an answer on Google for any question.

Fix committed upstream.

@DustinB it's there on mine as well. Going to test it in a couple of weeks. Lots on the docket! Thanks again, everyone.

@afk said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?: Great news ! Thanks @olivierlambert and @florent and let me know if you need some information on the vmware side. yes we are prototyping with vddk , it should open some interesting possibilities. stay tuned, hopefully by the end of the summer (I am saying it again : for a prototype) as a shameless plug, we are looking for users with VSAN to ensure we don't break thing for it

I probably would have just bought a cheap mini PC and used Virtual Box for this, which is something I did do in the past for an old XP machine when the hardware started to fail. Grabbed a disk to vhd of it before the final failure and loaded it into Vbox. Might be able to do this in nested virtualization in XCP-ng.

@iLix The sizing of the VM in XCP-NG was bigger compared to the source

@bpsingh76 said in xen 7.2 vm to xcpng 8.2: We have a VM on Xen server 7.2 and due to some reason we cant migrate it to xcpng. So, we exported xva of the VM, restored it on another xcpng 8.2, restore was successful but when we tried to start, it said no VM. we checked with another it was same. Can someone please suggest solution urgently. Setup Xen Orchestra and use the live migration feature. I have a link in my BIO or you can follow the from sources documentation.

@AlbertK said in MS SQL 2016 migration Question: @DustinB , I am also looking for what are the gotcha or limitation that one have to look out for and plan before even looking at migration. So as @tjkreidl said, use the same considerations that you would use for Hyper-V or VMware, those same considerations were completed by someone, at some point. There are a few assumptions we can make though: You're either planning to reuse your existing VMWare hosts OR are getting new hardware This hardware is going to be able to support everything you have today +20% increase in workload over 5 years Things to do ahead of a migration, assuming you're migrating an existing VM from VMWare to XCP-ng. Uninstall the VMWare drivers from the guest ahead of time If you aren't licensed by VMWare for Hot-Migration, plan downtime to shut the guest off as you will not be able to migrate it live from VMWare (VMWare restriction). Setup your XCP-ng host with all networking ahead of any migration, VLAN configurations, Management interface statically assigned, PIFs bonded ahead of adding any VMs etc. Create your pool with all hosts first - ideally each host will be identical (same hardware configuration) Install XCP-ng on each host Setup Xen Orchestra and connect to each host to XCP that will be in the pool Select a host to be your pool master (this can be changed later) Add the remaining pool members to the pool Shared Storage for your VMs is configured and attached to your XCP-ng Pool for both ISO's and VMs Use an SSD array if you can for the best performance Use a Standing Spinning array for the "C" drive Everything else is pretty straight-forward, hope this helps.

On vmware u would need als vcenter for this kind of features. And as u can easy deploy an empty xoa, why would this be an issue?

@olivierlambert nice catch It's following a dependencies update, removing an old one ( node-fetch ) . The fix should be merged this morning ( with the ability to resume an import ) https://github.com/vatesfr/xen-orchestra/pull/8440 fbeauchamp opened this pull request in vatesfr/xen-orchestra closed feat(v2v): resume an incomplete import #8440