From: Joshua West <jwest@brandeis.edu>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Hypervisor Memory Limitations on 64-bit Architecture?
Date: Fri, 18 Jul 2008 18:49:26 -0400 [thread overview]
Message-ID: <48811DF6.2040309@brandeis.edu> (raw)
In-Reply-To: <20080718191008.GC3771@edu.joroinen.fi>
Hi Pasi,
Thanks for the information. Do you have any details regarding x86_64
architecture memory limits with the Xen Hypervisor, using stock Xen --
instead of those modified/patched by vendors like Red Hat?
Thanks.
Pasi Kärkkäinen wrote:
> On Fri, Jul 18, 2008 at 12:56:34PM -0400, Joshua West wrote:
>
>> Hey all,
>>
>> I'm wondering if anybody could shed some light on this subject. Are
>> there limitations as to how much RAM a 64-bit Hypervisor will
>> recognize/support under the Xen 3.1.x or 3.2.x series (or the upcoming
>> 3.3.x if anything has changed)?
>>
>> >From what I recall, a 32-bit Xen Hypervisor will recognize up to 16GB of
>> RAM and a 64-bit Xen Hypervisor will recognize up to 32GB -- but I'm not
>> certain on if 32GB is in fact the upper limit for 64-bit Xen.
>>
>>
>
> http://www.redhat.com/rhel/compare/
>
> RHEL5 supports 16 GB of mem on x86 (32bit) platform.
> RHEL5 supports 256 GB of mem on x86_64 platform.
>
> And RHEL5 contains Xen.
>
> http://www.nabble.com/Unable-to-start-hvm-guest-on-cs16998-td15419631.html
>
> "Running Xen Unstable changeset 16998 (pulled 20080208) on Unisys ES7000/one 64x 256gb with SLE10SP1 x64."
>
> There you have an actual server with 256 GB of mem running Xen :)
>
> (yeah, the mail is about problems, but hey, it's xen-unstable repository
> they're testing there :)
>
> -- Pasi
>
--
Joshua West
Systems Engineer
Brandeis University
http://www.brandeis.edu
next prev parent reply other threads:[~2008-07-18 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 16:56 Hypervisor Memory Limitations on 64-bit Architecture? Joshua West
2008-07-18 19:10 ` Pasi Kärkkäinen
2008-07-18 22:49 ` Joshua West [this message]
2008-07-21 13:17 ` Konrad Rzeszutek
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=48811DF6.2040309@brandeis.edu \
--to=jwest@brandeis.edu \
--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 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.