From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 191481] New: Virtual machine CPU counters are broken forever after live migration to system with "steal time overflow" KVM bug
Date: Thu, 29 Dec 2016 16:21:38 +0000 [thread overview]
Message-ID: <bug-191481-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=191481
Bug ID: 191481
Summary: Virtual machine CPU counters are broken forever after
live migration to system with "steal time overflow"
KVM bug
Product: Virtualization
Version: unspecified
Kernel Version: Found since 3.18.31, still resides in latest ubuntu
3.19..4.8 builds
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: ds@vo-ix.ru
Regression: No
All (at least, compiled for ubuntu) kernels had the stolen time overflow bug,
described in links below:
http://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01295.html
https://bugs.launchpad.net/linux/+bug/1494350
It was fixed (in ubuntu) on summer 2016, so till now still exists affected
hosts.
Kernels built before Apr 2016 bypass "%still" counter as is, so sar output
likes this:
11:11:15 AM CPU %user %nice %system %iowait %steal %idle
11:10:48 AM all 0.00 0.00 0.50 0.00 0.00 99.50
11:10:49 AM all 0.00 0.00 0.00 0.00
18823208238479134720.00 203.06
11:10:50 AM all 0.00 0.00 0.00 0.00 0.00 100.00
While all newer kernel counters I've been tested sticks:
11:11:15 AM CPU %user %nice %system %iowait %steal %idle
07:07:56 AM all 0.50 0.00 0.00 0.00 0.00 99.50
07:07:57 AM all 0.00 0.00 0.50 0.00 0.00 99.50
07:07:58 AM all 0.00 0.00 0.50 0.00 0.00 99.50
07:07:59 AM all 0.00 0.00 0.00 0.00 100.00 0.00
07:08:00 AM all 0.00 0.00 0.00 0.00 100.00 0.00
07:08:01 AM all 0.00 0.00 0.00 0.00 100.00 0.00
%steal is always 100% after migration.
I slightly suspect that the reason resides in commit
0185604c2d82c560dab2f2933a18f797e74ab5a8.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-12-29 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 16:21 bugzilla-daemon [this message]
2017-01-01 1:23 ` [Bug 191481] Virtual machine CPU counters are broken forever after live migration to system with "steal time overflow" KVM bug 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.