Hi Pedro, it is more like "while still running the guest programs the rtc timers" then later on when the guest is paused no guest code runs, but this bit seems to be something the host can't pause continue. I'm not deep enough into (virt)timer programming to explain deeper, but that is how it overall looks to me.
If you follow the threads and bug I linked the discussions there are about e.g. changing devices to cause less of that and/or to consider IRQ storming it when it wakes up (but that seemed to be against some specification). If the guest goes to a proper pause state he is aware of likes S3/S4 it will most likely disable these timers. So it might also depend how exactly you pause things (guest aware or not for example). -- 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
