https://bugzilla.kernel.org/show_bug.cgi?id=191481 --- Comment #5 from Dmitry Svyatogorov <ds@xxxxxxxx> --- # cat /proc/stat | grep cpu cpu 413 0 352 14180440 27163 0 3 1754446170805 0 0 cpu0 212 0 200 7090896 11611 0 2 285245288023 0 0 cpu1 201 0 152 7089543 15551 0 1 1469200882781 0 0 * Guest not rebooted since yesterday, so counters remains broken. "latest kvm tree" on guest side? I've been tested (till now only on ubuntu) all latest kernel branches available for ubuntu 14.04: (4.8.15-040815-generic, 4.4.0-53-generic, 4.2.0-42-generic, 3.19.0-77-generic) to make sure the problem resides in mainline. (As far as I know, ubuntu-team does nothing with kvm, so such check looks sufficient.) At this moment I have simple plan to localize the buggy commit: 1. I already found that in 3.18 bug was committed to 3.18.31. So, checkout to 3.18.31, then revert both kvm commits. 2. In case test succeeds, there remains rather small amount of code for investigation. 3. Except, think again :) -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
