Hi Albert,
I assume you already read this topic: Unable to create new virt-manager vm with software TPM on Fedora 40 (corrected link)
I am not 100% sure if it is the same because the other user seems to have been able to still use swtpm once a machine was setup, and the one avc denial they have shown differs from other reports. However, the data of them is too limited to know for sure.
However, the denials of the ausearch you have presented seem to equal that of the bug report: 2272971 – Error starting domain: can't connect to virtlogd: Unable to open system token /run/libvirt/common/system.token: Permiso denegado
Except that you have additionally the swtpm denial.
I suggest to add your data to the bug report: the ausearch output (with the exact command), a short elaboration of your issue, and maybe comparison of with and without swtpm (I expect the difference will be only the one swtpm denial). Also, add a link to here in the bug report post, and vice versa.
This might help the policy team to improve their understanding of the overall issue and its relations.
Supplement/clarification: even if you can run VMs without swtpm, which seems to be not in common among reports, you have the related denials, so I expect your issue to be related (selinux polices have complex outreaches in these areas, and slight changes in the system might make them behave different). Make the points clear in the report, and also add that autorelabeling (which I would have expected anyway) does not help you, but given the avc denials you have logged, I don’t see the need for an additional report.
Also, even if it works without swtpm, check out if the denials are logged anyway or not.
Feel free to give us information here first before filing a post in the report if you want.