From: Alex Williamson <alex.williamson@hp.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: Daniel Scott <djscott@mit.edu>, kvm@vger.kernel.org
Subject: Re: Re: 3525MB RAM Limit
Date: Thu, 09 Apr 2009 09:48:48 -0600 [thread overview]
Message-ID: <1239292128.6184.152.camel@bling> (raw)
In-Reply-To: <200904091039.21427.iggy@theiggy.com>
On Thu, 2009-04-09 at 10:39 -0500, Brian Jackson wrote:
> I was thinking of a bug when using large pages, which may not be your problem.
> There have been other reports recently, with workarounds, that are similar,
> just not the exact same number you have.
>
> some subjects to look for:
> * Can't boot guest with more than 3585MB when using large pages
> There was a patch from Marcelo that was supposed to fix it.
> * kvm-84 and guests with more than 3536 MB Ram?
> there were suggestions to make sure to use the correct bios and the OP stated
> that upgrading his kernel actually fixed the problem
>
> I could swear there was another one, but maybe I'm thinking of the IRC
> channel. If you are still unable to get it to work, you should reply back with
> more info. Kernel version, KVM version, etc.
It could also be related to the guest trimming away memory due to the
way we used to report the MTRRs. This would show up in dmesg on the
guest. Try the latest kvm by hand and see if the problem goes away.
Thanks,
Alex
next prev parent reply other threads:[~2009-04-09 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:59 3525MB RAM Limit Daniel Scott
2009-04-07 3:46 ` Brian Jackson
2009-04-09 15:07 ` Daniel Scott
2009-04-09 15:39 ` Brian Jackson
2009-04-09 15:48 ` Alex Williamson [this message]
2009-04-09 18:54 ` Daniel Scott
2009-04-09 20:01 ` Sterling Windmill
[not found] ` <6835906b0904090849v24765218h4beea3780f55f8d3@mail.gmail.com>
[not found] ` <c779a6480904090925j70b635a0y810f65f19e92d707@mail.gmail.com>
2009-04-09 16:27 ` Mauricio Villarroel
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=1239292128.6184.152.camel@bling \
--to=alex.williamson@hp.com \
--cc=djscott@mit.edu \
--cc=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
/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