On Sat, Oct 20, 2018 at 4:27 AM Rick Payne wrote:
>
> OSv sets the MSR once, and then uses the result repeatedly - in fact it
> barrier()s it which is odd as we know it shouldn't change unless we
> write the MSR - which makes me think there was some misunderstanding
> here (which could easily be
On Mon, Sep 17, 2018 at 4:20 AM, Rick Payne wrote:
> On Mon, 2018-09-17 at 01:41 +0300, Nadav Har'El wrote:
> > I have a wild guess, but I'm not a big clock expert, and I'm CCing
> > Glauber who might have better ideas.
> >
> > My guess is that you have ntp running in the *host*, but not in the
On Mon, 2018-09-17 at 01:41 +0300, Nadav Har'El wrote:
> I have a wild guess, but I'm not a big clock expert, and I'm CCing
> Glauber who might have better ideas.
>
> My guess is that you have ntp running in the *host*, but not in the
> guest (we don't have an ntp client for OSv), and somehow
On Mon, Sep 17, 2018 at 1:21 AM, Rick Payne wrote:
> On Fri, 2018-09-14 at 12:12 -0700, Waldek Kozaczuk wrote:
> > Stupid question: are you sure the KVM accellarion is actually enabled
> > and kvm-clock actually used? If not OSv would fall back to hpet which
> > we know we have some problems
On Thu, Sep 13, 2018 at 10:19 PM, Rick Payne wrote:
>
> We have a problem with OSv's wall clock drifting away from the
> hypervisor's. For example, this VM has been running for under 24hrs,
> and when I compare the hypervisor time, with that retrieved from the
> httpserver-api, I get this:
>
> $
On Fri, 2018-09-14 at 12:12 -0700, Waldek Kozaczuk wrote:
> Stupid question: are you sure the KVM accellarion is actually enabled
> and kvm-clock actually used? If not OSv would fall back to hpet which
> we know we have some problems with.
The processor flags are: "sse3 cmpxchg16b x2apic clflush
On Fri, 2018-09-14 at 16:25 -0700, Dor Laor wrote:
> Need to look at the guest log and the restapi
The log says:
/usr/bin/qemu-system-x86_64 -name xxx -S -machine pc-i440fx-
xenial,accel=kvm,usb=off -m 8192 -realtime mlock=off -smp
4,sockets=4,cores=1,threads=1 ...
Rick
--
You received this
Need to look at the guest log and the restapi
On Fri, Sep 14, 2018, 15:53 Rick Payne wrote:
> On Fri, 2018-09-14 at 12:12 -0700, Waldek Kozaczuk wrote:
> > Stupid question: are you sure the KVM accellarion is actually enabled
> > and kvm-clock actually used? If not OSv would fall back to hpet
On Fri, 2018-09-14 at 12:12 -0700, Waldek Kozaczuk wrote:
> Stupid question: are you sure the KVM accellarion is actually enabled
> and kvm-clock actually used? If not OSv would fall back to hpet which
> we know we have some problems with.
My turn for a stupid question - how would I know?
I do
Stupid question: are you sure the KVM accellarion is actually enabled and
kvm-clock actually used? If not OSv would fall back to hpet which we know
we have some problems with.
Waldek
On Thursday, September 13, 2018 at 3:19:30 PM UTC-4, rickp wrote:
>
>
> We have a problem with OSv's wall clock
We have a problem with OSv's wall clock drifting away from the
hypervisor's. For example, this VM has been running for under 24hrs,
and when I compare the hypervisor time, with that retrieved from the
httpserver-api, I get this:
$ curl http://192.168.x.x/os/date && TZ=UTC date
"Thu Sep 13
11 matches
Mail list logo