I am however struggling to express this in a way that is easily understandable by others. > However, that does cause problems when the steal time goes negative > (due to hypervisor bugs). So in > https://lore.kernel.org/all/20240522001817.619072-22-dwmw2@xxxxxxxxxxxxx/ > I limited the amount of time which would be accounted to a future tick. That would definitely be an improvement over the old behavior. I noticed the issue because I've been trying to make sense of the numbers while trying to include the time that host was suspended in steal time in https://lore.kernel.org/kvm/20240820043543.837914-1-suleiman@xxxxxxxxxx/ (But I think the issue can happen even without these changes.) Thanks, -- Suleiman