> OS reports when booting always the message:
> WARNING: Time-of-day chip unresponsive; dead
> batteries? (this is inside a VM)
>
> This causes it to have a wrong time (like year 1986),
> until NTP has been started...
Hmm, yet another bug. It seems the root cause is a
bug in vmware, and some (but not all?) versions of
vmware fill be fixed, see bug 4788
http://defect.opensolaris.org/bz/show_bug.cgi?id=4788
At the same time a workaround will be added to OpenSolaris
build 110 to avoid the vmware bug:
Bug ID: 6741572
Synopsis: Time-of-Day chip not detected under vmware
http://bugs.opensolaris.org/view_bug.do?bug_id=6741572
> Here the output from the other logfile (last two lines):
> [ Dec 28 01:00:23 Executing start method
> ("/lib/svc/method/svc-hal start"). ] hal failed to start: error 2
> [ Mar 9 19:19:39 Method "start" exited with status 95. ]
>
> So yeah, inbetween those two lines, around 22 years pass ;)
Ok, so NTP will change the system clock. And this
seems to race with hald startup; due to bug 6792302
hald startup fails.... And without hald, Xorg fails, too.
> Any idea what I could do otherwise?
> Somehow to disable NTP until the GUI is running?
An idea would be to add a dependency on svc:/network/ntp:default
to the svc:/system/hal:default service. So that ntp
has fixed the clock, before hald tries to start.
Or check for and install vmware updates. According to
opensolaris bug 4788, some vmware produces
(e.g. Fusion 2.0.2) already have the fix.
--
This message posted from opensolaris.org
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
