From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Martin Lukasik" <martin.lukasik@cancer.org.uk>,
"Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen CPU limit?
Date: Tue, 30 Mar 2010 10:43:00 +0100 [thread overview]
Message-ID: <C7D78634.EF35%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BB1C52D.7060202@cancer.org.uk>
On 30/03/2010 10:32, "Martin Lukasik" <martin.lukasik@cancer.org.uk> wrote:
> 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?
Yeah, that would be sensible. All dom0 is doing is VM management (i.e.,
running control tools like xend/xm) and also handling I/O, so two cores is
probably plenty.
-- Keir
next prev parent reply other threads:[~2010-03-30 9:43 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 [this message]
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
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=C7D78634.EF35%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=martin.lukasik@cancer.org.uk \
--cc=pasik@iki.fi \
--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).