[SOLVED] Debian 9 Parallels Desktop wrong time after waking from suspend

adityavpratap · 07-09-2018, 01:56 AM

Hi,

I am running Debian 9 Gnome on my MacBook Air via Parallels Desktop. Everything works fine except for the fact that when I resume from suspend, the clock shows wrong time.

I tried -

$ sudo hwclock -w

but it does not correct the time.

Any suggestions?

Thanks in advance,

ondoho · 07-11-2018, 07:15 AM

Quote:

Originally Posted by adityavpratap

Everything works fine except for the fact that when I resume from suspend, the clock shows wrong time.

this is normal.
if your computer is connected to the internet, it should fix itself after a minute or so.
if your computer is NOT connected to the internet, the CMOS should provide the correct time.
if the CMOS battery is dead, that won't happen.

i sometimes manually set my date with

Code:

sudo date -s 'Jul 7 15:14'

as an example.

michaelk · 07-11-2018, 08:55 AM

I don't know much about Parallels or how its "hardware clock" works or how or if it keeps track of a virtual machines clock but to set the system time from the hardware clock you would run the command

hwclock -s

If running ntp most likely it has stopped. If you restart ntp it should reset time or as stated you can manually reset time via the date command if the hwclock command does not work.

I assume the virtual machine has no direct connection to the physical hardware clock.

adityavpratap · 07-11-2018, 08:56 AM

Thanks for the reply, eventhough my macbook is connected to internet, Debian shows wrong time whereas outside Parallels Desktop, macos show the correct time!

I'll try to restart ntp, if nothing else works, I'll set the time using the command posted by ondoho!

Thanks again,

ondoho · 07-12-2018, 02:19 AM

Quote:

Originally Posted by adityavpratap

Parallels Desktop

erm.
i missed the importance of this bit.
sorta virtualbox for mac os.
i thought op had installed linux on their macbook.

adityavpratap · 07-12-2018, 04:40 AM

Ok!
Restarting ntp sets the correct time.
Thanks guys, problem solved!