On a Friday in 2025, Nathan Chen via Devel wrote:
On 12/18/2025 6:19 PM, Nathan Chen wrote:Changes from v2: - Set per-process memory accounting mode for iommufd - Separated out formatting of iommufd object from qemuBuildHostdevCommandLine - Placed hostdev private data implementation in a separate commit - Allocate hostdev private data unconditionally - Compare FDs against -1 - Integrated callback function in virQEMUDriverPrivateDataCallbacks for qemuDomainHostdevPrivateNew - Dropped qemuProcessCloseVfioFds - Addressed other feedback from v2 (formatting, includes, etc.) - Revised seclabel logic to be device-specific for AppArmor and to allow paths for SELinux/DACI have found a bug with this series where attempting to boot an iommufd VM a second time immediately after shutdown fails with an error binding device fd to iommufd with "File descriptor in bad state". It does not occur with the previous libvirt revisions. I will investigate and resolve this before the next refresh.
Interesting; could it be related to closing the file descriptor later as I suggested (i.e. in qemuDomainHostdevPrivateDispose?). Maybe it gets called too late by libvirt, or some cleanup in the kernel takes too long? Jano
Nathan
signature.asc
Description: PGP signature
