Thank you guys! Problem temporarily fixed by Vates support,

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 ?!

Let me ping @team-xapi-network

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

@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.

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

@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.

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

@Pilow error reporting is a feature in itself . Thanks

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.

@MathieuRA Thank you, perfect Br,

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

@hitechhillbilly no it doesn't, it just ensures the N-th vCPU of Dom0 only runs on N-th pCPU of the machine. Not sure about the practical impact of it, in the past it has been used for getting meaningful CPU temperatures from coretemp (with physical core matching virtual one), but that doesn't work anymore since Xen filters MSR accesses (including Dom0).

@Greg_E said in Building XCP-ng from source code: @olivierlambert Ok, thanks. Yes I'm eagerly awaiting XCP-ng 9 for testing. Hi, check this thread: https://xcp-ng.org/forum/topic/11698/xcp-ng-9.0-demonstrator-early-preview More coming...