@jgrafton said: @laszlobortel We concluded that older Linux kernels plus live migrations plus lvmohba storage seems to trigger the issue. Our workaround was to upgrade to a mainline 6.x kernel packaged by ElRepo https://elrepo.org/wiki/doku.php?id=start for Rocky 8 systems that were especially prone to the CPU hang. The kernel upgrades effectively stopped the issue from occurring. That's ultra helpful interesting @jgrafton Maybe it's even worth a KB/known issue in our official doc, let me ping @thomas-dkmt I suppose https://docs.xcp-ng.org/troubleshooting/common-problems/ might be the right place to document it.

The rule is oddly written, and may conflict with another similar one that already exist in the distro (hence may not be useful to begin with). The modern generic rule for doing vCPU hotplug is, which would be preferable to the current z10-xen-vcpu-hotplug.rules. ACTION=="add", SUBSYSTEM=="cpu", ATTR{online}=="0", ATTR{online}="1"

Good to hear, thanks a lot for your feedback.

@TrapoSAMA https://updates.xcp-ng.org/isos/8.2/ And https://updates.xcp-ng.org/8/8.2/ appears fine.

The same as @john.c and also XO Lite tends to be less a priority because less critical than the full fledged XO (the priority is to replace entirely XO 5 in the next releases). Why you would need XO Lite outside basic actions? It's mostly meant to bootstrap XO itself and do basic operations (which is already the case, at least with many basic features already). Initially, the goal hasn't moved: replacing XenCenter. We are moving in that direction, but again, I think it's more important to get XO 6 finished first. I'm curious to understand more the use case of XO Lite in your context @unreal-shizzle ?

Hi @pierrebrunet. I have deleted the "parentless" VDIs and snapshots. So the "Unhealthy VDI" page is empty for me. So everytime I retry with the VM in question it is creating a new (full) backup-chain. Regards, Marc

@pierrebrunet ticket created https://help.vates.tech/#ticket/zoom/59723