Jan Beulich wrote:
Martin Lukasik <martin.lukasik@xxxxxxxxxxxxx> 11.03.10 17:08 >>>
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?
This is done on the make command line, by adding "max_phys_cpus=...".
Jan
Yeah... I thought that installing it from RPM wasn't a good idea... ;-)
Thanks for the info. Will give it a try some time this week.
BTW.: Wouldn't it make sense to include support for max number of CPUs
when building RPMs?
Martin
--
-----------------------------------------------------------------------
Martin Lukasik tel: +44 20 7269 3115
Bioinformatics Officer
Bioinformatics and Biostatistics
Cancer Research UK, London Research Institute
44 Lincoln's Inn Fields, London, WC2A 3PX, UK
-----------------------------------------------------------------------
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home