All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: weird /proc/stat output with newer (4.1, 4.2) kernels in kvm guest on 3.10 host?
Date: Wed, 2 Mar 2016 11:12:17 -0600	[thread overview]
Message-ID: <56D71EF1.2090404@windriver.com> (raw)


Hi,

I'm running a 3.10-based host with libvirt 1.2.12 and qemu 2.2.

Running a Fedora23 cloud image as a guest, the "cpu" lines in /proc/stat seem to 
be hardly changing:

[fedora@fedora23 boot]$ uptime
  17:01:50 up 44 min,  1 user,  load average: 3.00, 2.99, 2.79
[fedora@fedora23 boot]$ grep cpu /proc/stat
cpu  13 0 124 65880 165 0 0 23088 0 0
cpu0 1 0 4 21967 67 0 0 21866 0 0
cpu1 8 0 52 21877 66 0 0 623 0 0
cpu2 4 0 67 22034 30 0 0 598 0 0


Running an Ubuntu 15.10 cloud image as a guest, everything looks fine:

ubuntu@ubuntu1510:/boot$ uptime
  17:02:28 up 28 min,  1 user,  load average: 3.00, 2.98, 2.42
ubuntu@ubuntu1510:/boot$ grep cpu /proc/stat
cpu  3932 130 443061 46116 257 0 5 12974 0 0
cpu0 1296 130 139886 14960 195 0 1 12343 0 0
cpu1 1330 0 151580 15570 35 0 0 315 0 0
cpu2 1305 0 151595 15586 26 0 4 316 0 0


In both cases the current_clocksource is kvm-clock.  Not sure if it's relevent, 
but Fedora has "CONFIG_NO_HZ_FULL=y" and "CONFIG_NO_HZ_FULL_ALL is not set", and 
does not specify "nohz_full=" in the boot parameters.  Ubuntu has 
"CONFIG_NO_HZ_FULL is not set".


Anyone have any ideas what might be going on?

Chris

             reply	other threads:[~2016-03-02 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 17:12 Chris Friesen [this message]
2016-03-03 18:36 ` weird /proc/stat output with newer (4.1, 4.2) kernels in kvm guest on 3.10 host? Chris Friesen

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=56D71EF1.2090404@windriver.com \
    --to=chris.friesen@windriver.com \
    --cc=linux-kernel@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.