From: Stefan de Konink <stefan@konink.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Questions about certain Xen limits and features
Date: Mon, 10 Nov 2008 02:51:52 +0100 [thread overview]
Message-ID: <491793B8.5070904@konink.de> (raw)
In-Reply-To: <C539FFB4.1F0AF%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
>> (2a) What's the largest host memory that anybody has tested?
>> (2b) What's the expected host memory limit (if somebody was able to
>> configure a system that large)?
>
> I think 256GB has been tested. Theoretically we're good up to 1TB, and we
> could expand beyond even that without too much trouble.
I have seen *very* weird bugs related to kernel error reporting when I
made the switch from 16GB to 32GB of memory. I can do this 'semi'
dynamically using a Dell 1950.
To be able to actually boot system with 32GB I have to append; i8042.noaux
Might be good reference for other people.
Stefan
prev parent reply other threads:[~2008-11-10 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 14:01 Questions about certain Xen limits and features Vessey, Bruce A
2008-11-07 14:22 ` Keir Fraser
2008-11-07 14:30 ` Jan Beulich
2008-11-07 15:40 ` Vessey, Bruce A
2008-11-10 1:51 ` Stefan de Konink [this message]
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=491793B8.5070904@konink.de \
--to=stefan@konink.de \
--cc=keir.fraser@eu.citrix.com \
--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.