From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: I/O errors after migration - why? Date: Fri, 27 Mar 2009 17:51:18 +0100 Message-ID: <49CD0406.3030606@wpkg.org> References: <49CD0014.5020503@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: "kvm@vger.kernel.org" Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:60190 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757167AbZC0Qv0 (ORCPT ); Fri, 27 Mar 2009 12:51:26 -0400 Received: from localhost (filter1.syneticon.net [192.168.113.83]) by mx03.syneticon.net (Postfix) with ESMTP id C881E36145 for ; Fri, 27 Mar 2009 17:51:20 +0100 (CET) Received: from mx03.syneticon.net ([192.168.113.84]) by localhost (mx03.syneticon.net [192.168.113.83]) (amavisd-new, port 10025) with ESMTP id N+3n+fP6Nqy9 for ; Fri, 27 Mar 2009 17:51:19 +0100 (CET) Received: from [192.168.10.145] (koln-4db41662.pool.einsundeins.de [77.180.22.98]) by mx03.syneticon.net (Postfix) with ESMTPSA for ; Fri, 27 Mar 2009 17:51:19 +0100 (CET) In-Reply-To: <49CD0014.5020503@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski schrieb: > 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. 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. -- Tomasz Chmielewski http://wpkg.org