From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: amit.shah@redhat.com, qemu-stable@nongnu.org,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL 1/3] Migration: Generate the completed event only when we complete
Date: Thu, 15 Oct 2015 17:12:25 +0100 [thread overview]
Message-ID: <20151015161224.GD2598@work-vm> (raw)
In-Reply-To: <561FC11E.1000206@de.ibm.com>
* Christian Borntraeger (borntraeger@de.ibm.com) wrote:
> Am 15.10.2015 um 08:27 schrieb Juan Quintela:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > The current migration-completed event is generated a bit too early,
> > which means that an eager libvirt that's ready to go as soon
> > as it sees the event ends up racing with the actual end of migration.
> >
> > This corresponds to RH bug:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1271145
>
> Is that something for stable?
Hmm, yes, it probably should be.
cc'd in.
Dave
>
>
> >
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > Reviewed-by: Juan Quintela <quintela@redhat.com>
> > Reviewed-by: Amit Shah <amit.shah@redhat.com>
> > xSigned-off-by: Juan Quintela <quintela@redhat.com>
>
>
> > ---
> > migration/migration.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/migration/migration.c b/migration/migration.c
> > index b7de9b7..3d40f24 100644
> > --- a/migration/migration.c
> > +++ b/migration/migration.c
> > @@ -294,12 +294,12 @@ static void process_incoming_migration_co(void *opaque)
> > migrate_decompress_threads_join();
> > exit(EXIT_FAILURE);
> > }
> > - migrate_generate_event(MIGRATION_STATUS_COMPLETED);
> > qemu_announce_self();
> >
> > /* Make sure all file formats flush their mutable metadata */
> > bdrv_invalidate_cache_all(&local_err);
> > if (local_err) {
> > + migrate_generate_event(MIGRATION_STATUS_FAILED);
> > error_report_err(local_err);
> > migrate_decompress_threads_join();
> > exit(EXIT_FAILURE);
> > @@ -320,6 +320,12 @@ static void process_incoming_migration_co(void *opaque)
> > runstate_set(global_state_get_runstate());
> > }
> > migrate_decompress_threads_join();
> > + /*
> > + * This must happen after any state changes since as soon as an external
> > + * observer sees this event they might start to prod at the VM assuming
> > + * it's ready to use.
> > + */
> > + migrate_generate_event(MIGRATION_STATUS_COMPLETED);
> > }
> >
> > void process_incoming_migration(QEMUFile *f)
> >
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-10-15 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 6:27 [Qemu-devel] [PULL 0/3] Migration pull Juan Quintela
2015-10-15 6:27 ` [Qemu-devel] [PULL 1/3] Migration: Generate the completed event only when we complete Juan Quintela
2015-10-15 14:46 ` Eric Blake
2015-10-15 15:07 ` Christian Borntraeger
2015-10-15 16:12 ` Dr. David Alan Gilbert [this message]
2015-10-16 8:13 ` Juan Quintela
2015-10-15 6:27 ` [Qemu-devel] [PULL 2/3] migration: announce VM's new home just before VM is runnable Juan Quintela
2015-10-15 6:28 ` [Qemu-devel] [PULL 3/3] migration: fix deadlock Juan Quintela
2015-10-16 15:23 ` [Qemu-devel] [PULL 0/3] Migration pull Peter Maydell
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=20151015161224.GD2598@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).