xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	RAPHAEL REMONDINI <raphael.remondini@laposte.net>
Subject: Re: Dom0 crashed with xen4.0 and DEBIAN SQUEEZE AMD64
Date: Thu, 14 Apr 2011 09:00:59 -0400	[thread overview]
Message-ID: <20110414130059.GC5548@dumpdata.com> (raw)
In-Reply-To: <20110413070450.GP32595@reaktio.net>

On Wed, Apr 13, 2011 at 10:04:51AM +0300, Pasi Kärkkäinen wrote:
> On Fri, Apr 08, 2011 at 03:33:34PM +0200, RAPHAEL REMONDINI wrote:
> >    Hi
> > 
> >    I have installed xen4.0.1 on DEBIAN SQUEEZE 64 bits with 2.6.32-5 xen
> >    kernel.


> > 
> >    My server is HP PROLIANT DL160 with 16Go RAM with  Intel Xeon Quad Core
> >    E5504
> > 
> >    When start the server on kernel xen hypervisor the system reboot !!!
> > 
> 
> You should try using the latest dom0 kernel from Jeremy's xen.git 
> xen/stable-2.6.32.x branch and see if that makes a difference.
> 
> http://wiki.xen.org/xenwiki/XenParavirtOps
> 
> Debian's 2.6.32-5-xen kernel is based on a snapshot from last summer.
> (although there are some fixes included in the later revisions).

OK. It looks like you are hitting on a well known bug that ought at some point make
it in the stable tree. If you would like to get the fix right away we can send you
the fix and you can compile the kernel yourself.

Stefano, is the patch in your for-stable-2.6.32.32 OK for folks to use?

  reply	other threads:[~2011-04-14 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 13:33 Dom0 crashed with xen4.0 and DEBIAN SQUEEZE AMD64 RAPHAEL REMONDINI
2011-04-13  7:04 ` Pasi Kärkkäinen
2011-04-14 13:00   ` Konrad Rzeszutek Wilk [this message]
2011-04-14 14:03     ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110414130059.GC5548@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=pasik@iki.fi \
    --cc=raphael.remondini@laposte.net \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).