From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RAM overcomittment
Date: Wed, 27 Sep 2006 23:21:42 +0100 [thread overview]
Message-ID: <200609272321.43534.paul@codesourcery.com> (raw)
In-Reply-To: <FBE19388-C29F-4DB3-AEDB-6CC38186FA5F@gmail.com>
> > However, swapping (using virtual memory) will be a huge performance
> > killer. It will affect the performance of your host OS and all
> > applications, as well as for your QEMU instances.
>
> The problem is the swaping even the VM don't need all of ressource
> assigned... We lost RAM...
You need to fix your host OS then. If the guest isn't using the memory it
shouldn't be swapped in.
Paul
prev parent reply other threads:[~2006-09-27 22:21 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 ` [Qemu-devel] RAM overcomittment andrzej zaborowski
2006-09-28 14:45 ` 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 [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=200609272321.43534.paul@codesourcery.com \
--to=paul@codesourcery.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).