From: Peter Lieven <pl@kamp.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Qemu and heavily increased RSS usage
Date: Tue, 21 Jun 2016 10:21:55 +0200 [thread overview]
Message-ID: <5768F923.7040502@kamp.de> (raw)
Hi,
while upgrading from Qemu 2.2.0 to Qemu 2.5.1.1 I noticed that the RSS memory usage has heavily increased.
We use hugepages so the RSS memory does not include VM memory. In Qemu 2.2.0 it used to be ~30MB per vServer
and increased to up to 300 - 400MB for Qemu 2.5.1.1 (same with master). The memory increases over time, but seems
not to grow indefinetly. I tried to bisect, but had no result so far that made sense. I also tried valgrind / massif, but
valgrind does not see the allocation (at least at exit) and massif fails to rund due to - so it pretends - heap corruption.
Any help or ideas how to debug further would be appreciated.
Cmdline is:
./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -M pc-i440fx-2.1 -nodefaults -netdev type=tap,id=guest3,script=no,downscript=no,ifname=tap0,vnet_hdr -device virtio-net-pci,netdev=guest3,mac=52:54:00:ff:08:5e -iscsi
initiator-name=iqn.2005-03.org.xx:0025b5d0011f -drive format=raw,discard=on,file=iscsi://172.21.200.56/iqn.2001-05.com.equallogic:0-8a0906-98f384e0a-7d2004ee0a85767a-00lieven-test/0,if=none,cache=writeback,aio=native,id=disk0 -object iothread,id=iothread0
-device virtio-blk-pci,drive=disk0,iothread=iothread0 -global virtio-blk-pci.scsi=off -serial null -parallel null -m 4096 -smp 4,sockets=1,cores=4,threads=1 -monitor tcp:0:4004,server,nowait,nodelay -qmp tcp:0:3004,server,nowait,nodelay -name lieven-test
-boot order=c,once=dc,menu=off -k de -mem-path /hugepages -mem-prealloc -cpu Westmere,enforce -rtc base=utc -usb -usbdevice tablet -no-hpet -vga vmware
Thanks,
Peter
next reply other threads:[~2016-06-21 8:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 8:21 Peter Lieven [this message]
2016-06-21 13:18 ` [Qemu-devel] Qemu and heavily increased RSS usage Dr. David Alan Gilbert
2016-06-21 15:12 ` Peter Lieven
2016-06-22 10:56 ` Stefan Hajnoczi
2016-06-22 19:55 ` Peter Lieven
2016-06-22 20:56 ` Peter Maydell
2016-06-24 9:37 ` Stefan Hajnoczi
2016-06-24 9:53 ` Peter Lieven
2016-06-24 9:57 ` Dr. David Alan Gilbert
2016-06-24 9:58 ` Peter Maydell
2016-06-24 10:45 ` Peter Lieven
2016-06-27 12:39 ` Stefan Hajnoczi
2016-06-27 13:33 ` Peter Lieven
2016-06-23 9:57 ` Peter Lieven
2016-06-24 22:57 ` Michael S. Tsirkin
2016-06-23 14:58 ` Peter Lieven
2016-06-23 15:00 ` Dr. David Alan Gilbert
2016-06-23 15:02 ` Peter Lieven
2016-06-23 15:21 ` Paolo Bonzini
2016-06-23 15:31 ` Peter Lieven
2016-06-23 15:47 ` Paolo Bonzini
2016-06-23 16:19 ` Peter Lieven
2016-06-23 16:53 ` Paolo Bonzini
2016-06-23 21:28 ` Peter Lieven
2016-06-24 4:10 ` Paolo Bonzini
2016-06-24 8:11 ` Peter Lieven
2016-06-24 8:20 ` Paolo Bonzini
2016-06-24 8:45 ` Peter Lieven
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=5768F923.7040502@kamp.de \
--to=pl@kamp.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.