On 10/29/2009 02:21 PM, Avi Kivity wrote:
On 10/28/2009 06:46 PM, Michael S. Tsirkin wrote:
On Tue, Oct 27, 2009 at 09:36:18AM -0700, Shirley Ma wrote:
Hello Michael,
On Tue, 2009-10-27 at 17:27 +0200, Michael S. Tsirkin wrote:
Possibly GFP_ATOMIC allocations in vring_add_indirect are failing?
Is there a chance you are tight on guest memory for some reason?
with vhost, virtio does currently consume a bit more memory than
with userspace backend.
I did see memory leak on host every time after exiting guest. I don't
know where. Do you see it?
I don't see a leak specific to vhost. However, even without vhost,
starting up guest increases kmalloc-128 counter in /proc/slabinfo
and this fails to go down when qemu is killed.
Anyone else seeing this?
I'm seeing it, but starting a new guest seems to reclaim this memory.
I'll enable debug and see what's the cause.
kmemleak doesn't see any kvm memory leaks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
