On Wed, 28 Jun 2023, Sean Christopherson wrote: >Dropped all the old maintainers from Cc. This is one of the more impressive >displays of thread necromancy I've seen :-) Well, I found that mail, and it specifically mentioned users not having reported seeing this message, so… >> Full dmesg attached. This is on reboot, no VMs are running yet. > >Heh, there are no VMs that _you_ deliberately created, but that doesn't mean there >aren't VMs in the system. IIRC, libvirt (or maybe systemd?) probes KVM by doing >modprobe *and* creating a dummy VM. If whatever is creating a VM also creates a >vCPU, then the "soft" warning about KVM_SET_TSS_ADDR will trigger. No systemd here, but libvirt might be it. There’s significant time between the last kernel messages and this, that would explain it. >So long as the VMs you care about don't have issues, the message is completely >benign, and expected since you are running on Nehalem, which doesn't support >unrestricted guest. OK, thanks. Might want to make that more well-known… though I don’t have a good idea how. Perhaps the next person to run into that message will, at least, find this thread. bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg **************************************************** /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption! ****************************************************
