From: Kashyap Chamarthy <kchamart@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
peter.maydell@linaro.org, famz@redhat.com, lirans@il.ibm.com,
qemu-block@nongnu.org, quintela@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com, stefanha@redhat.com,
den@openvz.org, amit.shah@redhat.com, pbonzini@redhat.com,
mreitz@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/4] qmp-cont: invalidate on RUN_STATE_PRELAUNCH
Date: Wed, 26 Apr 2017 14:22:46 +0200 [thread overview]
Message-ID: <20170426122246.v2px6y33k4dpiiqb@eukaryote> (raw)
In-Reply-To: <ec621d28-d6bd-a125-fa1c-5e9a09b04c22@virtuozzo.com>
On Tue, Mar 07, 2017 at 01:11:23PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 07.03.2017 13:02, Kevin Wolf wrote:
> > Am 25.02.2017 um 20:31 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > > We must invalidate on RUN_STATE_PRELAUNCH too, as it is available
> > > through qmp_system_reset from RUN_STATE_POSTMIGRATE. Otherwise, we will
> > > come to
> > >
> > > qemu-kvm: block/io.c:1406: bdrv_co_do_pwritev:
> > > Assertion `!(bs->open_flags & 0x0800)' failed.
> > >
> > > on the first write after vm start.
> > >
> > > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> > Wouldn't it make more sense to invalidate in qmp_system_reset() where
> > the migration states are left?
> >
> > Or maybe BDRV_O_INACTIVE could even be tied directly to runstates? Not
> > sure how realistic this one is, but if we start adding invalidate_cache
> > calls all over the place, maybe that's a sign that we need to look for a
> > more central place.
>
> I've proposed it in cover letter) These bugs and my fixes are just show that
> something should be rethought.. I don't claim that these fixes are true way,
> they are just the simplest.
Hi Vladimir,
I wonder if you have a new version of your patch ("qmp-cont: invalidate
on RUN_STATE_PRELAUNCH").
Hailiang Zhang tells me on this the below thread that your patch fixes
the issue:
http://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg03925.html
-- [QEMU-2.8] Source QEMU crashes with: "bdrv_co_pwritev: Assertion
`!(bs->open_flags & BDRV_O_INACTIVE)' failed"
--
/kashyap
next prev parent reply other threads:[~2017-04-26 12:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 19:31 [Qemu-devel] [PATCH 0/4] some migration bugs Vladimir Sementsov-Ogievskiy
2017-02-25 19:31 ` [Qemu-devel] [PATCH 1/4] iotests: add migration corner cases test Vladimir Sementsov-Ogievskiy
2017-03-07 9:14 ` Fam Zheng
2017-03-07 11:23 ` Dr. David Alan Gilbert
2017-02-25 19:31 ` [Qemu-devel] [PATCH 2/4] qmp-cont: invalidate on RUN_STATE_PRELAUNCH Vladimir Sementsov-Ogievskiy
2017-03-07 9:19 ` Fam Zheng
2017-03-07 10:02 ` Kevin Wolf
2017-03-07 10:11 ` Vladimir Sementsov-Ogievskiy
2017-03-07 10:22 ` Kevin Wolf
2017-04-26 12:22 ` Kashyap Chamarthy [this message]
2017-04-26 13:43 ` [Qemu-devel] [Qemu-block] " Vladimir Sementsov-Ogievskiy
2017-02-25 19:31 ` [Qemu-devel] [PATCH 3/4] savevm: fix savevm after migration Vladimir Sementsov-Ogievskiy
2017-02-27 9:42 ` Denis V. Lunev
2017-03-07 9:53 ` Kevin Wolf
2017-03-07 9:59 ` Vladimir Sementsov-Ogievskiy
2017-03-07 11:01 ` Kevin Wolf
2017-03-07 11:20 ` Dr. David Alan Gilbert
2017-03-28 10:55 ` Dr. David Alan Gilbert
2017-03-28 11:09 ` Kevin Wolf
2017-03-28 11:13 ` Dr. David Alan Gilbert
2017-03-28 12:09 ` Kevin Wolf
2017-03-28 13:16 ` Vladimir Sementsov-Ogievskiy
2017-03-28 14:15 ` Paolo Bonzini
2017-03-29 15:29 ` Dr. David Alan Gilbert
2017-03-29 15:53 ` Paolo Bonzini
2017-04-25 14:22 ` [Qemu-devel] ping " Vladimir Sementsov-Ogievskiy
2017-03-28 11:18 ` [Qemu-devel] " Denis V. Lunev
2017-02-25 19:31 ` [Qemu-devel] [PATCH 4/4] migration: fix use-after-free of to_dst_file Vladimir Sementsov-Ogievskiy
2017-02-27 10:44 ` Dr. David Alan Gilbert
2017-02-28 9:59 ` Dr. David Alan Gilbert
2017-03-06 14:23 ` [Qemu-devel] [PATCH 0/4] some migration bugs Denis V. Lunev
2017-03-20 9:44 ` [Qemu-devel] ping " Vladimir Sementsov-Ogievskiy
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=20170426122246.v2px6y33k4dpiiqb@eukaryote \
--to=kchamart@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=lirans@il.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).