Unfortunately, I am still seeing the issue after making the update provided by py0xc3 above. Attempting to start up an existing VM that had been working prior to F40 (and for several days post F40). (attempted several times, but these are the last 3 attempts).
sudo ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today
----
type=AVC msg=audit(05/03/2024 09:31:18.436:387) : avc: denied { create } for pid=7038 comm=swtpm name=6-Eyre-swtpm.sock scontext=unconfined_u:unconfined_r:svirt_t:s0:c150,c949 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=sock_file permissive=0
----
type=AVC msg=audit(05/03/2024 09:59:23.626:388) : avc: denied { create } for pid=10142 comm=swtpm name=7-Eyre-swtpm.sock scontext=unconfined_u:unconfined_r:svirt_t:s0:c599,c753 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=sock_file permissive=0
----
type=AVC msg=audit(05/03/2024 10:03:58.365:406) : avc: denied { create } for pid=10939 comm=swtpm name=8-Eyre-swtpm.sock scontext=unconfined_u:unconfined_r:svirt_t:s0:c714,c798 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=sock_file permissive=0
For clarity, these lines were created when I attempt to “run” the QEMU/KVM User session for the VM named “Eyre”
Steps taken so far: run sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f53eab6892 and restarted my system
running again I get that there’s Nothing to do. Complete!
I also attempted to define a new user session VM using the same disk image, but ran into similar tpm errors. Is there a way to verify that the FEDORA-2024-f53eab6892 update is in place?