From owner-freebsd-stable@FreeBSD.ORG Sat Mar 10 13:57:00 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31363106566B for ; Sat, 10 Mar 2012 13:57:00 +0000 (UTC) (envelope-from adams-freebsd@ateamsystems.com) Received: from fss.sandiego.ateamservers.com (fss.sandiego.ateamservers.com [69.55.229.149]) by mx1.freebsd.org (Postfix) with ESMTP id 1326B8FC0A for ; Sat, 10 Mar 2012 13:56:59 +0000 (UTC) Received: from [192.168.15.220] (unknown [118.175.84.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by fss.sandiego.ateamservers.com (Postfix) with ESMTPSA id F06A0B9F36; Sat, 10 Mar 2012 08:56:57 -0500 (EST) Message-ID: <4F5B5DAB.3010905@ateamsystems.com> Date: Sat, 10 Mar 2012 20:56:59 +0700 From: Adam Strohl Organization: A-Team Systems User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4F5B0BB5.5010406@ateamsystems.com> <6D0B99CE-AE11-4250-A8D9-EF66E03E19BB@lists.zabbadoz.net> In-Reply-To: <6D0B99CE-AE11-4250-A8D9-EF66E03E19BB@lists.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Stable ML Subject: Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2012 13:57:00 -0000 On 3/10/2012 17:10, Bjoern A. Zeeb wrote: > On 10. Mar 2012, at 08:07 , Adam Strohl wrote: > >> I've now seen this on two different VMs on two different ESXi servers (Xeon based hosts but different hardware otherwise and at different facilities): >> >> Everything runs fine for weeks then (seemingly) suddenly/randomly the clock STOPS. > > Apart from the ntp vs. openvm-tools thing, do you have an idea what "for weeks" means in more detail? Can you check based on last/daily mails/.. how many days it was since last reboot to a) see if it's close to a integer wrap-around or b) to give anyone who wants to reproduce this maybe a clue on how long they'll have to wait? For that matter, is it a stock 9.0 or your own kernel? What other modules are loaded? Uptime was 31 days on the first incident / server (occurred 5 days ago) Uptime was 4 days on the second incident / server (occurred last night) One additional unique factor I just thought of: the two problem VMs have 4 cores allocated to them inside ESXi, while the rest have 2 cores. Kernel config is a copy of GENERIC (amd64) with the following lines added to the bottom. All the VMs use this same kernel which I compiled once and then installed via NFS on the rest: # -- Add Support for nicer console # options VESA options SC_PIXEL_MODE # -- IPFW support # options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 options IPDIVERT options IPFIREWALL_FORWARD