| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] XEN 4.0 + 2.6.31.13 pvops kernel : system crashes on sta
Actually, I did identify the problem (don’t know the fix) at least from
the console logs. Its related to running out of nr_irq's (attached JPG
for the console log).
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Tuesday, April 27, 2010 5:44 PM
To: Yuvraj Agarwal; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] XEN 4.0 + 2.6.31.13 pvops kernel : system crashes
on starting 155th domU
On 27/04/2010 08:41, "Yuvraj Agarwal" <yuvraj@xxxxxxxxxxx> wrote:
> Attached is the output of /var/log/daemon.log and /var/log/xen/xend.log,
but
> as far as we can see we don¹t quite know what might be going causing the
> system to crash (no console access anymore and system becomes
unresponsive and
> needs to be power-cycled). I have pasted only the relevant bits of
> information (the last domU that did successfully start and the next one
that
> failed). It may be the case that all the log messages weren¹t flushed
before
> the system crashedŠ
>
> Does anyone know where this limit of 155 domU is coming from and how we
can
> fix/increase it?
Get a serial line on a test box, and capture Xen logging output on it. You
can both see if any crash messages come from Xen when the 155th domain is
created, and also try the serial debug keys (e.g., try 'h' to get help to
start with) to see whether Xen itself is still alive.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
console-log-xen.JPG
Description: JPEG image
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home
