@MathieuRA I disabled Traefik and reverted to my old XO config (port 443, ssl encryption, http to https redirection), rebuild the docker container using your branch and tested: it is working fine on my end now Thank you very much! I did not expect this to get fixed so fast!

Because doing an update without rebooting doesn't reload the updated main programs, like XAPI. A host in only updated after a full reboot.

@nikade said in Unable to MIgrate VDI when host is low on free memory: Could you please explain the difference between the term dom0 and host? This is what I mean: [image: 1766359127766-ae06dd02-1c5c-44cb-acb0-484503864c6c-image.png] Dom0 is not "the host". It contains a management layer for the host but in reality it is just another VM, highly specialized one but stil just a VM. It does not see host's RAM as it's own.

@MathieuRA Hi I have a support tunnel open right now!

@Pilow error reporting is a feature in itself . Thanks

Yes!! Congrats for everyone (including you for the feedback @dcskinner !)

Let me ping @team-xapi-network

@vaewyn There is an emergency transition to new master xe command. Also, make sure all your hosts are properly time syncronized to each other or there can be pool issues. Try first: xe pool-designate-new-master host-uuid=<new-master-uuid> If that fails, you will need to run on the slave server: xe pool-emergency-transition-to-master

@benapetr Thanks, I will have to play with this when I have time.

Ah indeed, labels are honored even in the case of a warm migration. We used it ourselves when we migrated from Intel to AMD CPUs, it was really the best compromise betweeen live and cold (especially when you change the CPU vendor). Glad to see it's helping many people and companies now

Excellent news

@McHenry Turning off the Manage via Windows update first + tools uninstall + reinstall should take care of it.

@MathieuRA Thank you, perfect Br,

@dinhngtu I believe it was changing the guest TSC Mode that seems to have done the trick.

No idea if anyone have "fixed" anything No, the XO commit 5fcb6 hang for ~3 min at reboot today. edit: I disabled the sceduled reboot yesterday.

Yay! Santa came early this year!!

@olivierlambert said in Xen Orchestra Node 24 compatibility: Can you reproduce the issue on XOA? Or it's only on the sources + your current OS? We do not have a XOA license (yet) which is why I am currently solely using XO from sources. Therefore currently not able to reproduce on XOA. OS is Debian 13.

not better with production upgraded to 6.0.1 (XOA and XO Proxies) we will open a support ticket ps : if we delog/relog from XOA with another user, we have better chance to get the file restore working... not 100% very unstable is there a link ?!