public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Ioan Ionita <opslynx@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc5-git5 KVM memory not freed
Date: Sun, 23 Mar 2008 12:30:57 +0200	[thread overview]
Message-ID: <47E63161.90002@qumranet.com> (raw)
In-Reply-To: <df47b87a0803200941q7cbee10ev5a57f7cb25406896@mail.gmail.com>

Ioan Ionita wrote:
> Hi,
>
> I'm using KVM and the qemu kvm modified to run a windows guest. I'm
> allocating 900 MB to the guest. Seems that when I terminate a qemu
> process, the memory that was allocated to qemu is not freed:
>
>
> Mem:       2058140    1739156     318984          0     226944     425140
> -/+ buffers/cache:    1087072     971068
> Swap:            0          0          0
>
> So I'm using 1GB of ram even though I've terminated qemu. If I attempt
> to start qemu again, the machine locks up. No message in the logs.
>
> Command to start qemu:
> /usr/local/kvm/bin/qemu-system-x86_64 b.data -no-acpi -m 900 -net nic
> -net user -hdb temp.raw -usbdevice tablet
>
> uname -a
> Linux ops-desktop 2.6.25-rc5-git5 #1 SMP PREEMPT Sat Mar 15 14:47:25
> EET 2008 x86_64 GNU/Linux
>
>
> Not sure whether this is a problem on the kernel side.  I don't
> pretend to understand linux memory management. But it wasn't occurring
> with older kernels. I'll attempt to bisect.
>   

I reproduced this and am investigating.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-03-23 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 16:41 2.6.25-rc5-git5 KVM memory not freed Ioan Ionita
2008-03-23 10:30 ` Avi Kivity [this message]
2008-03-23 12:20   ` Avi Kivity
2008-03-24 23:30     ` Ioan Ionita
2008-03-25  6:21       ` Avi Kivity

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=47E63161.90002@qumranet.com \
    --to=avi@qumranet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opslynx@gmail.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