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: Tue, 10 Jan 2017 12:31:52 +0000 [thread overview]
Message-ID: <bug-191481-28872-qcwWFwQE0u@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 #3 from Dmitry Svyatogorov <ds@vo-ix.ru> ---
I've compiled/installed kernel 3.18.46 with 2348140d58f4 for ubuntu VM, but no
luck. Still falls into st=100%.
# dmesg -T
…
[Tue Jan 10 08:13:09 2017] Linux version 3.18.46-031846-generic (root@repo1)
(gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ) #201612271322 SMP Tue Jan 10
07:24:30 AST 2017
[Tue Jan 10 08:13:09 2017] Command line:
BOOT_IMAGE=/boot/vmlinuz-3.18.46-031846-generic
root=UUID=9a370490-4f38-4714-a3b1-c51f5562a5b1 ro transparent_hugepage=never
vga=792 console=ttyS0 console=tty0
…
# sar 1 600
08:21:55 AM CPU %user %nice %system %iowait %steal %idle
…
08:22:25 AM all 0.00 0.00 0.50 0.00 0.00 99.50
08:22:26 AM all 0.00 0.00 0.00 0.00 100.00 0.00
08:22:27 AM all 0.00 0.00 0.00 0.00 100.00 0.00
08:22:28 AM all 0.00 0.00 0.00 0.00 100.00 0.00
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-10 12:31 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 [this message]
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-qcwWFwQE0u@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