Tomasz Chmielewski <mangoo <at> wpkg.org> writes: > > Gerrit Slomma schrieb: > > Hello and good day. > > > > I have filed a bug report via bugzilla.redhat.com with the id > > With what ID? > > Could you give the full URL? > Sorry, my fault. Full URL is: https://bugzilla.redhat.com/show_bug.cgi?id=492688 Problem is described there but for the lazy i copy-paste it here: Virtual machine gets stuck after migration. One CPU is 100% load, other one idles. The virtual machine could be pinged, ssh-login is not always possible. If stopped on migration target and continued on migration-source the virtual machine recovers after some time without load. Version-Release number of selected component (if applicable): kvm-84-1.el5.x86_64.rpm kvm-kmod-84-1.el5.x86_64.rpm qemu-0.9.1-11.el5.x86_64.rpm qemu-img-0.9.1-11.el5.x86_64.rpm kvm and kvm-kmod compiled from sourceforge sources and installed from built rpm, qemu and qemu-img are from EPEL-repository How reproducible: Start a kvm-virtual-machine on host A, start a kvm-virtual-machine with the same parameters on host B in incoming-Mode. Migrate the virtual-machine from host A to host B. Watch the kvm-process go to 100% after migration finishs. Maybe you have to wait up to 5 seconds or apply a ls or such in the virtual machine. After stopping virtual machine on host B and continuing virtual machine on host A the virtual machine recovers -- 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
