From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mauro <mrsanna1@gmail.com>
Subject: Re: [Xen-devel] Xen 4 TSC problems
Date: Thu, 27 Sep 2012 23:42:04 +0200
Message-ID: <CAE17a0VkMuUEG9VaM7AFrwcsEjVBq9RfvTWz1_KmscAyCxeAbA@mail.gmail.com>
References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default>
	<AANLkTi=NFebVsnj_09+SpCZUo_bNTnTyJLAoR5sfbwZa@mail.gmail.com>
	<AANLkTikptc2POrKQgJuoVZRdwJTo64DJ_hm12KuPky4D@mail.gmail.com>
	<b1ca6ddc-ca69-447e-93e9-8d36d1ff4a43@default>
	<AANLkTinK94GDOF_GeaVs50wK0u8EdZ2rtzPuh65ca8qR@mail.gmail.com>
	<CAE17a0UPyzsNn=ps9MxarkGg=ns8dCpVz0qBDvesT2AOskwfVg@mail.gmail.com>
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	<CABx4GKrQxOOQo_uUXSFvy0nzdMp1A_qc=_e4K+88GkB7xv=9nw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-users-bounces@lists.xen.org>
In-Reply-To: <CABx4GKrQxOOQo_uUXSFvy0nzdMp1A_qc=_e4K+88GkB7xv=9nw@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-users>,
	<mailto:xen-users-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-users@lists.xen.org>
List-Help: <mailto:xen-users-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xen.org?subject=subscribe>
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org
To: Olivier Hanesse <olivier.hanesse@gmail.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>, xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>, Jeremy Fitzhardinge <jeremy@goop.org>, Jan Beulich <JBeulich@novell.com>, Keir Fraser <keir.xen@gmail.com>, Xen Users <xen-users@lists.xensource.com>, Mark Adams <mark@campbell-lange.net>
List-Id: xen-devel@lists.xenproject.org

On 27 September 2012 23:28, Olivier Hanesse <olivier.hanesse@gmail.com> wrote:
> Hello,
>
> From my point of view, this was a kind of xen hardware "incompatibility/bug"
> : I was able to reproduce this bug on more than 50 identical servers, but
> not on another farm of servers with a different hardware.
> Xen version, Debian Kernel was exactly the same on both farm.

Yes I think so.
The problem is where I use debian squeeze with xen 4.0.
In another server with the same hardware but with debian lenny and xen
3.0 I have no problems.
I've read that a workaround is to set clocksource=pit on the xen boot
line in the grub conf, I hope this works because I can't change hardware.