- The document describes issues that can cause the Xen hypervisor tool "xenwatch" to stall when destroying or creating virtual machines (domUs).
- One cause is leftover "inflight packets" in the network backend driver that prevent xenwatch threads from stopping. Resetting the network interface can help.
- Other potential causes involve idle block tags being unavailable or persistent grant pages remaining mapped due to storage or filesystem issues.
- The proposed solution is to run a dedicated xenwatch kernel thread per domU to avoid locking issues and allow independent processing of events.