From: Jens Seidel Subject: Re: CE: xen increasing min_delta_ns to 7651397591976463850 nsec / pvops domU Date: Thu, 25 Feb 2010 23:33:44 +0100 Message-ID: <20100225223342.GA2230@merkur.sol.de> References: <20100222082657.GA26436@merkur.sol.de> <20100225214442.GG2761@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20100225214442.GG2761@reaktio.net> Sender: linux-kernel-owner@vger.kernel.org To: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com Cc: Jens Seidel List-Id: xen-devel@lists.xenproject.org On Thu, Feb 25, 2010 at 11:44:42PM +0200, Pasi K=E4rkk=E4inen wrote: > CCing to xen-devel.. thanks Pasi ... I have more information: =20 > On Mon, Feb 22, 2010 at 09:26:59AM +0100, Jens Seidel wrote: > > I'm using vanilla 2.6.32.7 domU kernel with Xen 3.2 and get very of= ten a > > unresponsible system after approximately one or two days with messa= ges such as The problem seems to occur between 10h - 11.5h (verified three times). Using the options "hpet=3Ddisable clocksource=3Djiffies nolapic acpi=3D= off" the problem vanished but I get a minor time drift between dom0 and domU (an= d missed at least once my bus :-() > > [43616.674502] CE: xen increasing min_delta_ns to 16086592372704132= 408 nsec > >=20 > > on the console. I fail to login via ssh and even to cleanly shutdow= n this > > system via xm shutdown. sysrq requests still work. Oops, forget about sysrq. Now I think it didn't worked. > > PS: Please CC: me. Jens