From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: I/O errors after migration - why?
Date: Fri, 27 Mar 2009 17:34:28 +0100 [thread overview]
Message-ID: <49CD0014.5020503@wpkg.org> (raw)
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
next reply other threads:[~2009-03-27 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 16:34 Tomasz Chmielewski [this message]
2009-03-27 16:51 ` I/O errors after migration - why? Tomasz Chmielewski
2009-03-27 17:01 ` Tomasz Chmielewski
2009-03-27 17:14 ` Tomasz Chmielewski
2009-03-27 17:33 ` Anthony Liguori
2009-03-27 18:43 ` Tomasz Chmielewski
2009-03-28 1:08 ` Nolan
2009-03-28 10:21 ` Tomasz Chmielewski
2009-03-28 18:15 ` Nolan
2009-03-30 5:38 ` Takeshi Sone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CD0014.5020503@wpkg.org \
--to=mangoo@wpkg.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.