Dirk H. Schulz wrote:
Jean-Yves Migeon schrieb:dom0 is critical in regards to security, and must remain 100% reliable even in cases where domU is crippled (security by isolation). If it crashes because of a domU, it is clearly buggy, and makes assumption on a state or condition it should not to.That is the theory I also had in mind. :-)The real server ran CentOS dom0 and domU without any crashes for many, many months now. I simply reinstalled it with Debian Lenny and started moving Debian and NetBSD domUs there. That means: It can be a hardware failure, of course, but it is unlikely, I think, especially with this behaviour pattern: a crash only if certain domUs are run.Faulty hardware may be a source of problem too.
You mean that it also crashes the same way with just the dom0 and one NetBSD domU running?
How does it report the crash? Non responsive console? Blank screen?
Without further information, it is hard to tell. A good start would be a stacktrace, xm dmesg, or Xen console output.A stacktrace of the dom0 kernel, then?I have never done that (and googling did not show up any fast howto), so please point me to docs on that, if possible.
For Linux, a trace would look something like this, logged to console output (typically, your screen, or serial port):
http://pastebin.com/f4db7480c (look for "oops") Documentation: http://kerneltrap.org/sup/3648/oops-tracing.txt http://lkcd.sourceforge.net/ Just wondering: is there an X server running in your dom0? -- Jean-Yves Migeon jeanyves.migeon%free.fr@localhost