CentOS

Update... between 8.4 and 8.5, Centos integrated kernel kernel-4.18.0-331.el8 (ttps://git.centos.org/rpms/kernel/c/eff38ce94f417944a493ce131c5df27f6aec40c8?branch=c8s). That included changes from RHEL Bugzilla 1980072: + - hwmon: (k10temp) Zen3 Ryzen Desktop CPUs support (David Arcari) [1980072] + -...

OK, so I'm back to CentOS-signed k10temp as noted. I blacklisted it in /etc/modprobe.d, and rebooted. System comes back clean as expected, no errors. Sensors output as expected has no k10temp output. If I modprobe k10temp and run sensors I immediately get pages of kernel traces, and the sensors outp...

Yes. My normal process every kernel update is to re-run make / make install / modprobe k10temp using groeck's k10temp github repository... which "normally" recovers sensors Tdie and Tctl output after kernel upgrades lose them. More troubleshooting after chatting with groeck at https://github.com/gro...

EDIT: also does not work with stock k10temp, not just groeck's version. I've had CentOS 8 working for about 18m with a Ryzen 7 3700. I got temp monitoring working using k10temp from https://github.com/groeck/k10temp, and it's been reporting Tctl and Tdie no problems. Last week I updated to kernel 4....

Your post is a little hard to read all embedded in code tags. Suggest editing to have only the actual command line content tagged...

I do note though that I have two running libvirt services: libvirtd and libvirt-guests. The Red Hat article notes: Start libvirt-guests service If you have not started the service, start the libvirt-guests service. Do not restart the service as this will cause all running guest virtual machines to s...

I'll try again... the reboot will have done that. I assume that restarting the libvirtd daemon is destructive to any running VMs? EDIT: answered my own question from man page: Restarting libvirtd does not impact running guests. Guests continue to operate and will be picked up automatically if their ...

My CentOS 8 KVM host runs 5 x VMs, all of which are running CentOS (versions from 6 to 8). I prefer to have the host shut down the guests on a reboot, as I have found not all of the services always like coming back from suspend. I have followed the change suggested in https://access.redhat.com/docum...

OK, I've done it a little differently :) I've commented out the fstab entry for /boot/efi completely, and have a cron job running a tiny script every two minutes which checks whether /dev/sda1 is mounted. If it is mounted nothing happens. If it is NOT mounted, it firstly attempts to mount sda1 to /b...