@dinhngtu I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os. Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either. I dont know but maybe there is a way to put detect the correct VM template or make note. I didnt think using the win 11 template would have caused issues since using the "wrong" template on vm creation does not have the same effect.

@florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.

@olivierlambert thank for that. Just to be clear the vm was not runing but shut down if that makes a difference. @ph7 Both firewalls are Unifi Enterprise fortress gateways. - https://techspecs.ui.com/unifi/cloud-gateways/efg?subcategory=all-cloud-gateways Both sites are setup with Site Magic VPN. So should be full 1.1gbps if accurate. [image: 1767705099263-screenshot-2026-01-06-081123.png]

@myles3 Hello Myles3. This post is over 20 days old. The issue was since been resolved by support. I dont remember the exact solution off the top of my head with out looking it up.

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso. This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

@acebmxer Great. These are some YAML basics. You should read more about it . Following AI instructions without understanding is not going to take you far.

@olivierlambert Yes I previously was. now back on VHD. This was in my home lab, not work enviorment.

I had to disable Purge snapshot data when using CBT. Backups are not longer defaulting to full backups.

@olivierlambert Thought so just wanted to check. Thank you.

I just want to add that I am seeing the same issue with Ubuntu 24.04.3. Creating a VM does work, but it crashes immediately when trying to start it for setup. I have not yet tried the approach of starting with 24.04(.00) and then upgrading to the lastest version due to lack of time. We are still using XCP-NG 8.2.1 on the server in question. If an upgrade to 8.3 solves the issue, please let us know. Reading the thread, it appears to have the same problem, though. Processor is an AMD Ryzen 9 3900X. We have not had any other issues with the system and it's been running for a few years.

Backup job still failing. I have open a support ticket - Ticket#7746281

@florent yeah that is what i did deploy xo-ce while waiting for a response. I still have 3 more vms to migrate. I so i will continue this route for the migration. Thank you for the confirmation.

@Pilow I thought restarting tool stack affected both host? Either way did try that but on host 1 originally. So i restarted on host 2 (where problem is). still no locked. I rebooted host 2 and that seem to do the trick. Took a few min for garbage collection to complete. All clean now. Thanks.

@florent and @olivierlambert I think it can wait until XO6. I dont have sperate test servers at the office so if I need to spin up a test machine i may want to back it up for testing but not to cloud backup as its only test. Tagging would make this easy since you have tagging implanted. As a work around i could create separate backup jobs for those less important vms.

Yes! That's a good guide for what you want to achieve

Thank you everyone for your feedback, really appreciated!

@acebmxer Hello, We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon. Thanks for bringing this up!

I have no idea what this flag is doing, so my gut feeling is: no, it's not on XO side but a "problem "on the reverse proxy itself.

Before the end of this month.

@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.