From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 07:20:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7848C16A41F for ; Tue, 6 Dec 2005 07:20:44 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from blues.hansabank.lt (blues.hansabank.lt [193.109.235.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0290343D49 for ; Tue, 6 Dec 2005 07:20:43 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by blues.hansabank.lt (Postfix) with ESMTP id E6AD846129 for ; Tue, 6 Dec 2005 09:20:42 +0200 (EET) X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 6 Dec 2005 09:20:39 +0200 Message-ID: <217202CB5FF8AE439E263CE3D48ECB509BAA75@honda.int.hansa.lt> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: vmware calcru runtime went backward and huge inaccuracy in clock Thread-Index: AcX6MYjvpIXiBSxQQsCEOgy7Z5O8yQAA7SwA From: "Putinas Piliponis" To: Subject: RE: vmware calcru runtime went backward and huge inaccuracy in clock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 07:20:44 -0000 As additional test I have copied 6.0-STABLE to another host under VMWare 5.0 where 5.4-STABLE doesn't have issues with clock. Behaviour of 6 is same. So for me looks it's a FreeBSD 6.0 thing now. -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Putinas Piliponis Sent: Tuesday, December 06, 2005 8:52 AM To: freebsd-current@freebsd.org Subject: vmware calcru runtime went backward and huge inaccuracy in clock Hey, =20 I know I am not the first who brings up this problem. But browsing trough mail archives I didn't found a working solution. I am running vmware 5.5 currently and FreeBSD 6.0-RELEASE. After upgrading from 5.4 (at the same time I upgraded vmware from 5.0 so can't really say which fault is it). I noticed what I don't get daily reports. After small investigation I found out what clock inaccuracy is like in 2 minutes I get 1 minute time delay from real clock. (I wait 2 minutes, I do ntpdate with server, I get every time offset 60 seconds) I tried all kern.timecounter.hardware available options (ACPI-Fast, i8254, TSC) pretty much same result with all of them. =20 Time on host machine is accurate. As well I have on other host (with same hardware) running VMware 5.0 with FreeBSD 5.4 with timecounter.hardware: ACPI-safe and time accuracy there is like 60s in 24h (or normal in other words). =20 =20 Soo.. here comes my question, is it vmware fault, or is it FreeBSD fault? And any suggestions what I can do about ? =20 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"