Please redirect this bug to wherever relevant. Basically, since F43 we are encountering a new selinux failure [1]
```
type=AVC msg=audit(10/30/25 17:34:09.467:4630) : avc: denied { search } for pid=8234 comm=systemd-machine name=59740 dev="proc" ino=130755 scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:system_r:virtd_t:s0-s0:c0.c1023 tclass=dir permissive=0
```
(more details in the attached avc.txt file)
It seems to impact all tests, so it might be something very early on that is failing.
For more details, we are interacting with libvirt via testcloud [2] which is just a wrapper for the python interface. It does have a selinux handling [3], but I am not versed enough to understand if it is relevant.
[1]: https://github.com/teemtee/tmt/pull/4266 (not sure if you have access to the internal tests there, but we might be able to make the whole run public)
[2]: https://github.com/teemtee/testcloud/
[3]: https://github.com/teemtee/testcloud/blob/f7e6036f5173916723d9aa52a3bc7714950ed312/testcloud/image.py#L258-L272
Reproducible: Always
Reopening because the issue is still present even with `selinux-policy-42.18-1.fc43.noarch` which was supposed to fix this. There is a slight difference with the bug marked as duplicate where that one has `tcontext=system_u:system_r:svirt_t` and this one has `tcontext=system_u:system_r:virtd_t`.
Please redirect this bug to wherever relevant. Basically, since F43 we are encountering a new selinux failure [1] ``` type=AVC msg=audit(10/30/25 17:34:09.467:4630) : avc: denied { search } for pid=8234 comm=systemd-machine name=59740 dev="proc" ino=130755 scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:system_r:virtd_t:s0-s0:c0.c1023 tclass=dir permissive=0 ``` (more details in the attached avc.txt file) It seems to impact all tests, so it might be something very early on that is failing. For more details, we are interacting with libvirt via testcloud [2] which is just a wrapper for the python interface. It does have a selinux handling [3], but I am not versed enough to understand if it is relevant. [1]: https://github.com/teemtee/tmt/pull/4266 (not sure if you have access to the internal tests there, but we might be able to make the whole run public) [2]: https://github.com/teemtee/testcloud/ [3]: https://github.com/teemtee/testcloud/blob/f7e6036f5173916723d9aa52a3bc7714950ed312/testcloud/image.py#L258-L272 Reproducible: Always