I am running the latest version of Parallels on an M2 Max Mac Studio. I have two VMs running Ubuntu 22.04. The clock is being set 100+ years ahead on both of them. This happens when I just leave the VMs running, not paused or suspended. I set up a script to check the date every 5 seconds and it shows this:
Sun Dec 3 08:35:28 PM CST 2023
Sun Dec 3 08:35:33 PM CST 2023
... all fine until ....
Fri Dec 8 01:53:21 PM CST 2023
Fri Dec 8 01:53:26 PM CST 2023
Fri Dec 8 05:24:50 PM CST 2023
Sun Jan 29 12:52:18 PM CST 2119
Sun Jan 29 12:52:23 PM CST 2119
So it skipped ahead 4 hours and then 96 years. There was nothing going on with the VM, it was just running with no activity.
The hardware clock seems fine:
sudo hwclock -r
2023-12-09 10:29:41.569973-06:00
~ $ date
Sat Jan 28 10:23:07 AM CST 2119
I've tried with and without time sync from VM turned on, but I get the same behavior. I've tried ntp/chrony/timesyncd but once the time is off by that much, they can't get back in sync. The only way to get things back is to reboot. I even tried renaming prltimesync to prltimesync.stop to make sure that program wasn't causing it.
Trying to set the date manually looks like this:
sudo date --debug --set='2023-12-09 10:21:10'
date: parsed date part: (Y-M-D) 2023-12-09
date: parsed time part: 10:21:10
date: input timezone: system default
date: using specified time as starting value: '10:21:10'
date: starting date/time: '(Y-M-D) 2023-12-09 10:21:10'
date: '(Y-M-D) 2023-12-09 10:21:10' = 1702138870 epoch-seconds
date: timezone: system default
date: final: 1702138870.000000000 (epoch-seconds)
date: final: (Y-M-D) 2023-12-09 16:21:10 (UTC)
date: final: (Y-M-D) 2023-12-09 10:21:10 (UTC-06)
date: cannot set date: Invalid argument
Since that's obviously a valid date, my guess is it won't let you adjust the date that much in one command. Setting it back one day works:
date
Sun Jan 29 10:21:29 AM CST 2119
~ $ sudo date --set='2119-01-28 10:21:10'
Sat Jan 28 10:21:10 AM CST 2119
~ $ date
Sat Jan 28 10:21:11 AM CST 2119
I've been running on Parallels Intel for years with Ubuntu and never seen this so I have to think it's an ARM issue with Parallels.
Any ideas? At this point I'd be happy if I could just run a command to manually change the clock to the right time.
Thanks
Brian
Sun Dec 3 08:35:28 PM CST 2023
Sun Dec 3 08:35:33 PM CST 2023
... all fine until ....
Fri Dec 8 01:53:21 PM CST 2023
Fri Dec 8 01:53:26 PM CST 2023
Fri Dec 8 05:24:50 PM CST 2023
Sun Jan 29 12:52:18 PM CST 2119
Sun Jan 29 12:52:23 PM CST 2119
So it skipped ahead 4 hours and then 96 years. There was nothing going on with the VM, it was just running with no activity.
The hardware clock seems fine:
sudo hwclock -r
2023-12-09 10:29:41.569973-06:00
~ $ date
Sat Jan 28 10:23:07 AM CST 2119
I've tried with and without time sync from VM turned on, but I get the same behavior. I've tried ntp/chrony/timesyncd but once the time is off by that much, they can't get back in sync. The only way to get things back is to reboot. I even tried renaming prltimesync to prltimesync.stop to make sure that program wasn't causing it.
Trying to set the date manually looks like this:
sudo date --debug --set='2023-12-09 10:21:10'
date: parsed date part: (Y-M-D) 2023-12-09
date: parsed time part: 10:21:10
date: input timezone: system default
date: using specified time as starting value: '10:21:10'
date: starting date/time: '(Y-M-D) 2023-12-09 10:21:10'
date: '(Y-M-D) 2023-12-09 10:21:10' = 1702138870 epoch-seconds
date: timezone: system default
date: final: 1702138870.000000000 (epoch-seconds)
date: final: (Y-M-D) 2023-12-09 16:21:10 (UTC)
date: final: (Y-M-D) 2023-12-09 10:21:10 (UTC-06)
date: cannot set date: Invalid argument
Since that's obviously a valid date, my guess is it won't let you adjust the date that much in one command. Setting it back one day works:
date
Sun Jan 29 10:21:29 AM CST 2119
~ $ sudo date --set='2119-01-28 10:21:10'
Sat Jan 28 10:21:10 AM CST 2119
~ $ date
Sat Jan 28 10:21:11 AM CST 2119
I've been running on Parallels Intel for years with Ubuntu and never seen this so I have to think it's an ARM issue with Parallels.
Any ideas? At this point I'd be happy if I could just run a command to manually change the clock to the right time.
Thanks
Brian