On Tue, Jan 13, 2026 at 09:47:48 +0530, Akash Kulhalli via Devel wrote: > I'd like to resurface an earlier proposal [1] to make the unplug timeout > user-configurable. With production guests running sustained, non-trivial > workloads, we find that hot(un)plug operations regularly takes longer than > the > current default of 5s. However, the inability to easily configure this > timeout
Since hot-unplug is an asynchronous operation and we already have an asynchronous API (virDomainDetachDeviceAlias) I think that is the proper solution. No amount of timeouts will fix the inherent problems with it being async and guest-OS controled. > means that in the worst case a recompilation with appropriate values set is > required for each deployment, which is cumbersome to maintain and patch. You really shouldn't do this. If your application does care about the unplug you need to wait for the event and use the async API.
