From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Martin Lukasik <martin.lukasik@cancer.org.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen CPU limit?
Date: Tue, 30 Mar 2010 12:26:24 +0300 [thread overview]
Message-ID: <20100330092624.GA1878@reaktio.net> (raw)
In-Reply-To: <4BB1C174.6030901@cancer.org.uk>
On Tue, Mar 30, 2010 at 10:16:36AM +0100, Martin Lukasik wrote:
> Pasi Kärkkäinen wrote:
>> I think the number of virtual cpus (vcpus) per guest is (was) 32,
>> and now in Xen 4.0.0 you can have up to 64 vcpus per guest.
>>
>> The max number of physical cpus is 128 or so..
>>
>
> When I said "CPUs" I meant the number of physical CPUs (or strictly
> speaking: cores) visible by Dom0.
> I thought I got my RPM from RedHat's repo, but there is a possibility
> that I'm wrong here... and I thought that Xen won't support more than 32
> cores.
> I'm not really after setting up 48 cores for one virtual machine, just
> wanted to be able to have all 48 visible in Dom0 (and then have up to 16
> per VM).
>
> Thanks for the answers; interesting read.
>
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.
-- Pasi
next prev parent reply other threads:[~2010-03-30 9:26 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 [this message]
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
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=20100330092624.GA1878@reaktio.net \
--to=pasik@iki.fi \
--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).