From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: dom0 crash without any message Date: Tue, 4 Jun 2013 12:26:53 -0400 Message-ID: <20130604162653.GA22190@phenom.dumpdata.com> References: <1370277458.24512.47.camel@zakaz.uk.xensource.com> <20130604140523.GB7110@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 Tue, Jun 04, 2013 at 04:21:45PM +0200, William Dauchy wrote: > On Tue, Jun 4, 2013 at 4:05 PM, Konrad Rzeszutek Wilk > wrote: > > Do you see this if you boot the same kernel, but without Xen? > > I haven't tested with a i386 baremetal kernel but with an amd64 > baremetal kernel it boots fine (thanks to the X2APIC in amd64). I > guess that on i386 I've reached the 0xff APIC limit. I would think that the 64-bit kernel under Xen would work as well? > My dom0 is now booting when disabling two cores in the bios config; it > means reducing the cpu from 32 to 24. I hoped for a cmdline solution > instead of changing the bios config but did not find any. Did I miss > one? dom0_max_vcpus did not worked. There is also the Linux ones - nr_cpus= or some variant of it. 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. > > -- > William > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >