There is the issue of how the VM is stored. If it is on, say, lvm-thin, then the storage can handle the snapshot and the VM is in raw format. If it is on a file storage like NFS, then the image itself must do it, for example by being in qcow...
No, it still doesn't make sense. Proxmox is somehow supposed to know if this was an "intended" shutdown rather than a VM crash, and do something different in that case. And you want "on demand" machines to have high availability? What the heck...
What is the point of HA if you're going to be shutting the VM down for extended periods and it should not run on a cluster restart? On the face of it this does not make any sense.
The stuff about setting a slightly higher voltage and/or lower frequency in BIOS seems relevant though. It might also pay to look at what c-states are enabled and whether you have the AMD microcode installed.
Other than that I got nuthin'.
It is because he's trying to sync to a Windows DC and per usual Windows does things different. See for example:
https://support.scc.suse.com/s/kb/Synchronize-chrony-with-a-Windows-NTP-Server?language=en_US
If there are any shortwave listeners or ham operators in the house, they will be very upset with you for installing one of those things. They spew RF energy everywhere since they use basically the whole HF band and your house wiring probably...
Why do you care? Is there an actual slowdown of the VM that persists, or is this more of an aesthetic issue where you don't like to see swap use? From a system performance perspective it actually might be a good idea to put some lesser-used...
You should just be able to use a "server" line instead of "pool" in /etc/chrony/chrony.conf. It might be helpful to read the chrony and chrony.conf man pages...
server <ip-of-the-vm> iburst
The thing is, though, that this setup seems kind of...
The command "chronyc sources" will show what sources it is synced to, or if it is not synced.
Example output:
~$ chronyc sources
MS Name/IP address Stratum Poll Reach LastRx Last sample...
Multi monitors work fine for me using xrdp on Debian with the regular Windows client or with krdc. Xrdp is much easier to set up now on Debian 13 since there is now "pipewire-module-xrdp" so you don't have to compile stuff to get sound.
Somebody makes a RAM stick called "G Skill Ripjaws RAM"? LOL! The way PC vendors name things, especially in the gaming space, is pretty hilarious. I mean, wow, it is just a memory stick.
Off-topic, sorry, but I found it funny.
This isn't a question about PVE, it is about configuring your thin client.
From the thin client point of view the VMs are the same as 40 machines. It might be more productive to ask on that vendor forum.
What would be the difference security-wise? You will either have to open a port or go through a third-party server that your customers may or may not trust.
Either way support people will need root access.