A paused guest still can have some action in I/O threads or UI, but 15% seems a lot.
None of the automatic logs helps for this. You should gather some metrics which thread is using the CPU and where. pidstat -p $(pidof qemu-system-x86_64) -T ALL -rtuw 5 5 Report that back here on the bug to discuss what it might be. In a check with a paused linux guest that stays <1% for me. If you have more guests up identify the PID of the one in question and use it instead of `$(pidof qemu-system-x86_64)` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851062 Title: Qemu using CPU even when the VM is paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1851062/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
