All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: xen devel <xen-devel@lists.xensource.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: 2.6.27 - SMP enabled, but only 1 CPU
Date: Tue, 04 Nov 2008 15:13:52 -0500	[thread overview]
Message-ID: <4910AD00.7040605@theshore.net> (raw)
In-Reply-To: <490F5F50.7020704@theshore.net>

Christopher S. Aker wrote:
> Christopher S. Aker wrote:
>> I just compiled 2.6.27 (pae) using my .config from 2.6.26.  It boots 
>> fine, but only one CPU shows up, despite "vcpus = 4" and all of the 
>> SMP goodness enabled.  This happens on both Xen 3.2.x and 3.3.x (64 
>> bit hypervisor).
>>
>> beefcake:2.6.27-linode14# grep SMP .config
>> CONFIG_X86_SMP=y
>> CONFIG_X86_32_SMP=y
>> CONFIG_USE_GENERIC_SMP_HELPERS=y
>> CONFIG_SMP=y
>> CONFIG_X86_FIND_SMP_CONFIG=y
>> # CONFIG_X86_VSMP is not set
>> CONFIG_PM_SLEEP_SMP=y
>>
>> root@ubuntu:~# uname -a
>> Linux ubuntu 2.6.27-linode14 #1 SMP Sun Oct 12 20:34:47 EDT 2008 i686 
>> GNU/Linux
>> root@ubuntu:~# cat /proc/cpuinfo
>> processor    : 0
>> ...
>> (and that's it -- just one CPU)
>>
>> I must be missing something obvious, so I'd appreciate another set of 
>> eyes on this.  My .config, boot log, and xen.conf are located here:
>>
>> http://www.theshore.net/~caker/xen/2.6.27-linode14/config.txt
>> http://www.theshore.net/~caker/xen/2.6.27-linode14/bootlog.txt
>> http://www.theshore.net/~caker/xen/2.6.27-linode14/xen.conf
> 
> Same with 2.6.27.4 and a defconfig + the paravirt stuff enabled.  So, 
> what's the trick for getting SMP working with 2.6.27.* domUs?  Has 
> anyone achieved this?

Same thing with x86_64 domUs.  I'll try reverting back to the -rcs...

-Chris

  parent reply	other threads:[~2008-11-04 20:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 21:24 2.6.27 - SMP enabled, but only 1 CPU Christopher S. Aker
     [not found] ` <490F5F50.7020704@theshore.net>
2008-11-04 20:13   ` Christopher S. Aker [this message]
2008-11-05 15:31     ` Christopher S. Aker
2008-11-05 22:38       ` Jeremy Fitzhardinge
2008-11-05 22:57         ` Christopher S. Aker
2008-11-05 22:45       ` Jeremy Fitzhardinge
2008-11-05 23:05         ` Christopher S. Aker
2008-11-06  0:23           ` Jeremy Fitzhardinge
2008-11-06  2:00             ` Christopher S. Aker
2008-11-06  2:23               ` Stefan de Konink
2008-11-06  3:43               ` Jeremy Fitzhardinge
2008-11-06 18:04       ` Ian Campbell
2008-11-06 19:15         ` [Xen-devel] " Jeremy Fitzhardinge
2008-11-06 19:15           ` Jeremy Fitzhardinge
2008-11-06 21:16           ` [Xen-devel] " Ingo Molnar
2008-11-06 21:16             ` Ingo Molnar
2008-11-06 21:20             ` [Xen-devel] " Jeremy Fitzhardinge
2008-11-06 21:20               ` Jeremy Fitzhardinge
2008-11-06 21:22               ` [Xen-devel] " Ingo Molnar
2008-11-06 21:22                 ` Ingo Molnar
2008-11-06 21:28             ` [Xen-devel] " Jeremy Fitzhardinge
2008-11-06 21:28               ` Jeremy Fitzhardinge
2008-11-06 21:33               ` [Xen-devel] " Ingo Molnar
2008-11-06 21:33                 ` Ingo Molnar
2008-11-06 21:48                 ` [Xen-devel] " Jeremy Fitzhardinge
2008-11-06 21:48                   ` Jeremy Fitzhardinge
2008-11-06 22:20                   ` [Xen-devel] " Ingo Molnar
2008-11-06 22:20                     ` Ingo Molnar
2008-11-06 22:29                     ` [Xen-devel] " Jeremy Fitzhardinge
2008-11-06 22:29                       ` Jeremy Fitzhardinge
2008-11-07  9:53                     ` [Xen-devel] " Jan Beulich
2008-11-07  9:53                       ` Jan Beulich

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=4910AD00.7040605@theshore.net \
    --to=caker@theshore.net \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /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.