>>> On 08.10.17 at 07:29, wrote:
> Whatever the fix would be applied to guest kernel side, I think the root cause
> is because xen hypervisor returns a RUNSTATE_runnable time less than the
> previous one before live migration.
>
> As I am not clear enough with xen scheduling, I do not understand
devel] high CPU stolen time after live migrate
On Mon, 2017-10-02 at 18:37 +0200, Olivier Bonvalet wrote:
> 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.
>
On Mon, 2017-10-02 at 18:37 +0200, Olivier Bonvalet wrote:
> 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.
>
I think it can be this:
https://0xstubs.org/debugging-a-flaky-cpu-steal-time-co
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
