Recent content by BobhWasatch

https://ubuntu.com/download/server?pubDate=20260418#system-requirements-tab-lts 1.5 GB system memory 5 GB of free hard drive space Either a USB port or a DVD drive for the installer media I guess not only does nobody read the instructions, they don't even read the wrapper.

While it may not have messed with the network, it may have messed with the web page. Some of those scripts purport to remove the "nag screen" and as a result they can cause problems when PVE is newer than when the script was last updated.

Maybe because it is the installer default if you have a single disk.

This is that section of my /etc/network/interfaces. You need to use "nano" or "vi" to edit yours to look similar. Replace the "bridge-ports" line with whatever the name of your Ethernet device is (mine being enp191s0) and the address and gateway with ones appropriate to your network. iface...

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