[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: Xen 4 TSC problems


  • To: "andre.arnold" <andre.arnold@xxxxxxxxx>
  • From: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
  • Date: Fri, 15 Apr 2011 18:31:43 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 15 Apr 2011 09:32:22 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GAkxZBpx4eL68v9bKC81i9+xRY9wrC2AhtDHF3pSoHuhkbdl11ZgIBQRwQZprReLot TXcBd5wSteNHKZ+E7V1D1ymIswOuqVol7kOFkMDbFihFGiWIx265gnvC7d6yU1X9uHmc uYGHic7O8KfnsWJRuQPxJdUoaPp0cT7dnpQEQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

So far yes.
Let's wait another month to tell that setting clocksource=pit was the solution :)


2011/4/15 andre.arnold <andre.arnold@xxxxxxxxx>
Hi,

we experienced the same problem with xen 4 under debian squeeze on
our DELL PowerEdge R815 Servers.

Does the "clocksource=pit" setting solve the problem?

Cheers
Andre

--
View this message in context: http://xen.1045712.n5.nabble.com/Xen-4-TSC-problems-tp3396848p4304962.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.