Bugs item #2942079, was opened at 2010-01-29 17:13 Message generated for change (Tracker Item Submitted) made by haoxudong You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2942079&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: Open Resolution: None Priority: 5 Private: No Submitted By: Xudong Hao (haoxudong) Assigned to: Nobody/Anonymous (nobody) Summary: [SR] qemu return form "migrate " command spend long time Initial Comment: Environment: ------------ kvm.git Commit: 51ef04ce3219d05c88f204342b2db294b5590d0a qemu-kvm Commit: 3e6f07b0c86b7fabfce72c1a42e54b2ad79dc587 Host Kernel Version: 2.6.33-rc4 Bug detailed description: -------------------------- KVM guest Save-Restore command changed, the new command function can work. However, when we do <migrate "exec:dd of=test.img"> in guest qemu console, it will cost much long time to return(~2 minutes of a 256M memory guest), the speed of saving only has ~1MB/s 344640+0 records in 344640+0 records out 176455680 bytes (176 MB) copied, 183.226 s, 963 kB/s Reproduce steps: ---------------- 1) qemu-system-x86_64 -m 256 -smp 4 -net nic,macaddr=00:16:3e:57:87:39,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/guest.img 2) Ctrl+Alt+2 migrate "exec:dd of=test.img" This step takes ~2 minutes with a 256MB memory guest, it will be more long for a >256MB memory guest. 3) qemu-system-x86_64 -m 256 -smp 4 -net nic,macaddr=00:16:3e:57:87:39,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/guest.img --incoming "exec:dd if=test.img" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2942079&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
