All of lore.kernel.org
 help / color / mirror / Atom feed
From: pranith <1681688@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1681688] Re: qemu live migration failed
Date: Tue, 18 Apr 2017 19:42:45 -0000	[thread overview]
Message-ID: <20170418194245.17360.81760.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20170411080154.12474.20009.malonedeb@gac.canonical.com

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1681688

Title:
  qemu live migration failed

Status in QEMU:
  Incomplete

Bug description:
  qemu live migration failed

  the dest qemu report this error.

  Receiving block device images
  Completed 0 %^Mqemu-system-x86_64: block/io.c:1348: bdrv_aligned_pwritev: Assertion `child->perm & BLK_PERM_WRITE' failed.

  this bug is caused by this patch:
  http://git.qemu-project.org/?p=qemu.git;a=commit;h=d35ff5e6b3aa3a706b0aa3bcf11400fac945b67a

  rollback this commit, the problem solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1681688/+subscriptions

  parent reply	other threads:[~2017-04-18 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  8:01 [Qemu-devel] [Bug 1681688] [NEW] qemu live migration failed Lidong Chen
2017-04-11  8:21 ` [Qemu-devel] [Bug 1681688] " Lidong Chen
2017-04-11 13:35   ` 858585 jemmy
2017-04-11 13:57     ` Kevin Wolf
2017-04-11 14:00       ` Laurent Vivier
2017-04-11 14:05       ` Laurent Vivier
2017-04-18 19:42 ` pranith [this message]
2017-04-18 20:10 ` pranith
2020-11-17 11:52 ` Thomas Huth
2021-01-17  4:17 ` Launchpad Bug Tracker

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=20170418194245.17360.81760.launchpad@gac.canonical.com \
    --to=1681688@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.