make no-kvm failing with "FATAL ERROR:system clock is inaccessible" about nanos HOT 6 CLOSED

i'm afraid this was intensional. without kvm we have no translation between rdtsc and
actual seconds. andrii did the first part of #24 which was to try to determine if
kvm was providing the right scaling factor for us.

the second part was to use a different time source so that we could function without hpet, which he's looking at

oddly, running without kvm seems to work. any tcp timers must be totally out of whack. i guess if there are no losses...

from nanos.

Oh, I see. But for me it's not working without kvm.

Maybe this should stay in a topic branch until it works enough to not break for the common case? Not that I can't start using kvm, but running without it shouldn't be broken in master.

from nanos.

@wjhun
I can suggest mark as comment this line for your test.
/uniboot/x86_64/clock.c:59

from nanos.

sorry, I was totally unclear. kvm provides the clock scaling factors, so running with lvm is safe.

andrii committed a change in response to #24 which halts if the scaling factor isn't set.

without the scaling factor the clock/timers make no sense, so this seemed reasonable.

could just set the halt back to a console

in order to get a decent clock in non-kvm, we need to write a driver.

from nanos.

I think this issue we can close?

from nanos.

Yes, thank you.

from nanos.