SOLVED TrueNAS Bhyve VM's do not pass time calls down to the underlying host OS like ESXi does?

[eldxmgw]

This is correct?
"I have given up trying to run anything time critical in the FreeNAS Bhyve VM's, as they do not pass time calls down to the underlying host OS like ESXi does".

This is exactly my problem fristly seen when i was setup a Windows Server 2019 PDC VM and trying to configure the NTP.
The sync wasn't possible at any time running this VM in TureNAS.
Then i was trying the same with a Win10 Client OS. Syncing the clock with a MS or whatsoever NTP wasn't possible.
I've never seen something like that in a VMware environment. The Server VM runs good in the Bhyve Hypervisor, except that it won't pass time calls.
In the mean time i tried TrueNAS Scale, and i reinstalled the whole TrueNAS Core - but still the same.
Searching the net showed me that i'm somewhat not alone with this problem. But i haven't found a solution so far which is strongly needed.
Can somebody confirm, or somebody knows if there's a way how to fix that issue? Cause without i cannot see running a server n this Hypervisor.

I've almost given up since i already have wasted so much time on this. What i'm doing wrong?

 

[Patrick M. Hausen]

What is the source of that statement?

I honestly have no clue what that is supposed to mean - what does the hypervisor host have to do with running NTP in the client? All I can say is that I run Linux and Windows on my TrueNAS and I do use NTP.

Linux:

Code:

ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*192.168.1.4     192.168.1.1      3 u   35   64  377    0.943  -105.74   6.330
 0.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
+ntp1.rrze.uni-e .DCFp.           1 u   13   64  377   30.852  -98.708   9.498
+time.cloudflare 10.48.8.4        3 u    1   64  377   33.352  -109.07   4.365
+time2.hs-augsbu 131.188.3.221    2 u   40   64  377   37.142  -113.20   9.419
+mail.klausen.dk 193.79.237.14    2 u   30   64  377   33.008  -106.96   4.868
+ntp14.kashra-se 192.168.100.15   2 u   39   64  377   35.435  -115.43   8.663

Windows:

Code:

C:\WINDOWS\system32>w32tm /query /status
Sprungindikator: 0(keine Warnung)
Stratum: 3 (Sekundärreferenz - synchr. über (S)NTP)
Präzision: -23 (119.209ns pro Tick)
Stammverzögerung: 0.0334789s
Stammabweichung: 7.8814246s
Referenz-ID: 0xC0A80101 (Quell-IP:  192.168.1.1)
Letzte erfolgr. Synchronisierungszeit: 06.05.2021 03:53:30
Quelle: 192.168.1.1,0x9
Abrufintervall: 10 (1024s)

 

[eldxmgw]

I found the sentence in this thread, message #3: https://www.truenas.com/community/threads/the-entire-time-system.74656/

Even a stinky Windows 10 cannot sync the time with time.windows.com. This is my problem. I also checked that the TrueNAS or TrueNAS Scale shows the correct time in GUI, but date in the shell shows ~ 2hrs in future. Then i just took a look at the BIOS time which was correct. Then i was figuring out that using the setting "local time" in TrueNAS * hypervisor sets the wrong time like date in shell would show it. Setting "UTC" in the hypervisor will set the time correctly. But at the very end it doesn't matters if choosing local time or UTC, both options will give you errors syncing the time while not pass time calls to the underlying host OS.

 

[Morris]

In Windows 10 settings for time & Date
- Set Time Automatically - On
- Set Time Zone Automatically - Off
- Select your time zone
- Adjust Daylight Savings Time Automatically - Your choice

Now click the "sync now" button

Your time has been automagicly been set!

 

[eldxmgw]

In Windows 10 settings for time & Date
- Set Time Automatically - On
- Set Time Zone Automatically - Off
- Select your time zone
- Adjust Daylight Savings Time Automatically - Your choice

Now click the "sync now" button

Your time has been automagicly been set!

No chance at all.
Fresh installed Win10, with latest updates, working except for time syncing, see the attached picture.
Same for Windows 2019 Server. I never managed to get it working so far.

 

[Morris]

No chance at all.
Fresh installed Win10, with latest updates, working except for time syncing, see the attached picture.
Same for Windows 2019 Server. I never managed to get it working so far.

Try setting your time manually, then switch to synchronization. I'm not able to translate the error yet I assume it's about too much of a difference. If manual time set followed by automatic fails, check your error log for hints.

Good luck,

Morris

 

[eldxmgw]

I found a solution and maybe it was my fault. But overall i'm so happy to finally fixed this issue, even when it took some weeks.
I tested with Win 2019 Server and Win 10 successfully.
The switch used in conjunction with the TrueNAS system is a 52 port HPE Office Connect 1920S.
"Auto DoS Features" were enabled.
I tested all options individually and come to the conclusion, that this option forced that issue, which i've disabled afterwards: