All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: dom0 crash without any message
Date: Tue, 4 Jun 2013 12:26:53 -0400	[thread overview]
Message-ID: <20130604162653.GA22190@phenom.dumpdata.com> (raw)
In-Reply-To: <CAJ75kXbcr_c+gXcN0SY8+7EEFQV+7hA-A_r32UWWLEq9gzBwDA@mail.gmail.com>

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
> <konrad.wilk@oracle.com> 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
> 

  reply	other threads:[~2013-06-04 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 16:14 dom0 crash without any message William Dauchy
2013-06-03 16:37 ` Ian Campbell
2013-06-03 17:38   ` William Dauchy
2013-06-03 17:45     ` Andrew Cooper
2013-06-03 21:13       ` William Dauchy
2013-06-04 14:05     ` Konrad Rzeszutek Wilk
2013-06-04 14:21       ` William Dauchy
2013-06-04 16:26         ` Konrad Rzeszutek Wilk [this message]
2013-06-05 12:52           ` William Dauchy
2013-06-05 14:56             ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130604162653.GA22190@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=wdauchy@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.