Recent content by BobhWasatch

I don't see any question in your post. Could you clearly state what the issue is?

It is very likely to be swapping things out that then never get swapped back in. In which case there's no harm being done, and a slight good in that there's more RAM for caching.

The pvesm command is in /usr/sbin, which is not on the default path for a cron job: * * * * * /usr/sbin/pvesm apiinfo

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 format rather than raw, because NFS itself doesn't do...

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 does that even mean? HA is not intended to be just...

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'.

Googling "software wrote 0xE to reset control register 0xC" leads to some interesting info.

You might be the only person running frr directly on their PVE host.

NVidia card? Those are known to have issues with Wayland.

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

The chronyc sources output says it isn't synced (left-most column).

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 isn't shielded at all (why would it be?). Just wanted...

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 things in swap in order to have cache on a slow device.

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 brittle to me. Your cluster time will depend on that...