From owner-freebsd-questions@FreeBSD.ORG Fri Apr 8 14:33:02 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 101EE16A4D5 for ; Fri, 8 Apr 2005 14:33:02 +0000 (GMT) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id A549943D3F for ; Fri, 8 Apr 2005 14:33:01 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 28087 invoked from network); 8 Apr 2005 14:33:00 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Apr 2005 14:33:00 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 605FA53; Fri, 8 Apr 2005 10:32:59 -0400 (EDT) Sender: lowell@be-well.ilk.org To: dick@nagual.st References: <20050407120148.1904bcae.dick@nagual.st> From: Lowell Gilbert Date: 08 Apr 2005 10:32:58 -0400 In-Reply-To: <20050407120148.1904bcae.dick@nagual.st> Message-ID: <44ekdl8hk5.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: rtc question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2005 14:33:02 -0000 dick hoogendijk writes: > I decided to remove polling and hz=1200 from my kernel. The system was > slower. Things run pretty smooth now (duron-800/512Mb) with the default > HZ=100, /but/ : > > Now vmware3 is complaining about the rtc : timing error, please > increase... > The virtual machine itself runs just fine. If it does no harm I want to > stick to the HZ=100. What does this rtc message mean and what are the > consequenses? An unstable system? Depends what you mean by "unstable". The symptom I would most expect would be the virtual machine seeing some variation in real-time clock rate. In your position, I would try some intermediate values for HZ, and see what happens. In particular, 1000 is the usual recommended value for faster systems, and 200 or 400 might well be okay.