Are there still known memory leaks in the virtio block and/or net drivers? If not, have we found one? This is our host setup: - Tyan h2000M motherboard - 2x dual-core AMD Opteron 2220 CPUs - 16 GB RAM - quad-port NIC bonded together into 1 kvmbr0 interface - 3Ware 9550SXU-12ML RAID controller - 12x 400 GB SATA drives (4-disk RAID5, 4-disk RAID5, 3-disk RAID5, spare disk) - LVM used to stitch the 3 arrays into one volume group Running 64-bit Debian 5.0 (Lenny), using qemu-kvm0.12.4 and kernel 2.6.32 from lenny-backports. Guests are Ubuntu Server 8.04 LTS, Debian Lenny, Windows XP, and Windows 2003. All of the Linux VMs use virtio for both network and disk. All the Windows VMs use virtio for network and IDE emulation for disk. Within 2 weeks of booting, the host machine is using 2 GB of swap, and disk I/O wait is through the roof. Restarting all of the VMs will free up RAM, but restarting the whole box is the only way to get performance back up. A guest configured to use 8 GB of RAM will have 9 GB virt and 7.5 GB res shown in top. In fact, every single VM shows virt above the limit set for the VM. Usually by close to 25%. Going back through the mailing list archives and bug archives, there's been mention of several memory leaks in the virtio drivers back to KVM-72. Last bug report I read shows them all being fixed in 0.12.4, which we're running. Perhaps there's something wrong with our setup? Perhaps there's still a leak to be found? Perhaps this is fixed in 0.12.5 or newer? Open to suggetions. Sample KVM command-line: /usr/bin/kvm -name riker -smp 1 -m 1024 -vnc :5 -daemonize -localtime -usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:5,model=virtio -net tap,ifname=tap5 -pidfile /var/run/kvm/riker.pid -boot c -drive index=0,media=disk,if=virtio,boot=on,file=/dev/mapper/vol0-riker -drive index=1,media=disk,if=virtio,file=/dev/mapper/vol0-riker--var We're in the process of migrating from our custom scripts (kvmctl) to libvirt, if that makes any difference. -- Freddie Cash fjwcash@xxxxxxxxx -- 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
