VMware migration tool: we need your feedback!
-
@olivierlambert to be clear as i mentioned in my post, the VMs are shut down.
-
Are you using XOA on
latestchannel? My question holds regarding the presence of a snapshot for this VM
-
@olivierlambert just about to edit my comment
There are no snapshots. I shutdown the VM at the time.
-
@florent will take a look tomorrow (it's V-day here)
-
@olivierlambert Understood. I also have a support ticket open as well to track.
Has this been tested on ESXi 8.0.0 ?
-
I'm not sure, but without any delta mode (no snap and VM halted) the format (full) should work. Maybe there's something else in 8.0
-
@olivierlambert the plot thickens. I’m still in POC mode so no production impact. With so many VMs I would like to transfer and test the migration tool would be helpful.
Anyways, I’ll wait for your testing. Enjoy the holiday -
yep I had no snapshots my side either and same error
-
@olivierlambert hello! I don’t have the patch pushed to my XOA. Do I need to do anything to get the fix? I have the support tunnel open
-
Well, you have to wait a bit for @florent to put the patch on your XOA, and since you are on the community forum and not with pro support, you have to be a bit patient until we can do that on our free time
Stay tuned and keep the tunnel opened At worst, we'll have a patch release in XOA this week (Friday maybe).@Flying9167 this is now fixed on
masterbranch. -
@olivierlambert woohooo! Thank you team - have just tested on XOA built from sources and its working!
If I give my XOA more CPU and/or RAM will it speed up the import? Is it bound to the resources of XOA? I'm getting 7.5MiB and have got 20MiB before but no more. My hardware (both sides) does support reads and writes at over 500MiB across my 10Gb link.
-
It's XO from the sources, XOA is Xen Orchestra virtual Appliance
(the turnkey thing you deploy as a VM directly)Regarding the speed, it depends but since we have to read from Vmware API, then convert it on the fly, then read twice to avoid thick provisioned, it's not fast. However, you can have warm migration if you have VMware 6.5, so it's kind of automatically spawn on destination when done.
-
@olivierlambert Oh roger that, I didn't realise the distinction!
-
@olivierlambert Ahh ok. Im still new to the whole process here so forgive me.
Can you clarify something for me? I have premium support now but im on the community forums (here). Is there another channel i can use to get the issue addressed in accordance to my license level (community vs preimum). Does this affect the open ticket i have with support? -
If you have XOA with pro support, the first reflex is to go for the pro support and create a ticket. You have the guarantee to have an answer and dedicated resources given in a reduced timeframe.
Here, it's only "a bonus", and we try to help, but there's 0 guarantee.
-
the test with @dumarjo showed that there is still a bug during the import. I am still investigating it and will keep you informed, hopefully today or tomorrow
-
@olivierlambert Ok i see now. xcp-ng.org vs xcp-ng.com. Community vs Pro.
I will keep the existing community POC in place. How do i pivot to Pro? Do i reach out to your amazing team for the iso along with support contract?
-
It's off topic but you have both Xen Orchestra and XCP-ng pro support (because they are done by 2 different teams). We can provide bundles with both so you are entirely covered in your infrastructure, not just when you have a problem, but even discussing before about migrating, best practices and having our feedback/advice directly to build the best of the entire stack
Feel free to contact us if you want to know more -
@olivierlambert Yep i am escalating to sales here.
I think I started off things incorrectly. It was my assumption that XO being the hypervisor is the product that's free and the XOA is the licensed product. -
No worries, it's not trivial if you don't know anything about our stack, that's why we are working on creating a more unified identity through the Vates stack/Vates virtualization, with everything included (like vSphere includes ESXi+vCenter, Vates Virtualization will include XCP-ng+XO)
