kvm_intel is showing up in the logs but I have an AMD CPU... Is this somehow related to the Back-ported Oracle Vbox fix for Kernel 7.0 ???
Got this message in the logs:
My CPU Info:
kvm_intel is showing up in the logs but I have an AMD CPU... Is this somehow related to the Back-ported Oracle Vbox fix for Kernel 7.0 ???
Got this message in the logs:
My CPU Info:
I guess this is simply a Component of the Program. And like the Message shows: It isn't supported from Your CPU - which is clear because You have an AMD CPU.
Yeah weird though because I never got that message in the logs before with Kernel 6.17.
Usally each kernel progression has new stuff added to support and unfortunatly sometimes bugs but most here are good at helping when those happen.... ![]()
I'm guessing that this is some kind of work-around to load in the Intel kvm as a placeholder for the AMD kvm and then once the system is up and running load in the amd kvm for Oracle Vbox when needed as a fix for the bug.
Not exactly related, but I have found Intel stuff creeping in from an installed .iso.
If you install Synaptic Package Manager, do a search for 'microcode'.
More often than not it will be Intel microcode. I remove this and if not already installed I use AMD microcode as I have an old Ryzen 7 1700X processor.
I also spotted you are using Wayland, which isn't friendly with nVidia graphics. See if things run better in xorg.
Xorg is being sunset... Nvidia drivers have improved... Wayland is the path forward along with newer kernels i.e. 7.x - at least for newer hardware.
I think yo will find I am not the only one that disagrees with you.
.
You might be on to something for older hardware... I have an old laptop that I bought in 2020 that is currently running Windows 10... Microsoft extended the security updates for an additional year until October 2027... When that time is up I plan on installing Zorin OS on it and will probably use the older 6.17 or 6.8 Kernel and Xorg.