I believe I've found a bug in build 4128, but I wanted to see if anyone else experiences this. I'm using Windows XP Professional SP2 as my guest OS. If I suspend the VM, and then some time later resume it, the clock in the guest OS is off by the amount of time the VM was suspended. If I shut down the guest OS rather than suspend it, the time is correctly synched. So it seems time synchronization doesn't work when I suspend/resume the VM. Is anyone else experiencing this?
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
time synchronization and suspend/resume bug
- Thread starter friley
- Start date
friley said:I believe I've found a bug in build 4128, but I wanted to see if anyone else experiences this. I'm using Windows XP Professional SP2 as my guest OS. If I suspend the VM, and then some time later resume it, the clock in the guest OS is off by the amount of time the VM was suspended. If I shut down the guest OS rather than suspend it, the time is correctly synched. So it seems time synchronization doesn't work when I suspend/resume the VM. Is anyone else experiencing this?
This doesn't really sound like a bug. Sounds like Windows is storing time in RAM, so resuming will restore the old time. If set to check the time on a time server, it will fix itself after a while. I suppose restarting causes it to check the CPU clock, which means the time is then set correctly.
I got a reply from Parallels. It apparently takes "a few minutes" to synchronize. It took 15 minutes when I just tried it. Strange, I would think it would synch right away, then start the synch timer for the amount of time you have set in the preferences. Anyway, it appears I was just too impatient.
My PD 2.5 (build 3214) XP(SP2) VM only took 5-6 seconds to correct it's time sync after being paused.
My PD 3.0 (build 4128) XP(SP2) VM took about 30-40 seconds to correct it's time sync after being paused.
I did also notice diffent default Time Synchronization settings in Parallels Tools Center. PD 2.5 does not default to having "Keep time difference between primary and guest OS" checked, while PD 3.0 does have this Advanced option checked by default.
Our Windows Domain Controllers provide time services for Windows clients, although Mac clients are set to time.apple.com (yes, I know: they should all point to same time server, but...).
Also, both VMs are configured for Bridged Ethernet.
My PD 3.0 (build 4128) XP(SP2) VM took about 30-40 seconds to correct it's time sync after being paused.
I did also notice diffent default Time Synchronization settings in Parallels Tools Center. PD 2.5 does not default to having "Keep time difference between primary and guest OS" checked, while PD 3.0 does have this Advanced option checked by default.
Our Windows Domain Controllers provide time services for Windows clients, although Mac clients are set to time.apple.com (yes, I know: they should all point to same time server, but...).
Also, both VMs are configured for Bridged Ethernet.
Last edited: