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

Re: [Xen-devel] dom0 crash with unstable

  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
  • Date: Tue, 6 Oct 2009 13:23:41 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Oct 2009 10:24:17 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=OEh8bsQ8RhdnCsP4RFff+kyQxLALiMtUmfhWUvoq7rcERlAP1GSA6tsntHgdzdg1/M BYT4C8v+Hy/6NTjj9ynSI0Fy6SiQ0OCdA+2/PZhrbCvXBGmBEXOeIiYDuDt6EKU3GxU7 eScIJqdXfOKhUY+k1wk9AnWnAxIYQRlwpvBcs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> That's mysterious.  My first thought is that this is a separate problem.
I agree... and thanks for your help in diagnosing this issue.

> Is it ever stable?  What happens if you set dom0_mem to 4G or less?
It still crashes, even with 2G of dom0 memory.

> Is the console responsive when the kernel hangs?  That is, can you type
> "Ctrl-A Ctrl-A Ctrl-A" to get Xen, then enter debug keys?  '0' (zero)
> should dump the context for dom0 and give some clue about where it is dying.
Yes, this seems to work.  Typing 0 dumped info for each of the cores
(i.e., 15 vcpu states).  I've attached the output.


Attachment: log.txt
Description: Text document

Xen-devel mailing list



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