public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 191481] Virtual machine CPU counters are broken forever after live migration to system with "steal time overflow" KVM bug
Date: Wed, 11 Jan 2017 09:00:06 +0000	[thread overview]
Message-ID: <bug-191481-28872-hhB9OB8EdO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-191481-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=191481

--- Comment #5 from Dmitry Svyatogorov <ds@vo-ix.ru> ---
# 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.

  parent reply	other threads:[~2017-01-11  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 16:21 [Bug 191481] New: Virtual machine CPU counters are broken forever after live migration to system with "steal time overflow" KVM bug bugzilla-daemon
2017-01-01  1:23 ` [Bug 191481] " bugzilla-daemon
2017-01-09  9:23 ` bugzilla-daemon
2017-01-10 12:31 ` bugzilla-daemon
2017-01-11  1:21 ` bugzilla-daemon
2017-01-11  9:00 ` bugzilla-daemon [this message]
2017-01-11 11:15 ` bugzilla-daemon
2017-01-11 14:04 ` bugzilla-daemon
2017-01-12 11:53 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-191481-28872-hhB9OB8EdO@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox