Time/clock running behind on Virtualized Ventura

[patatman]

BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.

Describe the issue
I've noticed that if I boot the VM in the morning, and work in it (also locking my macbook occasionally), the Time starts to drift. My host machine would have time: 13:58 and my virtual Ventura would run 30 or more minutes behind (displaying 13:12).

Is it possible the virtualised clock is running slower? Wouldn't it be better to pass to host clock trough the VM to prevent this?

Configuration

• UTM Version: 4.1.6
• macOS Version: Ventura
• Mac Chip M1 pro

Crash log
None

[antonkratz]

I observe the same issue, has been ongoing for about a year for me, with this config. Guest system is Ubuntu 23.04 (lunar).

• UTM Version: Version 4.4.4 (92)
• macOS Version: 14.2.1 (23C71)
• Mac Chip: M2

[hari-arumugam]

For now, i manage to sync with hwclock --hctosys as frequently as needed, in addition to the QEMU flag -rtc base=utc,clock=host