@gduperrey

Thank you for the reply. Work uses XOA.

Edit - Support ticket created - Ticket#7755004

@gduperrey

When applying updates at work. I started with first pool and choose the rolling pool updates and ran into issue after fist host came back up the second host didnt enter maintenance mode and the operation appeared to have just stopped. I then manually put host 2 in maintenance mode and applied updates. Once updates finished it restated the tool stack and took the host out of maintenance mode. I put it back into maintenance mode and rebooted the host. Once it came backup no migration occurred as expected to bring vms back to host2.

Moved on to pools 2 and 3 and just did everything manually. Each time load balance appears to be broken now just like home lab.

I have rebooted XOA deleted load balance config. rebuilt using different name and still no load balance.

Once manually migrated vms back over to second host in all three pools all seems ok.

Found issue in my script all seems to be working now for me just no vmware vm to test import on

@edsilber

Yeah I am not sure. I havent seen heard anyone else having similar issues. I heard of other issues in regards to the actual migration but not the setup.

Now that you have logs posted maybe someone form Vates will chime in.

I just tried with my install and i get stuck on first step... Not sure if because of my script or there is an actual issue...

Edit - Just booted up XOA on home lab. It looks like i had attempted to setup previously so can test there. Work XOA again was already setup prior for actual migration. See what other say.

@edsilber

This is from a fresh install of XO from sources...

this should have walked you through the process to import from vmware.

@benapetr

If you are still having issues you can try the script i created to install XO from sources. I would advise not running in production, But i have been using it for a few weeks in my home lab and havent ran into many issues.

https://github.com/acebmxer/install_xen_orchestra

@User-cxs

Assuming you enabled nested virtualization on the xcp-ng host you also need to enabled in the vms bios settings for windows.

Install went with out issues on my homelab pc windows 11.

I used the installer found in the package folder.

@Pilow

While that could be true only 1 vm was shuffled to another SR. But all VMs now being backup with CBT enabled.

Well... i just check again at backups and after the last scheduled backup at 1am all vms fell back to full backup again.

Now delta backups are working again. I tried re-enabling CBT so far so good. Still did a delta backup snapshot was removed no errors.

Maybe someone with more knowledge could explain why its working now.

2026-03-12T00_32_16.994Z - backup NG.txt

all but 1 vm is on host 2.....

with the current above setting for home lab.

said:

When creating vm in v6 and renaming the disk name. You can only enter 1 letter at a time. You have to keep clicking then typing the next letter. No other field has this issue.

This is still an issue in the latest commit - 2cd5ba0

said:

When creating new vm in XOv6 it does not set the correct number of cpu's....

I set 4 cpu's and after creation there is only 1. Also the ISO image is not mounted after creation.

This issue was fixed in commit - 2444861

@MathieuRA

Glad to see this finally fixed. I brought this up a while ago...

https://xcp-ng.org/forum/post/102102

After shuffuling a vm around on differen SR I started another backup job and all vms failed back to full with CBT disabled in backup job.

When the following schedule back task started all vms did a delta backup.....

Screen shots from works Load Ballance plug settings...

Latest update using RPU all vms moved off master onto second host. After reboot host 2 moved all vms to master after reboot half the vms moved back over to host 2. This happend on 3 pools with 2 host each.

From home lab with latest changes i tried..... Started with same settings as work....

@majorp93,

I am in the process moving a vm to new SR to see if that would make a difference. I cant recall 100% but i am sure i had cbt enabled before. I just double checked works backup and cbt is enable there with no issue.

Once migration is complete i will try again with out CBT.

I have forced a full backup and then did another delta backup and still delta backups are falling back to full backups.

Updated work servers 3 pools 6 host with Rolling Pool Update.

Not sure if related to this. But now all my vms are failing back to full backups.

Attached is the first backup when all vms fail back full backup and the most recent backup log. All backups in between were full backups.

2026-03-07T05_00_00.117Z - backup NG.txt

2026-03-10T04_00_03.845Z - backup NG.txt

Backup file before vms fail back to full.
2026-03-06T21_42_15.233Z - backup NG.txt