From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 23:58:52 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88D5EF74 for ; Wed, 14 Jan 2015 23:58:52 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5093E5F3 for ; Wed, 14 Jan 2015 23:58:51 +0000 (UTC) Received: from [10.12.30.100] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t0ENwm6L026170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2015 23:58:49 GMT Date: Wed, 14 Jan 2015 23:58:48 +0000 From: Karl Pielorz To: Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <582A8DBAC6CBEE430519DBD0@Karls-Mac-mini.local> In-Reply-To: <54B6F68B.3040403@egr.msu.edu> References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> <54B6D62F.9090002@egr.msu.edu> <979140BCE806D10DE127B63B@Karls-Mac-mini.local> <54B6F68B.3040403@egr.msu.edu> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 23:58:52 -0000 --On 14 January 2015 18:06:51 -0500 Adam McDougall wrote: > Are you sure you are running 6.5 and not 6.2? The guest's kernel should > detect Xen 4.4 instead of 4.1. 6.5 is Creedence but it was called > Creedence during the long alpha stage before it became 6.5. Sorry - my mistake (Coffee is wearing off this time of night) - doesn't help I've seen 'next' XenServer called 7 at some point :) We're running 6.2 - *not* 6.5... -Karl