Bugs item #2776577, was opened at 2009-04-20 13:23 Message generated for change (Comment added) made by tljohnsn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2776577&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Trent Johnson (tljohnsn) Assigned to: Nobody/Anonymous (nobody) Summary: Call trace after live migration of 32 bit guest under load Initial Comment: CPU: model name : Intel(R) Xeon(R) CPU L5335 @ 2.00GHz Host is running centos 5.3 2.6.18-128.1.6.el5 kvm-84 Guest is running 32 bit centos 4.7 kernel 2.6.9-78.0.13.ELsmp Start guest with: qemu-kvm -M pc -m 512 -smp 1 -name c4test -uuid ace28629-2d19-89aa-036b-bea6f46a4909 -monitor pty -pidfile /var/run/libvirt/qemu//c4test.pid -boot c -drive file=/makersvm/c4test.img,if=ide,index=0,boot=on -net nic,macaddr=54:52:00:16:1b:76,vlan=0 -net tap,script=/etc/kvm/qemu-ifup,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -vnc 0.0.0.0:1 -k en-us Start building a kernel on the guest - then: migrate tcp:dest.example.com:4444 It fails with the attached log messages, however the guest can be continued on the source host. Save and resume work fine if I copy the state file manually. The problem does not go away with -no-kvm-irqchip or -no-kvm-pit switch. The problem does not happen with the -no-kvm switch. Thanks, Trent ---------------------------------------------------------------------- >Comment By: Trent Johnson (tljohnsn) Date: 2009-04-21 14:28 Message: I am no longer having the problem after updating to kvm-85 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2776577&group_id=180599 -- 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
