On Saturday, 20.06.2015 at 11:57, Thomas Leonard wrote: > On 15 June 2015 at 11:56, Martin Lucina <[email protected]> wrote: > > On Friday, 12.06.2015 at 16:40, Thomas Leonard wrote: > >> I also tested mirage-skeleton/console, which worked but ran rather > >> fast (it's supposed to wait 1s between each print). Calling > >> gettimeofday showed the clock running fast for some reason. > > > > I've logged issues rumprun/#30 (clock runs fast) and rumprun/#31 (no > > rtc/wall time on hw/kvm), so that we don't forget and users see it's a > > known problem. > > Thanks!
Wow, timekeeping is *complicated*. See the full discussion at http://www.freelists.org/post/rumpkernel-users/Implement-timekeeping-for-rumprunhw-x86 Any testing will be much appreciated. You will need to pull the latest rumprun and opam-rumprun master and rebuild the ocaml-rumprun toolchain from scratch due to other changes in the rumprun toolchain. I will continue to improve the timekeeping code, especially with with better support for KVM (pvclock). Martin
