I'm trying to perform live migration by following the instructions on
http://www.linux-kvm.org/page/Migration.
Unfortunately, it doesn't work very well - guest is migrated, but looses
access to its disk.
On the destination host, I'm starting the guest with exactly the same
options as on the source host, with "-incoming tcp:0:4444".
On the source host, I start the migration with "migrate -d tcp:B:4444".
Both hosts use the same iSCSI device and can access it.
Looks like the destination host can't really access the iSCSI device
after all? No - after I reboot the guest (echo b > /proc/sysrq-trigger),
it boots just fine from its disk. Also lsof on the host shows that the
kvm process accesses the correct /dev/sdX device.
Both hosts use kvm-84.
This is what kernel says on the guest after migration:
sd 0:0:0:0: ABORT operation started.
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: ABORT operation started.
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: ABORT operation started.
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: ABORT operation started.
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: ABORT operation started.
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: DEVICE RESET operation started.
sd 0:0:0:0: DEVICE RESET operation timed-out.
sd 0:0:0:0: BUS RESET operation started.
sym0: suspicious SCSI data while resetting the BUS.
sym0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x0,
expecting 0x100
sd 0:0:0:0: BUS RESET operation timed-out.
sd 0:0:0:0: HOST RESET operation started.
sym0: suspicious SCSI data while resetting the BUS.
sym0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x0,
expecting 0x100
sym0: the chip cannot lock the frequency
sym0: SCSI BUS has been reset.
sd 0:0:0:0: HOST RESET operation timed-out.
sd 0:0:0:0: scsi: Device offlined - not ready after error recovery
(...)
Buffer I/O error on device sda1, logical block 1
lost page write due to I/O error on sda1
sd 0:0:0:0: rejecting I/O to offline device
--
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
