It does seem to be related to the guest, because with a dummy (non-
bootable, garbage data) disk image, the rapid memory leak does not
occur.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1288620
Tit
On Wed, 23 Apr 2014 13:10:39 -, Stefan Hajnoczi wrote:
> So this is a problem that only happens under Valgrind? Perhaps this
> is
> a valgrind bug.
No, it happens outside of Valgrind as well. It only happens when QEMU
is told to read a config file (with -readconfig).
--
You received this
Attaching config file mentioned in previous comment.
** Attachment added: "windows8_throwaway_VM.conf"
https://bugs.launchpad.net/qemu/+bug/1288620/+attachment/4049965/+files/windows8_throwaway_VM.conf
** Summary changed:
- memory leak with default NIC model
+ memory leak with config file
*
I have been able to consistently reproduce the bug again, and have run
QEMU with Valgrind until OOM. It is unrelated to networking; it is
caused by loading a config file.
I ran QEMU from Git commit 7f6613cedc59fa849105668ae971dc31004bca1c
under valgrind via...
valgrind qemu-system-x86_64 -readco
Even after rebooting with the kernel I was using when I had the problem
behaviour in QEMU, I can not reproduce the issue. It certainly was not
a one-off, because QEMU was gobbling memory consistently on my system,
in consecutive sessions.
--
You received this bug notification because you are a m
I can not reproduce this even with the Ubuntu package after rebooting
after a kernel update. I will try again with the previous kernel image
to confirm this is the relevant variable. Is it possible that the
behaviour I described in the initial report is/was caused by code in the
KVM module?
--
Public bug reported:
I have a Windows 7 SP1 Professional 64-bit installation on a QCOW2 image
with compat=1.1, which I launch via
qemu-system-x86_64 -drive file=windows_base_HDD.img,index=0,media=disk
-enable-kvm -m 512M -vga std -net nic,vlan=0 -net user,vlan=0
As soon as I start using the netw
