Please ignore the 'Notes' in above comments and already tried the issue with following kernel&kvm on AMD host again.
-------------------------------------------------------------
kernel&kvm version
2.6.18-256.el5&kvm-83-231.el5
-------------------------------------------------------------
Additional,
1.Use iscsi and had better have the source and destination connect to a third-party server
2.create a lvm about 156M and begin migration at a time (please see attachment)
-log info
From source host-
/usr/libexec/qemu-kvm -rtc-td-hack -usbdevice tablet -no-hpet -drive file=/dev/migrate/deng1,if=virtio,boot=on,werror=stop,cache=none,format=qcow2,media=disk -cpu qemu64,+sse2 -smp 4 -m 4G -net nic,macaddr=00:12:24:57:a8:2e,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -uuid `uuidgen` -vnc :2 -boot dc -balloon none -monitor stdio -drive file=/opt/RHEL5.6-Server-20110106.0-x86_64-DVD.iso,if=ide,werror=stop,cache=none,format=raw,media=cdrom -notify all
QEMU 0.9.1 monitor - type 'help' for more information
(qemu)
(qemu)
(qemu)
(qemu) migrate -d tcp:10.66.9.101:1234
# VM is stopped due to disk write error: virtio0: Invalid argument
(qemu) migration_notify_done
info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
Min,
We did not fix it for 5.8, but now that I read it again. Line #5 in your description says that it does not exist in 5.7. If it is true, then we should have closed it already.
Well, looking at its duplicates, it seems to be relevant to 5.7 too.
Anyhow, we decided to close it for the following reasons:
1. Since we didn't make it for 5.8 dev-freeze and it doesn't look like a trivial fix, we gave up on 5.8.
2. Since there is no data corruption, we decided not to drag it further to 5.9