After several months, I'm raising this issue again, now on 2.2.4.
On Dec 8, 2008, at 03:29, Michael Thayer wrote:
Paul Gilmartin wrote:
Running OpenSolaris under VirtualBox 2.0.6 under Tiger
on a MacBook.
It appears that when the MacBook sleeps, VM's clock likewise
sleeps. This morning Solaris was several hours slow.
...
Do I need to run NTP client?
The VirtualBox Guest Additions contain a time synchronisation daemon
which should deal with this.
It appears that either this or NTP steers the clock by only a
fractional increment, perhaps 1%. So after a 15 minute sleep
it takes the clock an entire day to reset. Hardly satisfactory.
The UserManual says,
The Guest Additions will re-synchronize the time regularly.
... What does "regularly" mean? Periodically? How often?
By what increment each time?
I abandoned this matter when a Solaris developer pointed out to
me that while Solaris running native on a laptop correctly resets
the clock after the laptop sleeps, VM has no way of knowing when
the host sleeps. WAD. QED.
But I beleve I have a refutation. When I Pause the VM (Host-P)
VM is certainly aware. But when I Resume (Host-P again), the
clock remains out of sync. I believe that on Resume, VM ought
properly to do whatever is necessary to signal the guest to
reset its clock, even as Solaris does when a laptop lid is closed
and opened.
I believe this (mis-) behavior is portable; it appears likewise
on a Windows host.
Thanks,
gil
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
