Pasi Kärkkäinen wrote:
Why do you need to have all the cores visible to dom0?
It's usually enough to have a couple of cores for dom0,
and the rest free/available in Xen hypervisor for other guests.
I read three books about Xen, but surely they weren't a good read. Many
things haven't been even mentioned (btw: can anyone recommend a *good*
book on Xen?)
I thought that the way it works is: you set up Dom0 with max number of
CPUs and then allocate them to VMs.
But since Dom0 is a VM as Keir said, then it all must be up to a hypervisor.
So I need a hypervisor to support 48 cores, then set up Dom0 with let's
say 2 vCPUs and 1GB of RAM, and create other VMs according to my
requirements.
Am I right?
Thank you,
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