From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: whit <whitson22@comcast.net>, xen-devel@lists.xensource.com
Subject: Re: Supported #of CPUs/VMs per CPUs
Date: Mon, 18 Sep 2006 13:17:05 +0100 [thread overview]
Message-ID: <20060918121705.GD25730@redhat.com> (raw)
In-Reply-To: <C1342401.152F%Keir.Fraser@cl.cam.ac.uk>
On Mon, Sep 18, 2006 at 10:22:57AM +0100, Keir Fraser wrote:
> On 15/9/06 18:18, "whit" <whitson22@comcast.net> wrote:
>
> > Can find documented how many CPUS can Xen support and how many Virtual
> > Machines per CPU are allowed? Can someone please supply this info?
>
> Xen supports up to 32 CPUs on a 32-bit system, or 64 CPUs (by default) on a
> 64-bit system. Guests can have up to 32 virtual CPUs. The only limit to
> number of domains is amount of hardware resource (mainly memory) that you
> have to share.
Are these hard limits, or just the kernel config defaults for Xen kernels ?
Any reason the guest VCPU count is limited to less than the physical number
on x86_64 ? (not that I expect much demand for 64 CPU guests)
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-09-18 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 17:18 Supported #of CPUs/VMs per CPUs whit
2006-09-18 9:22 ` Keir Fraser
2006-09-18 12:04 ` whit
2006-09-18 12:23 ` Keir Fraser
2006-09-18 14:23 ` Puthiyaparambil, Aravindh
2006-09-18 14:45 ` Keir Fraser
2006-09-18 13:40 ` George Dunlap
2006-09-22 0:34 ` Florian Kirstein
2006-09-22 9:02 ` Petersson, Mats
2006-09-22 13:45 ` George Dunlap
2006-09-18 12:17 ` Daniel P. Berrange [this message]
2006-09-18 12:29 ` 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=20060918121705.GD25730@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=whitson22@comcast.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.