@DevilDan Yeah, you cant change the static min in xoa, it has to be done through the cli

xe vm-memory-limits-set static-min=8GiB static-max=8GiB dynamic-min=8GiB dynamic-max=8GiB uuid=xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx

This is what i did, but like you said, the documentation says i makes no difference.

@DevilDan
We had a similar problem when we tested version 8.3. In our case, it was related to the memory limits of the VMs.

In 8.2, setting different values for Dynamic and Static memory caused a bluescreen.
In 8.3, Windows Server VMs sometimes bluescreened, while both Windows Desktop and Server VMs occasionally froze as you described.

Our VMs were not fresh installs, but we resolved the issue by setting the Dynamic and Static memory limits to the same value (both min and max).

Please do try to see if it solves your problem.

@DustinB You were right; the backups showing as detached are remnants from the backup schedule that I disabled earlier.

The only remaining issue is that the filters show the VMs as "Not Backed Up," even though they are included in the sequences.

I have a set of VMs that I backup using Sequences. The backup schedules are intentionally disabled for these VMs because I only back them up through the Sequences feature.

In the filter view, these VMs are displayed as "Not Backed Up."
Under "Backup > Health" the backups for these VMs are showing as detached with "Unknown Job".

Is this the intended behavior when backing up VMs solely using Sequences? I'm just using a weird configuration ?

Steps to Reproduce:

• Disable backup schedules for specific VMs.
• Set up and run a backup sequence that includes these VMs.
• Check the filter view and "Backup > Health" status for these VMs.

Xen-Orchestra from Sources : commit 4fc97
XCP-ng 8.2.1