Re: Ubuntu in bhyve

Jason,

Thanks for your reply.

We run NTP on our router (a pfsense) and both the host (TrueNAS) and 
guests are using it, correctly I believe.

On TrueNAS:

# ntpdate -q time.rogue-research.com
server 10.xx.xx.1, stratum 2, offset -0.000149, delay 0.02580
15 Jun 18:19:11 ntpdate[1239]: adjust time server 10.xx.xx.1 offset 
-0.000149 sec

On Ubuntu:

$ timedatectl
                Local time: Thu 2023-06-15 18:17:02 EDT
            Universal time: Thu 2023-06-15 22:17:02 UTC
                  RTC time: Thu 2023-06-15 22:17:02
                 Time zone: America/Toronto (EDT, -0400)
System clock synchronized: yes
               NTP service: active
           RTC in local TZ: no

I believe both indicate that it's working...

Sean



On 15 Jun 2023, at 17:42, jason@tubnor.net wrote:

> Make sure your guests (and host) are syncing to a reliable time 
> source. I
> have heard time to time of some having this issue, but we haven't seen 
> it
> though we do use OpenNTPD across our BSD/*nix guests (windows has its 
> own
> time sync service).
>
>
>
> Cheers,
>
>
>
> Jason.
>
>
>
> From: owner-freebsd-virtualization@freebsd.org
> <owner-freebsd-virtualization@freebsd.org> On Behalf Of Sean McBride
> Sent: Friday, June 16, 2023 5:20 AM
> To: freebsd-virtualization@FreeBSD.org
> Subject: Ubuntu in bhyve
>
>
>
> Hi all,
>
> I am running bhyve (via TrueNAS Core 13) and have some Ubuntu 20.04 
> and
> 22.04 guests.
>
> One of them rather regularly seizes up hard, where I cannot ssh to it, 
> then
> after a few minutes works again. This happens repeatedly and on and 
> off. In
> the Ubuntu logs I see messages like:
>
> clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' 
> as
> unstable because the skew is too large:
> clocksource:                       'hpet' wd_nsec: 536417782 wd_now:
> 638cb3ff wd_last: 63036152 mask: ffffffff
> clocksource:                       'tsc' cs_nsec: 536821277 cs_now:
> 225a9f9e1250b cs_last: 225a9b3891749 mask: ffffffffffffffff
> clocksource:                       'tsc' is current clocksource.
> tsc: Marking TSC unstable due to clocksource watchdog
> TSC found unstable after boot, most likely due to broken BIOS. Use
> 'tsc=unstable'.
> sched_clock: Marking unstable (12899572906362, 
> 9192186981)<-(12908811630850,
> -46250627)
> clocksource: Checking clocksource tsc synchronization from CPU 2 to 
> CPUs
> 0-1,3.
> clocksource: Switched to clocksource hpet
> loop8: detected capacity change from 0 to 114000
>
> Although I don't fully grok these messages, they sound like something 
> that
> could be bhyve's fault. Anyone know if that may indeed be the case?
>
> There is a thread about this on the TrueNAS forum too, but with no 
> answers
> really:
>
>
> <https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.1083
> 76/>
> https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.10837
> 6/
>
> Thanks,
>
> Sean