public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Jackson <iggy@theiggy.com>
To: "Alberto Treviño" <alberto@byu.edu>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Live memory allocation?
Date: Sat, 28 Mar 2009 12:17:42 -0500	[thread overview]
Message-ID: <200903281217.43062.iggy@theiggy.com> (raw)
In-Reply-To: <200903280738.34169.alberto@byu.edu>

On Saturday 28 March 2009 08:38:33 Alberto Treviño wrote:
> On Thursday 26 March 2009 08:11:02 am Tomasz Chmielewski wrote:
> > Like, two guests, each with 2 GB memory allocated only use 1 GB of
> > host's memory (as long as they don't have many programs/buffers/cache)?
> >
> > So yes, it's also supported by KVM.
>
> The problem I've seen with this feature is that Windows guests end up
> taking all of their available memory once they are up and running.  For
> example, booting Windows XP in KVM 82 show a steady increase in memory. 
> Then about the time the login box is about to appear, memory usage jumps to
> the maximum allowed to the VM (512 MB in this case).  I remember reading
> somewhere Windows would try to initialize all memory during boot, causing
> KVM to allocate all memory.  VMware, however (and I don't know about
> VirtualBox) knows about this and works around it, making sure memory isn't
> all allocated during the Windows boot process.
>
> Would there a way to work around the Windows memory allocation issue in KVM
> as well?


KVM devs have a patch called KSM (short for kernel shared memory I think) that 
helps windows guests a good bit. See the original announcement [1] for some 
numbers. I spoke to one of the devs recently and they said they are going to 
resubmit it soon.


[1] http://marc.info/?l=kvm&m=122688851003046&w=2



> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-03-28 17:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:44 Live memory allocation? Evert
2009-03-26 14:01 ` Tomasz Chmielewski
2009-03-26 14:04   ` Izik Eidus
2009-03-26 14:11     ` Tomasz Chmielewski
2009-03-26 17:47       ` Evert
2009-03-28 13:38       ` Alberto Treviño
2009-03-28 17:17         ` Brian Jackson [this message]
2009-03-30 13:23           ` Alberto Treviño
2009-03-30 15:48             ` Brian Jackson
2009-03-28 18:25         ` Nolan
2009-03-29 12:33           ` Avi Kivity
2009-03-30 13:40             ` Tomasz Chmielewski
2009-03-30 13:48               ` Avi Kivity
2009-03-30 13:55                 ` Tomasz Chmielewski
2009-03-30 14:58                   ` Avi Kivity
2009-03-30 15:15                     ` Tomasz Chmielewski
2009-03-30 15:18                       ` Javier Guerra
2009-03-31  9:30                         ` Tomasz Chmielewski

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=200903281217.43062.iggy@theiggy.com \
    --to=iggy@theiggy.com \
    --cc=alberto@byu.edu \
    --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