From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.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
Message-ID: <bug-191481-28872-hhB9OB8EdO@https.bugzilla.kernel.org/>
References: <bug-191481-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.29.136]:49568 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755341AbdAKJAL (ORCPT <rfc822;kvm@vger.kernel.org>);
        Wed, 11 Jan 2017 04:00:11 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
        by mail.kernel.org (Postfix) with ESMTP id A4AB620204
        for <kvm@vger.kernel.org>; Wed, 11 Jan 2017 09:00:09 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
        by mail.kernel.org (Postfix) with ESMTP id 582D420212
        for <kvm@vger.kernel.org>; Wed, 11 Jan 2017 09:00:06 +0000 (UTC)
In-Reply-To: <bug-191481-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.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.