This is the second time I've encountered this issue in roughly a week.. this time it happend while I was actively using the VM (evidently, not a sleep/suspend issue).. The system clock on my guest host spontaneously jumped forward from February 18 2024 (current time) to a remarkable April 11 2119 The last time this occured it was resolved with a reboot of the guest OS, though I had to resolve a bunch of timestamps that caused dependency issues in my build system (because obviously a file dated 95 years in the future is newer than the binary I'm trying to build in 2024) I can't say this is specifically a Parallels issue, though I don't encounter such problems on physical hardware timedatectl shows the following $ timedatectl Local time: Tue 2119-04-11 02:10:36 AEST Universal time: Mon 2119-04-10 16:10:36 UTC RTC time: Sat 2024-02-17 14:21:40 Time zone: Australia/Sydney (AEST, +1000) System clock synchronized: no NTP service: active RTC in local TZ: no The guest VM is configured to sync with my mac, and the time shows on the host OS as normal. I've tried restarting chrony, but ultimately the only fix I can see is to reboot the guest OS After doing so, timedatectl shows correctly $ timedatectl Local time: Sun 2024-02-18 01:29:03 AEDT Universal time: Sat 2024-02-17 14:29:03 UTC RTC time: Sat 2024-02-17 14:29:04 Time zone: Australia/Sydney (AEDT, +1100) System clock synchronized: yes NTP service: active RTC in local TZ: no chronyd journal logs at the time indicate the following: Feb 17 11:40:30 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 11:58:30 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 12:00:40 fedora-39-arm64-kde chronyd[947]: Selected source 27.124.125.252 (2.fedora.pool.ntp.org) Feb 17 12:00:41 fedora-39-arm64-kde chronyd[947]: Selected source 159.196.3.239 (2.fedora.pool.ntp.org) Feb 17 12:03:56 fedora-39-arm64-kde chronyd[947]: Selected source 162.159.200.123 (2.fedora.pool.ntp.org) Feb 17 14:25:34 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 14:25:34 fedora-39-arm64-kde chronyd[947]: Can't synchronise: no selectable sources Feb 17 14:28:16 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 14:30:25 fedora-39-arm64-kde chronyd[947]: Selected source 159.196.3.239 (2.fedora.pool.ntp.org) Feb 17 14:33:41 fedora-39-arm64-kde chronyd[947]: Selected source 162.159.200.123 (2.fedora.pool.ntp.org) Feb 17 19:36:47 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 19:36:47 fedora-39-arm64-kde chronyd[947]: Can't synchronise: no selectable sources Feb 17 19:39:13 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 19:41:22 fedora-39-arm64-kde chronyd[947]: Selected source 27.124.125.252 (2.fedora.pool.ntp.org) Feb 17 19:41:23 fedora-39-arm64-kde chronyd[947]: Selected source 159.196.3.239 (2.fedora.pool.ntp.org) Feb 17 19:42:28 fedora-39-arm64-kde chronyd[947]: Selected source 162.159.200.123 (2.fedora.pool.ntp.org) Feb 17 23:01:36 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 23:01:36 fedora-39-arm64-kde chronyd[947]: Can't synchronise: no selectable sources Feb 17 23:33:42 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Feb 17 23:35:51 fedora-39-arm64-kde chronyd[947]: Selected source 95.111.218.150 (2.fedora.pool.ntp.org) Feb 17 23:35:52 fedora-39-arm64-kde chronyd[947]: Selected source 159.196.3.239 (2.fedora.pool.ntp.org) Feb 17 23:40:11 fedora-39-arm64-kde chronyd[947]: Selected source 162.159.200.123 (2.fedora.pool.ntp.org) Apr 11 01:45:36 fedora-39-arm64-kde chronyd[947]: Forward time jump detected! Apr 11 01:45:36 fedora-39-arm64-kde chronyd[947]: Adjustment of 732.7 seconds is invalid Apr 11 01:45:36 fedora-39-arm64-kde chronyd[947]: Can't synchronise: no selectable sources Apr 11 01:45:36 fedora-39-arm64-kde chronyd[947]: Source 27.124.125.252 replaced with 139.180.160.82 (2.fedora.pool.ntp.org) Apr 11 01:47:44 fedora-39-arm64-kde chronyd[947]: Selected source 162.159.200.123 (2.fedora.pool.ntp.org) Apr 11 01:47:44 fedora-39-arm64-kde chronyd[947]: System clock wrong by -3002405930.904271 seconds I also see this, as the first messages when the clock change occurs.. which may indicate this is actually a virtualisation issue unless it's just a downstream effect of such a drastic clock shift. Apr 09 10:39:58 fedora-39-arm64-kde rtkit-daemon[834]: The canary thread is apparently starving. Taking action. Apr 11 01:45:36 fedora-39-arm64-kde kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: Apr 11 01:45:36 fedora-39-arm64-kde kernel: watchdog: Watchdog detected hard LOCKUP on cpu 5 Apr 11 01:45:36 fedora-39-arm64-kde kernel: rcu: 5-...!: (6 ticks this GP) idle=fa34/1/0x4000000000000002 softirq=4315308/4315310 fqs=1 Apr 11 01:45:36 fedora-39-arm64-kde kernel: rcu: (detected by 1, t=3002265904964 jiffies, g=10908273, q=1453 ncpus=6) Apr 11 01:45:36 fedora-39-arm64-kde kernel: Sending NMI from CPU 1 to CPUs 5: Apr 11 01:45:36 fedora-39-arm64-kde kernel: Modules linked in: isofs uinput snd_seq_dummy snd_hrtimer Apr 11 01:45:36 fedora-39-arm64-kde kernel: NMI backtrace for cpu 5 Apr 11 01:45:36 fedora-39-arm64-kde kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE 6.7.3-200.fc39.aarch64 #1 Apr 11 01:45:36 fedora-39-arm64-kde kernel: Hardware name: Parallels International GmbH. Parallels ARM Virtual Machine/Parallels ARM Virtual Platform, BIOS 19.2.1 (54832) Wed, 20 Dec 202 Apr 11 01:45:36 fedora-39-arm64-kde kernel: pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) Apr 11 01:45:36 fedora-39-arm64-kde kernel: rfkill nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink qrtr prl_fs_freeze(POE) prl_fs(POE) sunrpc binfmt_misc vfat fat snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer virtio_balloon snd prl_tg(POE) soundcore acpi_tad joydev pktcdvd loop zram crct10dif_ce polyval_ce polyval_generic virtio_net virtio_gpu ghash_ce Apr 11 01:45:36 fedora-39-arm64-kde kernel: pc : cpuidle_idle_call+0xb0/0x1b0 Apr 11 01:45:36 fedora-39-arm64-kde kernel: lr : cpuidle_idle_call+0x160/0x1b0 Apr 11 01:45:36 fedora-39-arm64-kde kernel: sp : ffff800083b9be00 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x29: ffff800083b9be10 x28: 0000000000000000 x27: 0000000000000000 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x23: 0000000000000000 x22: ffff0000c03ac400 x21: ffff0000c03ac400 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000000000 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8da0ddf8 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x14: 0000000000000000 x13: 0000000000000000 x12: ffff800082d1f850 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x11: 0000000000000001 x10: 021b9daf72002b16 x9 : ffff80008029d5f8 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x8 : ffff0000c03ae5c8 x7 : 0000000000000004 x6 : 000004d6ea1fcfed Apr 11 01:45:36 fedora-39-arm64-kde kernel: x5 : 4000000000000000 x4 : ffff80037b47a000 x3 : ffff80037b47a000 Apr 11 01:45:36 fedora-39-arm64-kde kernel: x2 : 0000000000000005 x1 : ffff800083b9bde0 x0 : ffff8000824fa008 Apr 11 01:45:36 fedora-39-arm64-kde kernel: Call trace: Apr 11 01:45:36 fedora-39-arm64-kde kernel: cpuidle_idle_call+0xb0/0x1b0 Apr 11 01:45:36 fedora-39-arm64-kde kernel: do_idle+0xa8/0xf8 Apr 11 01:45:36 fedora-39-arm64-kde kernel: cpu_startup_entry+0x40/0x50 Apr 11 01:45:36 fedora-39-arm64-kde kernel: secondary_start_kernel+0xe0/0x108 Apr 11 01:45:36 fedora-39-arm64-kde kernel: __secondary_switched+0xb8/0xc0 Apr 11 01:45:36 fedora-39-arm64-kde kernel: net_failover sha3_ce sha512_ce sha512_arm64 failover virtio_dma_buf ahci_platform libahci_platform virtio_mmio ip6_tables ip_tables fuse i2c_dev Apr 11 01:45:36 fedora-39-arm64-kde kernel: Sending NMI from CPU 4 to CPUs 5: Apr 11 01:45:36 fedora-39-arm64-kde kernel: NMI backtrace for cpu 5 Apr 11 01:45:36 fedora-39-arm64-kde kernel: CPU: 5 PID: 641427 Comm: kworker/5:2 Tainted: P OE 6.7.3-200.fc39.aarch64 #1 Apr 11 01:45:36 fedora-39-arm64-kde kernel: Hardware name: Parallels International GmbH. Parallels ARM Virtual Machine/Parallels ARM Virtual Platform, BIOS 19.2.1 (54832) Wed, 20 Dec 202 Apr 11 01:45:36 fedora-39-arm64-kde kernel: Workqueue: 0x0 (events) Apr 11 01:45:36 fedora-39-arm64-kde kernel: pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) Apr 11 01:45:36 fedora-39-arm64-kde kernel: pc : __schedule+0x288/0x760 Apr 11 01:45:36 fedora-39-arm64-kde kernel: lr : __schedule+0x288/0x760
Hello, same problem for me on Debian 12, and as mentioned in this issue https://forum.parallels.com/threads...-mac-running-ubuntu-22-vm.362410/#post-933443 also on Ubuntu 22, so it is definitely a problem on the hypervisor. I've opened a ticket and the support ask me to do some tests and send the technical report but the problem is still present. You mentioned that your VMs are synced with the Macos time and the problem came up, mine not, are completely isolated from the host and the drift occurs like yours to the year 2119, so unfortunately that is not a solution to the problem. I'm going to contact the support to deliver the results of my tests
I have been struggling with the same issue. After 8-20 hours, the kernel crashes and my date goes to 2119, breaking everything. I've tried multiple os and kernels. This started before parallels 20 and it still an issue now.
Can you surf the web when in time travel mode? Perhaps you can find what stocks to invest in or teams to bet on.
Some more details - this is macOS 14.7.1, Parallels 20.1.1 and guest VM is Ubuntu 22.04 LTS. I do *not* have Parallels Tools installed in the guest OS but the "Time" setting is set to "Sync from Mac"
And one other note. I'm not sure if it is related, but I did recently enable Snapshot Smart Guard and Optimize for Time Machine. I had never seen this problem before then.
