qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RAM overcomittment
Date: Thu, 28 Sep 2006 00:36:51 +0200	[thread overview]
Message-ID: <fb249edb0609271536n6b7c74aena9a52723811c017d@mail.gmail.com> (raw)
In-Reply-To: <A132AD5E-984E-432A-BBC4-1D7EE4B34529@gmail.com>

Hi,

On 27/09/06, The MoonSeeker <themoonseeker@gmail.com> wrote:
> Ok but some virtual solution like openVZ allow you run more VM than the
> memory installed. By example, with openVZ I can create 10 Virtual Machine
> who have a limite fixe to 200 MB but have guaranteed RAM of 20MB. With qemu
> I need to have 10 X 200MB for VM's + 128 MB host of RAM installed on the
> work station...
>
> I think we can Save ressource because in the most case, the VM's will never
> use the 200MB. I think it will be a nice if qemu implemented a tool that let
> use exceed this limitation.

How would you implement that?

>
> I can show you an application domain :
>
> For my diploma project, I have to create a network simulator but with these
> limitation I can't use qemu. Because if would like to simulate 20 workstions
> I need 20 X 128 MB = 2560 MB of RAM... + host RAM!!! But in the simulation,
> the VM's never will use all of ressource..

Then give the VMs only as much as they will use (note that VMs can
also have swap) or use host swap.

Regards,
-- 
balrog 2oo6

  parent reply	other threads:[~2006-09-27 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 21:31 [Qemu-devel] RAM overcomittment The MoonSeeker
2006-09-27 21:41 ` Paul Brook
2006-09-27 21:59   ` The MoonSeeker
2006-09-27 22:19     ` Paul Brook
2006-09-27 22:53       ` The MoonSeeker
2006-09-27 22:58         ` Paul Brook
2006-09-27 23:12           ` [Qemu-devel] PowerPC Decrementer Clock Rate Ely Soto
2006-09-27 22:36     ` andrzej zaborowski [this message]
2006-09-28 14:45     ` [Qemu-devel] RAM overcomittment James Oakley
2006-09-28 22:29       ` Bill C. Riemers
2006-09-27 21:57 ` James Olsen
2006-09-27 22:16   ` The MoonSeeker
2006-09-27 22:21     ` Paul Brook

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=fb249edb0609271536n6b7c74aena9a52723811c017d@mail.gmail.com \
    --to=balrog@zabor.org \
    --cc=balrogg@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).