@carloum70 One option to address the HA error messages: Delete the HA configuration and re-configure it from scratch once the bonds are all configured OK, which it appears you think they now are.

@poddingue Huh.. Good catch. I set all of the VMs to restart, and now it does make maintenance mode possible, on the host. However, when we go into licensed/paid production (soon tm). It would be an absolute nightmare to try and find one VM that might not be on the right HA-plan... And it does kind of feel that Maintenance-mode should be compatible with whatever HA-plan is chosen regardless. Perhaps there could be a way to assign a global/pool-wide HA-plan along with enabling HA alltogether? Update: Shining light on that there is already a feedback-item, wishing for this kind of mass-operation for HA. https://feedback.vates.tech/posts/45/bulk-operation-for-setting-vm-ha-option

@FritzGerald Understood. Thanks for posting. I will get back to this as soon as I have some time.

@henri9813 Hi, There should be a new "reclaimSpace" in next release which help you to clean repositories. Just to let you know, we prefer to not remove orphan backups in case a VM removal is accidental and you want to bring back it from a backup repository

@pandusen said: its scary that GPU passthrough still has a low priority for XCP-ng, during the boom of AI and local LLM Inferencing. As XCP-ng product owner, and someone who sees how much work developers put into such topics, may I ask you to elaborate on this "has low priority" statement?

@ataxyanetwork hey, thanks for sharing this. I am new to the forum so maybe i am not looking in the right place. Your Blog seems to be offline, so did you link the Appliance here in the forum or is it only available on the blog thx

@poddingue Turns out it is all secondary-to-secondary out of sync. So that makes it less intense, though if primary dies I wonder how it will resolve this, or if it will become split brained. Still unsure of how it happened, but the ones I manually cleaned up have not come back. Going to continue to manually clear them up. If it happens again I will have an alert setup to notify me, and I have all the xcp-ng logs and everything to be able to see what happened. If that happens I will post here with details and logs for the resource so we can see how it occurs. [image: image.jpeg]