Anthony Liguori schrieb:
(...)
Similar symptoms with virtio_blk (i.e., when guest is booted off a
live CD and tries to access the disk after migration).
The only difference between SCSI and virtio_blk is that SCSI signals
errors and aborts, and virtio_blk waits forever and doesn't give a
clue.
That is interesting (or not?).
In monitor, after migration, "info block" says:
scsi0-hd0: type=hd ...
Before migration, it was:
virtio0: type=hd ...
?
On both sides the guest was started with the same option (delta
"-incoming...").
Can you give the full command line on both ends and what KVM version it is?
kvm-84
/usr/bin/kvm -monitor unix:/var/run/qemu-server/117.mon,server,nowait
-vnc unix:/var/run/qemu-server/117.vnc,password -pidfile
/var/run/qemu-server/117.pid -daemonize -usbdevice tablet -name opennms1
-smp 1 -id 117 -cpuunits 1000 -vga cirrus -tdf -k de -drive
file=/var/lib/vz/template/iso/systemrescuecd-x86-1.1.7-beta3.iso,if=ide,index=2,media=cdrom
-drive
file=/dev/disk/by-path/ip-10.2.18.9:3260-iscsi-iqn.2009-03.net.syneticon:san3.opennms1-lun-1,if=scsi,index=0,boot=on
-m 400 -net
tap,vlan=6,ifname=vmtab117i6,script=/var/lib/qemu-server/bridge-vlan6
-net nic,vlan=6,model=e1000,macaddr=F6:13:A3:72:4D:9F -serial
unix:/var/run/qemu-server/117.serial,server,nowait -incoming tcp:0:4444
file=/dev/disk/by-path... is a symlink to a proper /dev/sdX device (i.e.
/dev/sdah on host1, /dev/sds on host2).
When checked with lsof, kvm process uses a proper /dev/sdX device on
both hosts.
--
Tomasz Chmielewski
http://wpkg.org
--
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
