From owner-freebsd-virtualization@FreeBSD.ORG Mon May 19 13:56:04 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1C8FF18 for ; Mon, 19 May 2014 13:56:04 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C71A2EAA for ; Mon, 19 May 2014 13:56:04 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 764C2B94A; Mon, 19 May 2014 09:56:03 -0400 (EDT) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: clock wrong in bhyve vm's Date: Mon, 19 May 2014 09:52:16 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201405190952.16343.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 May 2014 09:56:03 -0400 (EDT) Cc: Joe Maloney X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 13:56:04 -0000 On Monday, May 19, 2014 12:15:21 am Joe Maloney wrote: > So far I've created 2 VM's in bhyve with 11 CURRENT updated world as of > today. One VM is running FreeBSD 10. The other is running FreeNAS 9.2.1.6 > Beta. It seems every VM I create has the time wrong about 5 or 6 hours. > Using ntpdate will correct the time until the VM reboots. Has anyone else > noticed this or know of a possible fix other than using ntpd? Is that your offset from UTC? Do you have /etc/localtime set correctly in your guests? -- John Baldwin