From: Olivier Bonvalet <xen.list@daevel.fr>
To: xen-users@lists.xensource.com
Cc: xen-devel@lists.xen.org
Subject: high CPU stolen time after live migrate
Date: Mon, 02 Oct 2017 18:37:57 +0200 [thread overview]
Message-ID: <1506962277.6552.25.camel@daevel.fr> (raw)
Hi,
with Xen 4.8.2, migrated domains have wrong stats for stolen time.
For example :
root! laussor:/proc# cat stat
cpu 87957976 32463 6483874 361169794 3075806 0 937004 183086986113 0 0
cpu0 2828867 2434 226580 43754152 786651 0 42766 1778722573131 0 0
cpu1 2611496 3545 232529 42364047 594846 0 2441 1598822754769 0 0
cpu2 21958330 14923 1338283 40315990 424045 0 127421 1086605305497 0 0
cpu3 2725745 339 271471 42426113 319132 0 1408 41756798508 0 0
cpu4 21738600 3858 1099222 39528759 508996 0 682044 321900840424 0 0
cpu5 9543155 1668 1165194 53274011 231727 0 8130 1652751948052 0 0
cpu6 14223984 4014 970888 48826880 126790 0 67909 254194505219 0 0
cpu7 12327794 1680 1179702 50679764 83618 0 4883 827029885923 0 0
intr 7866132625 99868037 0 434116966 617 0 363800 0 94983174 425603035 1016 0 390335 0 0 122245733 369053953 1041 0 358301 0 0 77267482 422334777 1015 0 371084 0 0 96031342 218747945 993 0 331440 0 0 77622794 333046334 1139 0 444912 0 0 57536561 237035283 1126 0 407725 0 0 41162673 306795645 1196 0 431960 0 0 775 0 0 0 0 479 0 0 0 952 0 0 0 17046 30405 15526 94781 14025 3849 16848 4485 16352 1801 17611 2104 14016 1807 16868 2235 3680 0 0 0 0 0 0 0 110370 107659 101208 355716 107895 62726 105345 70387 112823 62653 103888 70642 109312 63799 103388 65918 0 0 0 5619 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 6178259009
btime 1506309567
processes 6457002
procs_running 2
procs_blocked 0
softirq 2893820956 8 574619811 808518311 848843354 0 0 12041195 205459383 0 444338894
root! laussor:/proc# cat /proc/uptime
652005.23 2631328.82
Values for "stolen time" in /proc/stat seems impossible with only 7 days of uptime.
Is it a known bug ?
thanks,
Olivier
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-10-02 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 16:37 Olivier Bonvalet [this message]
2017-10-03 9:22 ` high CPU stolen time after live migrate Dario Faggioli
2017-10-03 22:46 ` Re : " Olivier Bonvalet
-- strict thread matches above, loose matches on Subject: below --
2017-10-08 5:29 Dongli Zhang
2017-10-09 8:26 ` Jan Beulich
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=1506962277.6552.25.camel@daevel.fr \
--to=xen.list@daevel.fr \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xensource.com \
/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.