@kagbasi-wgsdac Normally, this issue has already been fixed upstream since a long time. XS tools 9.4.0 is pretty old, you should update to 9.6.0 which should contain a newer Xenbus balloon driver. Better yet, you can switch to the XCP-ng tools (as you've done), since the XCP-ng tools are what we now recommend for all Windows guests. A new version of the XCP-ng tools is coming out soon with lots of improvements. You can check for the driver version by running this command on the host: xe vm-param-get uuid=<VM UUID> param-name=PV-drivers-version For XS 9.6.0, I'd expect it to report xenbus: XenServer 9.1.13.23.

@poddingue Olá! The failure has a fixed duration of 5 minutes.

@poddingue, that is true, my first post here. I'll try to play with these BIOS settings again. and keep you posted. Cheers

More options: to Prevent overwriting the file: Method 1: Probably the best option. Use a Configuration Directory. Modern OpenSSH versions (8.2+) support an include directive. This is the cleanest approach. Create a drop-in file: Put your custom settings in a separate file, such as /etc/ssh/sshd_config.d/custom.conf. The rule: Package updates will not touch files inside this directory. Verification: Ensure the line Include /etc/ssh/sshd_config.d/*.conf is active at the top of your main /etc/ssh/sshd_config file. Method 2: Lock the File (Alternative) You can force the filesystem to make the file immutable so nothing can change it. Lock the file: Run sudo chattr +i /etc/ssh/sshd_config Unlock for edits: Run sudo chattr -i /etc/ssh/sshd_config when you need to make intentional changes. Method 3: Tell Apt to Ignore Updates. If you are on a Debian-based system, you can force the package manager to always keep your local version. Add this line to /etc/apt/apt.conf.d/local: UCF_FORCE_CONFFOLD=true

@olivierlambert Are there extra steps to get the load balancer to read and honor the affinity tags? I have VMs with set affinity and the load-balancer plugin completely ignores them. I see that there are tags for affinity and anti-affinity, but those drop-downs are blank despite having affinity set on some VMs.

Drivers are actually in @Team-Hypervisor-Kernel scope nowadays

After trying a few more restores the other vms did not get this name change. Not sure why it happened to the one vm, but the other retained their original names and tags.

Du coup j'ai testé avec RHEL 9, ça fonctionne aussi. Faut bien prendre l'iso "dvd", pas "boot" en revanche ! (je me suis fait avoir en téléchargeant l'image)