From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen CPU limit? Date: Mon, 29 Mar 2010 17:27:29 +0100 Message-ID: References: <4B991586.30602@cancer.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B991586.30602@cancer.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Martin Lukasik , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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" 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