Date: Fri, 13 Jul 2007 23:36:49 +0200 From: Thomas Backman <serenity@exscape.org> To: Dominique Goncalves <dominique.goncalves@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD uses the year 1936 in qemu Message-ID: <EF99037F-7D71-4DA9-8227-A2EDE6D2E86D@exscape.org> In-Reply-To: <7daacbbe0707131333q7a290e2bn6d0999151f6d5777@mail.gmail.com> References: <7daacbbe0707131333q7a290e2bn6d0999151f6d5777@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 13, 2007, at 10:33 PM, Dominique Goncalves wrote: > Hi, > > I'm trying to run FreeBSD 7.0-CURRENT as a guest in qemu-0.9.0 (using > freesbie), but FreeBSD thinks the current date is Sat 31 oct 1936. > newsyslog and syslogd do not start correctly. > > Creating and/or trimming log files: > newsyslog: > malformed 'at' value: > /var/log/all.log 600 7 * @T00 J > > . > <snip> > Of course I can use ntpd or ntpdate but it's too late in the > startup order. > I found a similar problem [1] reported which proposes a fix [2]. > I applied the patch in PR i386/111117 and the date is now set > correclty inside qemu. > > Is this a bug in FreeBSD or qemu ? This happens in VMWare (VMWare Fusion, to be exact) as well. The same topic was up recently (last post today), "Debugging time". According to the last post, the issue seems to be resolved (but with no patch commited). /Thomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF99037F-7D71-4DA9-8227-A2EDE6D2E86D>