xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Martin Lukasik <martin.lukasik@cancer.org.uk>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen CPU limit?
Date: Mon, 29 Mar 2010 17:27:29 +0100	[thread overview]
Message-ID: <C7D69381.EC0E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B991586.30602@cancer.org.uk>

Latest Xen supports up to 128 CPUs by default. Earlier versions you can try
rebuilding (for example): "make xen max_phys_cpus=64".

 -- Keir

On 11/03/2010 17:08, "Martin Lukasik" <martin.lukasik@cancer.org.uk> wrote:

> Hello,
> 
> Can somebody explain why the number of CPUs Xen can handle is limited to 32?
> I have a machine with 48 cores, and would love to virtualise it, but if
> I do it, I loose 16 CPUs, which isnt very good... :-(
> Where is this limit coming from? Or maybe it is possible to change it
> somewhere in the source files?
> 
> Cheers,
> Martin
> 
> 
> This communication is from Cancer Research UK. Our website is at
> www.cancerresearchuk.org. We are a charity registered under number 1089464 and
> a company limited by guarantee registered in England & Wales under number
> 4325234. Our registered address is 61 Lincoln's Inn Fields, London WC2A 3PX.
> Our central telephone number is 020 7242 0200.
>  
> This communication and any attachments contain information which is
> confidential and may also be privileged.   It is for the exclusive use of the
> intended recipient(s).  If you are not the intended recipient(s) please note
> that any form of disclosure, distribution, copying or use of this
> communication or the information in it or in any attachments is strictly
> prohibited and may be unlawful.  If you have received this communication in
> error, please notify the sender and delete the email and destroy any copies of
> it.
>  
> E-mail communications cannot be guaranteed to be secure or error free, as
> information could be intercepted, corrupted, amended, lost, destroyed, arrive
> late or incomplete, or contain viruses.  We do not accept liability for any
> such matters or their consequences.  Anyone who communicates with us by e-mail
> is taken to accept the risks in doing so.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      parent reply	other threads:[~2010-03-29 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 16:08 Xen CPU limit? Martin Lukasik
2010-03-29 15:49 ` Pasi Kärkkäinen
2010-03-30  7:16   ` Jan Beulich
2010-03-30  7:53     ` Pasi Kärkkäinen
2010-03-30  8:56       ` Jan Beulich
2010-03-30 16:14       ` Dan Magenheimer
2010-03-31  7:11         ` Jan Beulich
2010-03-30  9:16   ` Martin Lukasik
2010-03-30  9:23     ` Keir Fraser
2010-03-30  9:26     ` Pasi Kärkkäinen
2010-03-30  9:32       ` Martin Lukasik
2010-03-30  9:39         ` Pasi Kärkkäinen
2010-03-30  9:43         ` Keir Fraser
2010-03-29 16:00 ` Jan Beulich
2010-03-29 16:03   ` Martin Lukasik
2010-03-29 16:17     ` Jan Beulich
2010-03-29 16:27 ` Keir Fraser [this message]

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=C7D69381.EC0E%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=martin.lukasik@cancer.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).