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: Thu, 12 Jan 2017 11:53:14 +0000 [thread overview]
Message-ID: <bug-191481-28872-tPF1JdmFZJ@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 #8 from Dmitry Svyatogorov <ds@vo-ix.ru> ---
LOL! bugzilla.kernel.org becomes invalid place to fix commits merged into
master-branch.
JFYI, the problem was yesterday localized in
f9c904b7613b8b4c85b10cd6b33ad41b2843fa9d. The kernel 3.18.46 with this commit
reverted is running on tests for ≈20 hours, no additional problems found till
now.
For those who found this thread because of stucking with the same problem, you
can safely rebuild the problematic kernel with "git revert
f9c904b7613b8b4c85b10cd6b33ad41b2843fa9d" or make/apply reverting patch,
depending on your distro/build system. Less accuracy in stolen time calculation
will scarcely be a bereavement.
Good luck!
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2017-01-12 11:53 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
2017-01-11 11:15 ` bugzilla-daemon
2017-01-11 14:04 ` bugzilla-daemon
2017-01-12 11:53 ` bugzilla-daemon [this message]
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-tPF1JdmFZJ@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