[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 11:13:20 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 06 Oct 2009 08:14:22 -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 :content-transfer-encoding; b=dpRhhGkZyPHsf7h3O75VJqkSfBrzxIv4pxI3CkvIf8cNop0B/iHcOI48OBL/yY+eJw GrAIHus9002lzbZTmQNi1TETXn3wqpq0yNweanqdL8j/vnVOyHyIt9J6otjZBoMFt7uK Nl3YuolYNjXUriLUxSQ8pnEj6fBDT8hMgRSnk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> It looks like its encountering a pfn (page number) that's greater than
> the total number of pages given to the domain.
> Aaah, 36GB memory.  What happens if you configure
> CONFIG_XEN_MAX_DOMAIN_MEMORY larger to match, or set dom0_mem to less
> than 32GB?
> (It shouldn't crash regardless, but it will confirm the diagnosis.)

Ok, so I tried setting dom0_mem to a variety of values less than 32GB.
 I'm still getting a crash, but now it is more random.  Basically, I'm
watching the boot process via a serial line, and instead of seeing the
dom0 crash output that I posted before, I'm simply seeing the output
stop, and the boot process hanging, in a different spot with each
boot.  Removing the dom0_mem value beings me back to the behavior I
had before, where the dom0 crash output shows up reliably each time.


Xen-devel mailing list



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