@User-cxs dans ce cas en l'occurence de coupures intempestives au niveau réseau (scrute de plus pret le routage entre ces 2 subnets (j'ai supposé que c'etait du /24)) tu peux avoir le comportement erratique ou tout disparait et fini par revenir monitore un ping du xoa vers les hosts, voir si tu as des pertes de paquet de temps en temps. au moment ou les hosts disparaissent, essaie de pinger les hosts depuis le XOA... a mon avis un probleme de réseau quelque part...

Okay waiting for your feedback

@MathieuRA Dont think you pushed this already unless i am mistaken. But on Commit 9226c One vm populates the backup second on dashboard while the other do not. this happens to be the same vm check to confirm your changes. I dont recall if i checked other vms. But on Commit 9226c 1 vm dashboard loads correctly.

@Andrew the NBD warning is probably doable. the other solution is not : NBD is mandaotry to use CBT ( the fallback with export can't work without a real snapshot )

yes, the last changes are released in latest ( 6.3) tomorrow if everything proceed as intended mostly : https://github.com/vatesfr/xen-orchestra/pull/9622 https://github.com/vatesfr/xen-orchestra/pull/9557 and this one was in 6.2 : https://github.com/vatesfr/xen-orchestra/commit/e36e1012e20c9678efa15148179941cb284c39a6 that's nice to hear fbeauchamp opened this pull request in vatesfr/xen-orchestra closed feat(xo-server): use index for getAllUnhealthyVdiChainsLength #9622 fbeauchamp opened this pull request in vatesfr/xen-orchestra closed fix(backups): better handling of generator cleanup #9557 0 fbeauchamp committed to vatesfr/xen-orchestra fix(xo-web): reducing polling for patches and license

@User-cxs said: when I want to shut down a node with VMs on it, the HA will cause the following We are still waiting for your question. P.S. The solution is in the GH issue that I previously linked.

Good moaning... The solution was pretty simple: a toolstack restart on the master (xcp83) did get all back on track and it now allows me to move the systems with a simple shutdown/start.

Not sure the issue, but rebooted the host and everything is fine again. I definitely had rebooted the host twice though after applying the patches and physically unplugged and moved the host.