Hello,
We're using qemu-kvm on Debian 6 for a VM farm (currently 16 hosts), on HP
blade hardware. We're experiencing issues on our Debian 5 and 6 guests
after we migrate them between hosts. This issue does not occur with the
qemu-kvm binary version 0.14.1 (compiled from source), but does occur with
any release after it (from 0.15.0-rc1 all the way to 1.1.0).
The issue is that after a live migration, the guest runs and and responds
to network traffic, terminal sessions are unresponsive when I run "top".
So basically:
1. start guest on vmA; everything fine
2. migrate guest via libvirt to vmB; everything fine, top works
3. migrate guest back to vmA; run top, it hangs
4. migrate to vmB; top works again
This problem occurs with 0.15, 1.0, and 1.1, but not with 0.14.1 (or
anything earlier). The problem occurs whether I try to run 'top' via an
SSH session, or via the (VNC) console. This also appears to mess up
shutdowns/reboots, as the init scripts want to print stuff to the console
and can't
The guest kernel version does not seem to matter, and neither does the
host OS kernel. Currently I'm testing with Debian kernel 3.2.20-1~bpo60+1,
which is just about the newest you can get from squeeze-backports, but
we've experienced the issue on the regular squeeze 2.6.32 kernels as well
for the guests, and the 2.6.39 kernels as well (hosts).
The command-line arguments that "qemu-system-x86_64" is using is (wrapped
for cleanliness attempted):
/srv/mcvmm/qemu-kvm-0.14.1/bin/qemu-system-x86_64 -S -M pc-0.12
-enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1
-name dm-logging -uuid 1e8c52a3-d966-1b37-3f69-10c12383c929
-nodefconfig -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/dm-logging.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive
file=/srv/vmimages/images4/systems/dm-logging_prealloc.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21
-device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:01:00:00:a5,bus=pci.0,addr=0x3,bootindex=2
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0
-device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus
-incoming tcp:0.0.0.0:49159
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
--
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
