All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: Arbitrary reboot with xen 3.4.x
Date: Thu, 19 Nov 2009 19:06:56 +0100	[thread overview]
Message-ID: <4B058940.2050009@inria.fr> (raw)

Hello.

I've a dom0 working perfectly under xen 3.3.x, with a bout 15 HVM domU. 
When migrating to xen 3.4.1, with the same dom0 kernel (2.6.27.37), 
everything seems to be fine, I can launch the various hosts, but 5 to 10 
minutes later, the host violently reboot... I can't find any trace in 
the logs. I do have a second host with the same configuration and setup, 
and the result is similar. It seems to be linked with domU activity, 
because without any domU, or without any domU with actual activity, I 
don't have any reboot. I had to rollback to xen 3.3.0.

I already attempted such upgrade to xen 3.4.0 this summer, with exactly 
the same result.

It seems like an hardware issue (but it doesn't appears with 3.3.0), or 
a crash in the hypervisor, than syslog is unable to catch when it 
appears. How can I try to get a trace ?
-- 
BOFH excuse #248:

Too much radiation coming from the soil.

             reply	other threads:[~2009-11-19 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 18:06 Guillaume Rousse [this message]
2009-11-19 18:09 ` Arbitrary reboot with xen 3.4.x Pasi Kärkkäinen
2009-11-20 10:42   ` Guillaume Rousse
2009-11-20 13:35     ` Pasi Kärkkäinen
2009-11-21  1:29       ` Blktap device monitoring code! Ata E Husain
2009-11-20 22:48         ` Daniel Stodden
2009-11-21 13:49       ` Arbitrary reboot with xen 3.4.x Guillaume Rousse

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=4B058940.2050009@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.