public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>
Subject: migration fails with virtio-blk
Date: Mon, 10 May 2010 13:49:09 +0400	[thread overview]
Message-ID: <4BE7D695.9020002@msgid.tls.msk.ru> (raw)

Apparently there's an issue with migration when
virtio-blk is in use at the time migration occurs.

See Debian bug #580649 for details:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649

In short: 2.6.26 (guest) + 0.12.3 + virtio-blk fails.
2.6.32 guest works, 0.11 works, non-virtio-blk works.

Debian qemu-kvm is compiled without --enable-iothread -
JFYI.

The bugreport contains a backtrace taken from guest.

Now, one can say it's a bug in 2.6.26 kernel, which
is quite old.  But the problem does not occur with
qemu-kvm-0.11, so it might be treated as a regression
instead.

Thanks!

/mjt


             reply	other threads:[~2010-05-10  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10  9:49 Michael Tokarev [this message]
2010-05-10 18:34 ` migration fails with virtio-blk Michael Tokarev
2010-05-10 18:38   ` Anthony Liguori
2010-05-10 18:57     ` Michael Tokarev

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=4BE7D695.9020002@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox