That is great data to have @Kevin, thank you. There is no problem at all that you've done that with some slightly other versions.
The loop around KVM_IRQ_LINE_STATUS really seems interesting and certainly will help to identify things. In fact with that I already found: - https://bugzilla.redhat.com/show_bug.cgi?id=1638289 - https://www.spinics.net/lists/kvm/msg157148.html All of them unfortunately ended with assumptions on windows programming bad timers and that being just a consequence of it. I still can't repdroduce this on my side to take a look myself, but seeing that the upstream experts have already looked at it and didn't have more ideas indicates it will be a complex case for them anyway. The bug is against Fedora and not upstream-kvm/qemu, mostly the same people but that is why it was closed EOL. It seems to me we need the main developers back on it to really get a grip on it. - maybe you want to re-kindle this by replying to the old mail thready like "this stil is an issue" or open an upstream bug. But OTOH that might just be an interaction between windows expecting to run on real HW and pausing a VM. https://www.spinics.net/lists/kvm/msg157371.html summarizes that nicely. So I'm unsure how much more will happen bringing it up again. ** Bug watch added: Red Hat Bugzilla #1638289 https://bugzilla.redhat.com/show_bug.cgi?id=1638289 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
