From: "Jan Beulich" <jbeulich@novell.com>
To: Xen-devel@lists.xensource.com, mukesh.rathor@oracle.com
Subject: Re: max vcpus in dom0
Date: Tue, 27 Apr 2010 09:23:19 +0100 [thread overview]
Message-ID: <4BD6AD07020000780005CF3B@vpn.id2.novell.com> (raw)
>>> Mukesh Rathor 04/27/10 4:20 AM >>>
>Looking at a bug where dom0 is crashing coming up with more than 32
>vcpus, the problem happens trying to initialize 32nd vcpu. I see
>the shared info is limited to 32vcpus, implying we'd have a hard limit
>of 32 vcpus in dom0, correct?
That's the legacy limit, yes. Any attempt to go beyond 32 CPUs requires
the kernel to use the per-vCPU-info-placement hypercall prior to bringing
up those vCPU-s.
Jan
next reply other threads:[~2010-04-27 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 8:23 Jan Beulich [this message]
2010-04-28 2:34 ` max vcpus in dom0 Mukesh Rathor
2010-04-28 15:38 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2010-04-28 6:50 Jan Beulich
2010-04-27 2:17 Mukesh Rathor
2010-04-27 8:59 ` Pasi Kärkkäinen
2010-04-27 18:38 ` Jeremy Fitzhardinge
2010-04-27 18:41 ` Pasi Kärkkäinen
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=4BD6AD07020000780005CF3B@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.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).