From owner-freebsd-xen@FreeBSD.ORG Thu Mar 7 14:00:33 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86E87CD0 for ; Thu, 7 Mar 2013 14:00:33 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [199.188.211.146]) by mx1.freebsd.org (Postfix) with ESMTP id 56F63BD7 for ; Thu, 7 Mar 2013 14:00:32 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 14-md50000143000.msg for ; Thu, 07 Mar 2013 08:00:30 -0600 From: "Jay West" To: =?iso-8859-1?Q?'Roger_Pau_Monn=E9'?= References: <000901ce1aa7$90704320$b150c960$@ezwind.net> <000601ce1aed$97e06540$c7a12fc0$@ezwind.net> <513851F1.8080009@citrix.com> In-Reply-To: <513851F1.8080009@citrix.com> Subject: RE: misc. questions Date: Thu, 7 Mar 2013 08:00:32 -0600 Message-ID: <000801ce1b3c$223a5900$66af0b00$@ezwind.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQKL4ehw6L2D+tg443ETJqm5K2YJBgFv1UkzAhkruCQCFALI1pbxy/Qw Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-Spam-Processed: gateway.ezwind.net, Thu, 07 Mar 2013 08:00:30 -0600 (not processed: message from valid local sender) X-MDRemoteIP: 71.14.76.0 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-MDAV-Processed: gateway.ezwind.net, Thu, 07 Mar 2013 08:00:31 -0600 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 07 Mar 2013 14:00:33 -0000 It was written.... >I think there were several fixes for the RTC clock recently, so trying the Xen 4.2 branch might bring some improvements. I'm using Citrix Xenserver 6.1, so stuff from the Xen 4.2 branch isn't available for me.... >Also, it is possible to use the PV clock from HVM (PVHVM) domains, which will probably bring better stability. I'm going to look into this when I have some spare cycles. That I would very much like to know how to do so that I can give it a shot. J