Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Mar 2014 13:39:48 +0000
From:      Michael Berman <michael.berman@tidalscale.com>
To:        Neel Natu <neelnatu@gmail.com>, Andrea Brancatelli <abrancatelli@schema31.it>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: Clock in bhyve
Message-ID:  <CF4C48C9.1FC6E%michael.berman@tidalscale.com>
In-Reply-To: <CAFgRE9HkY5F_WbS4TSVv%2BDGtp6_GAFfzJguqpY8icDYhDwCkWw@mail.gmail.com>
References:  <766b303ae006c121f8bebe077193e4fa@schema31.it> <CAFgRE9HkY5F_WbS4TSVv%2BDGtp6_GAFfzJguqpY8icDYhDwCkWw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

In my humble experience, the clock inside a VM can jump badly enough that
NTP complains and exits.
You=B9ll need to configure NTP to be very forgiving.   VMware does a lot of
work in its tools/driver to avoid this.

Michael

On 3/15/14, 4:35 PM, "Neel Natu" <neelnatu@gmail.com> wrote:

>Hi Andrea,
>
>On Sat, Mar 15, 2014 at 11:14 AM, Andrea Brancatelli
><abrancatelli@schema31.it> wrote:
>>
>>
>> Hello everybody.
>>
>> I have a stupid question for you :)
>>
>> Is the clock in bhyve virtual or just a hook the host?
>>
>> I mean, should I run ntpd inside the VMs as I would do, let's say, with
>> VMWare, or is it enough to run it on the host?
>
>You should also run it inside the guest.
>
>best
>Neel
>
>> --
>>
>> Andrea Brancatelli
>>
>>
>> _______________________________________________
>> freebsd-virtualization@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>> To unsubscribe, send any mail to
>>"freebsd-virtualization-unsubscribe@freebsd.org"
>_______________________________________________
>freebsd-virtualization@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>To unsubscribe, send any mail to
>"freebsd-virtualization-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF4C48C9.1FC6E%michael.berman>