linux-kernel - Re: 2.6.25-rc5-git5 KVM memory not freed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Mar 2008 12:30:57 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Ioan Ionita <opslynx@...il.com>
CC:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.25-rc5-git5 KVM memory not freed

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/