From: Stefan Hajnoczi <stefanha@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Bug 1396052 <1396052@bugs.launchpad.net>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
aik@ozlabs.ru
Subject: Re: [Qemu-devel] [Bug 1396052] [NEW] migration failed when running BurnInTest in guest
Date: Tue, 2 Dec 2014 15:10:54 +0000 [thread overview]
Message-ID: <20141202151054.GC12390@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20141127092059.GB3899@grmbl.mre>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Thu, Nov 27, 2014 at 02:50:59PM +0530, Amit Shah wrote:
> On (Tue) 25 Nov 2014 [09:32:58], z08687 wrote:
> > Public bug reported:
> >
> > Hi,
> > I found a live migration problem and have found out the reason, but I can't fix it up myself. I really need help.
> > When live migration vm and it's block device in save time, it will occur probabilistic .
> >
> > Step:
> > 1. start a windows vm,and run burnInTest(it will write dirty data to block device in migration)
> > 2. migrate vm with it's block device.
> > 3. a few minutes later, dest vm was killed and migration will be failed (probabilistic )
>
> That's a nice test case, as well as good analysis.
This is a known issue:
https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg02959.html
Please try this patch:
commit 7ea2d269cb84ca7a2f4b7c3735634176f7c1dc35
Author: Alexey Kardashevskiy <aik@ozlabs.ru>
Date: Thu Oct 9 13:50:46 2014 +1100
block/migration: Disable cache invalidate for incoming migration
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-02 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 9:32 [Qemu-devel] [Bug 1396052] [NEW] migration failed when running BurnInTest in guest z08687
2014-11-27 9:20 ` Amit Shah
2014-12-02 15:10 ` Stefan Hajnoczi [this message]
2014-12-12 9:38 ` [Qemu-devel] [Bug 1396052] " z08687
2018-05-22 13:39 ` Thomas Huth
2018-05-26 13:35 ` z08687
2018-05-27 12:02 ` Thomas Huth
2018-05-29 7:19 ` Kevin Wolf
2018-05-30 11:27 ` z08687
2021-05-03 16:11 ` Thomas Huth
2021-07-03 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=20141202151054.GC12390@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=1396052@bugs.launchpad.net \
--cc=aik@ozlabs.ru \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).