From owner-freebsd-stable@FreeBSD.ORG Sat Mar 10 08:07:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22D51106566B for ; Sat, 10 Mar 2012 08:07:23 +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 0BEBF8FC19 for ; Sat, 10 Mar 2012 08:07:22 +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 DA516B9E1A for ; Sat, 10 Mar 2012 03:07:15 -0500 (EST) Message-ID: <4F5B0BB5.5010406@ateamsystems.com> Date: Sat, 10 Mar 2012 15:07:17 +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: FreeBSD-Stable ML Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 08:07:23 -0000 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. In the first case I saw a jump backwards of about 15 minutes (and then a 'freeze' of the clock). The second time just 'time standing still' with no backwards jump. Logging accuracy is of course questionable given the nature of the issue, but nothing really jumps out (ie; I don't see NTPd adjusting the time just before this happens or anything like that). Naturally the clock stopping causes major issues, but the machine does technically stay running. My open sessions respond, but anything that relies on time moving forward hangs. I can't even gracefully reboot it because shutdown/etc all rely on time moving forward (heh). So I'm not sure if this is a VMWare/ESXi issue or a FreeBSD issue, or some kind of interaction between the two. I manage lots of VMWare based FreeBSD VMs, but these are the only ESXi 5.0 servers and the only FreeBSD 9.0 VMs. I have never seen anything quite like this before, and last night as I mentioned above I had it happen for the second time on a different VM + ESXi server combo so I'm not thinking its a fluke anymore. I've looked for other reports of this both in VMWare and FreeBSD contexts and not seeing anything. What is interesting is that the 2 servers that have shown this issue perform similar tasks, which are different from the other VMs which have not shown this issue (yet). This is 2 VMs out of a dozen VMs spread over two ESXi servers on different coasts. This might be a coincidence but seems suspicious. These two VMs run these services (where as the other VMs don't): - BIND - CouchDB - MySQL - NFS server - Dovecot 2.x I would also say that these two VMs probably are the most active, have the most RAM and consume the most CPU because of what they do (vs. the others). I have disabled NTPd since I am running the OpenVM Tools (which I believe should be keeping the time in sync with the ESXi host, which itself uses NTP), my only guess is maybe there is some kind of collision where NTPd and OpenVMTools were adjusting the time at the same time. I'm playing the waiting game now to see what this brings (again though I am running NTPd and OpenVMTools on all the other VMs which have yet to show this issue). Anyone seen anything like this? Ring any bells? -- Adam Strohl A-Team Systems http://ateamsystems.com/