Time sync issues on silicon mac running Ubuntu 22 VM

I've been having this problem with Ubuntu 24.04 as well. Fortunately for me, it does not impact my workflow drastically because I can rollback to an earlier snapshot without losing much. The first time it happened, I noticed in the kernel log that there was an array index out of bounds exception in what appeared to be some bit of parallels code, judging by the function name. Regrettabely, I did not know about this forum at the time, else I would have posted the details. I figured the issue had to do with some parallels tools time sync, so I disabled time-sync, and installed ntpd instead. Today, the issue happened again, immediately after an auto-snapshot was taken. I rolled back to the earlier snapshot and the problem was gone again. If/when it happens again, I'll be sure to post the kernel stack trace.

 

I just realized that when I upgraded to the latest Parallels and MacOS version, I also disabled Smart-Guard based on some of the comments in this thread. My uptime is 7 days now without the issue. It seems that there could be several causes.

 

So it could be the pause and resume when creating a snapshot?

 

Sure seems so. I suspect there are several causes, that being one of them.

 

I have the exact same issue. It started when I upgraded to the latest macOS major update 15.0.1

Before that it never happened.

It happens very reliably when a snapshot is taken.

If I manually, or an auto-snapshot, takes place - the VM will suddenly corrupt and set the year into the future.

It will need restarting the VM to fix the time, but the VM will be permanently damaged (for example the MOTD message is cached and now its cached for 95 years in the future so never updates and now MOTD messages are broken). Some can be fixed, but its a massive hassle. So this is a very serious issue.

If the VM is shutdown, a snapshot can be taken. If a snapshot is taken while the VM is running the clock runs wild.

I have had to disable auto-snapshots, which I am not happy about.

Please Parallels will you instruct us if you can reproduce and if a fix is being worked on?

I have tried using the Mac/Linux VM sync time setting both on and off.

Arm64 ubuntu 24.04 AND 22.04 both tested with issue. Parallels 19 and 20 BOTH tested and have the issue. Must be MacOS 15.0.1. Prior macOS was fine.

To reproduce just use macos 15.0.1 and take a live snapshot of a running VM and look at the clock.

TO users effected by this, you may need to develop some find commands to look for files created >2024 and track them all down. Delete caches, rebuild or reinstall anything else. I hope your VM is not permanently broken. If you do have a snapshot, try and restore it but do not let it power up, as the break happens after it comes back from pause, and it actually should be fine in the snapshot if you can power it down after restore fast enough to avoid any damage.

 

Create a support ticket, and they'll escalate it to development team after some troubleshooting. Everyone affected by this should do it.

 

Hi, the support told me that the issue has escalated to level two, hope they found a solution soon

 

There is a new Parallels update out now, 20.1.1, and also macOS 15.1. It's still a total mess. My time switched two times during the upgrade to 20.1.1 and presumably during the Parallels tool upgrade. Entirely unrelated, the only silver lining is that I think after three years or more, the arm64 version of Windows 11 no longer constantly stutters audio, making it somewhat usable. I'm hoping either Apple, Parallels, or Microsoft did something to fix that. The release notes never say so I lack confidence it'll stay working.

 

I hope so. They simply closed my case after unhelpful suggestions.

 

still having this issue, sometimes after VM resume system time jumps into the future:

Code:

timedatectl
               Local time: Wed 2120-01-03 15:10:08 CET
           Universal time: Wed 2120-01-03 14:10:08 UTC
                 RTC time: Tue 2024-11-12 10:14:42
                Time zone: Europe/Madrid (CET, +0100)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

 

Just discovered i have this issue on my Ubuntu 22.04 VM, after ugrading to Sequoia, al lnetworking from the vm just broke. Paralells suggested installing the parallels tools, eventually reinstalling Parallels fixed the networking issue, but now the time is also set to the year 2120 and nothing i try can fix this. Its causing all sorts of problems.....

Parallels - give us a solution PLEASE!

 

Yeah, tech support hasn't been helpful at all. I suggest everyone open cases. They don't seem to be escalating to development because not enough people are complaining. Terrible product support from Parallels.

 

I have same issue on ubuntu 2404 parallels. I turn off timedatectl

Code:

sudo timedatectl set-ntp no
sudo apt update
sudo apt install ntp
ntpq -p

then you reboot, the issue will gone

 

I started having an issue immediately after updating to parallels version 20.2.1.
I am running Ubuntu server in a VM and the time is now jumping to January 25th, 2120.
I have tried turning off the time sync with the mac and set the time in unbuntu's command line.
It is fine till I log out, when it then jumps around 96 years into the future.

 

And then I try 19.x and it doesn't change anything.
I restored an old copy of the ubuntu server and it is working correctly now.

 

I have this issue in both parallels 19 and 20. I tried all variations of disabling timectl, ntp, etc. the only thing that has stopped it is disabling smart guard snapshots.

 

I've had smart guard off for a long time.
I manually backup the VM's.
The time issue is underneath an Ubuntu bug that doesn't seem to have been fixed yet.

 

I have same issue since updated to 20.1.2. Any permanent solution from parallels?

 

It seems to be an Ubuntu issue.
The list of time zones gets damaged/cleared and it has perhaps two time zones.
https ://askubuntu.com/questions/1528949/time-setting-problems-with-ubuntu-24-04

 

This time set in future give us all sort of problem. Mysql crash, all the log rotation stopped and log file size increased since current log file set in future. Anyone experiencing other issue?