From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: dom0 crash without any message Date: Wed, 5 Jun 2013 10:56:25 -0400 Message-ID: <20130605145625.GA28843@phenom.dumpdata.com> References: <1370277458.24512.47.camel@zakaz.uk.xensource.com> <20130604140523.GB7110@phenom.dumpdata.com> <20130604162653.GA22190@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: William Dauchy Cc: Ian Campbell , xen-devel List-Id: xen-devel@lists.xenproject.org On Wed, Jun 05, 2013 at 02:52:49PM +0200, William Dauchy wrote: > On Tue, Jun 4, 2013 at 6:26 PM, Konrad Rzeszutek Wilk > wrote: > > I would think that the 64-bit kernel under Xen would work as well? > > haven't tested but I guess so regarding the issue. > > > There is also the Linux ones - nr_cpus= or some variant of it. > > yup, it only worked through bios configuration. > > > But instead of using work-arounds I would like to understand why you are > > hitting this and fix it. > > Hence the question about baremetal - and if you could kindly also attach > > the serial log of that bootup - it could in figuring out what is going > > on. > > you mean an i386 baremetal log? Yes. > > -- > William