From: Daniel Bareiro <dbareiro@uol.com.ar>
To: Rik van Riel <riel@redhat.com>
Cc: dbareiro@gmx.net, KVM General <kvm@vger.kernel.org>,
"hugh.dickins@tiscali.co.uk" <hugh.dickins@tiscali.co.uk>
Subject: Re: Swap usage with KVM
Date: Mon, 2 Aug 2010 16:52:57 -0300 [thread overview]
Message-ID: <20100802195257.GL21963@defiant.freesoftware> (raw)
In-Reply-To: <4C571D23.3040802@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]
Hi, Rik.
On Monday, 02 August 2010 15:31:47 -0400,
Rik van Riel wrote:
>>>>> I have an installation with Debian GNU/Linux 5.0.4 amd64 with
>>>>> qemu-kvm 0.12.3 compiled with the source code obtained from the
>>>>> official site of KVM and Linux 2.6.32.12 compiled from source code
>>>>> of kernel.org. All this is installed on an HP Proliant DL380 G6
>>>>> with two Xeon E5530 quadcore processors and 16 GiB of RAM which
>>>>> has two VMs with the following configuration of memory:
>>>>>
>>>>> Hostname | RAM
>>>>> ===============+===============
>>>>> Aps4 | 7 GiB
>>>>> Leela | 7 GiB
>>>>> ===============+===============
>>>>> TOTAL | 14 GiB
>>>>>
>>>>> Initially the host was created with a swap partition of 1 GiB, but
>>>>> today we found that the use of swap quickly began to grow
>>>>> increasingly. Therefore, as a contingency, we had to hot-add a
>>>>> logical volume of 1 GB of swap on the VMHost. Is 'normal' this use
>>>>> of memory?
>>> That depends on what is going on in the host.
>>>
>>> Did you notice any performance issues in the guest when you started
>>> using swap?
>> After the logical volume of 1 GB that I added when I found this
>> problem (being the operating system with 2 GB), I added other 3 GB to
>> have a little more margin, but today I got again a new alert of
>> Nagios:
>>
>>
>> Swap usage WARNING [...] SWAP WARNING - 30% free (1490 MB out of 5052 MB)
>>
>>
>> I don't see performance issue in the VMs.
>>
>> Marcelo Tosatti recommended me to apply the EPT patch
>> (6316e1c8c6af6ccb55ff8564231710660608f46c). Should it be safe for use in
>> production? Are there plans that this patch is applied on some version
>> of Linux stable?
> Yes, that patch is safe and definitely recommended.
Perfect. Thanks for so fast answer.
And there are some estimates of when this patch is in Linux stable?
Regards,
Daniel
--
Mi frase del día:
BOFH excuse #281:
The co-locator cannot verify the frame-relay gateway to the ISDN server.
Daniel Bareiro - GNU/Linux registered user #188.598
Proudly running Debian GNU/Linux with uptime:
16:44:53 up 23 days, 21:37, 11 users, load average: 0.02, 0.06, 0.08
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-08-02 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 15:12 Swap usage with KVM Daniel Bareiro
2010-07-11 19:12 ` Daniel Bareiro
2010-07-11 21:49 ` Rik van Riel
2010-08-02 18:57 ` Daniel Bareiro
2010-08-02 19:31 ` Rik van Riel
2010-08-02 19:52 ` Daniel Bareiro [this message]
2010-08-02 20:22 ` Rik van Riel
2010-08-02 21:43 ` Daniel Bareiro
2010-08-27 10:04 ` Swap usage with KVM (and KSM) Daniel Bareiro
2010-08-27 13:42 ` Rik van Riel
2010-07-11 21:05 ` Swap usage with KVM Freddie Cash
2010-07-11 22:08 ` Daniel Bareiro
2010-07-20 15:04 ` Daniel Bareiro
2010-07-20 19:18 ` David Weber
2010-07-22 10:09 ` Daniel Bareiro
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=20100802195257.GL21963@defiant.freesoftware \
--to=dbareiro@uol.com.ar \
--cc=dbareiro@gmx.net \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kvm@vger.kernel.org \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox