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

Re: [Xen-users] Re: dom0 freezing


  • To: "Bernhard Schmidt" <berni@xxxxxxxxxxxxx>
  • From: "Ray Barnes" <rrb@xxxxxxxxxxxx>
  • Date: Mon, 9 Jun 2008 02:24:26 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 08 Jun 2008 23:25:36 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=aRh25YGrNmd9VFjR0Wc0mlTKecwzPVn+Nhy2Ujjo9O4qg6BRid2J/+D1XZvKP0Bc9y cQXeSBErxp0kmykEBuDjuIJZATbeP78KxmJOfqMMYxVYM/vqv3drA+FnaOArVtECS76J +vYVMqHsyehzc2pYDA/8mFk+IWebSe5tWWqeQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Since you have IPKVM access, ask your host to boot up memtest86 for
you and let your box "cook" for 12 to 24 hours, as these kinds of
problems are always hardware-related in my experience.  I run a
hosting shop and memtest86 is standard operating procedure for all
server deployments.  It will identify hardware issues with the
motherboard/RAM/cpu usually within minutes, and heat-related issues
usually within 24 hours.  I would recommend not taking the IPKVM off
while it's under test for various reasons.  You'll either get a bad
memory block, a lockup, a reboot, or several passes with no error of
any kind.  HTH.

-Ray


On Sun, Jun 8, 2008 at 5:52 PM, Bernhard Schmidt <berni@xxxxxxxxxxxxx> wrote:
> Stephan Seitz <s.seitz@xxxxxxxxxxxx> wrote:
>
>> Anyway, I found the ubunty gutsy and ubuntu hardy (x32_64) kernels
>> bleeding edge, but NOT stable for production use...
>
> Ubuntu Gutsy has been rock-stable for me since it was released. Hardy
> kernels have several stability issues which usually manifest in an OOPS
> either in dom0 or domU, but I haven't seen a single box freezing without
> any message at all so far.
>
>> If your hoster did have changed all relevant parts, I assume there are some
>> me obscure BIOS settings "changed". In general, I would suggest to
>> move from gaming hardware to server hardware ;)
>
> The crashes (re)appeared when everything except (!) the board was
> changed.
>
> I would happily move to server hardware if
> a) I would find another hoster with native and decent IPv6 on the
> ethernet in a price range suitable for end users
> b) there would be a guarantee that these issues don't happen again
>
> b) is the key here, I have installed a number of Xen boxes, both x32
> and x64 with Debian-Xen, Ubuntu-Xen or homebrew Xen. Some of them had
> their share of issues (flaky drivers, flaky RAM, flaky kernels), but
> none ever failed on me like that. Especially since basically the whole
> system was changed between the old instabilities mid-2007 and the recent
> ones. I totally fail to understand this, may it be gameserver hardware
> or expensive hardware, the system should be stable.
>
>> Feel free to take it (and get a higher MTBF for debugging...)
>> http://boreas.netz-haut.net/pub/kernelpack-2.6.18.8-xen-2008.tar.gz
>
> I'll try that kernel, but I'm pretty sure it will fail as well.
>
> Bernhard
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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


 


Rackspace

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