All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Nolan <nolan@sigbus.net>
Cc: kvm@vger.kernel.org
Subject: Re: I/O errors after migration - why?
Date: Sat, 28 Mar 2009 11:21:33 +0100	[thread overview]
Message-ID: <49CDFA2D.9000300@wpkg.org> (raw)
In-Reply-To: <loom.20090328T010502-399@post.gmane.org>

Nolan schrieb:
> Tomasz Chmielewski <mangoo <at> wpkg.org> writes:
>> 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.
> 
> The LSI logic scsi device model doesn't implement device state save/restore. 
> Any suspend/resume, snapshot or migration will fail.

Oh, that sucks - as not everything supports virtio (which doesn't work 
for me as well for some reason) - like Windows (which should be 
addressed soon with block virtio drivers), but also older installations, 
running older kernels.
Does IDE support migration?


> I sent a patch that partially addresses this (but is buggy in the presence of
> in-flight IO):
> http://lists.gnu.org/archive/html/qemu-devel/2009-01/msg00744.html


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2009-03-28 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 16:34 I/O errors after migration - why? Tomasz Chmielewski
2009-03-27 16:51 ` 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 [this message]
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=49CDFA2D.9000300@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=kvm@vger.kernel.org \
    --cc=nolan@sigbus.net \
    /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.