From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 2/2] failover: don't allow to migrate a paused VM that needs PCI unplug
Date: Tue, 2 Nov 2021 13:08:25 -0400 [thread overview]
Message-ID: <20211102130811-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <5139c0a8-6aa0-48df-f353-84a15ffc4dd1@redhat.com>
On Tue, Nov 02, 2021 at 06:06:51PM +0100, Laurent Vivier wrote:
> On 02/11/2021 16:04, Michael S. Tsirkin wrote:
> > On Wed, Sep 29, 2021 at 04:43:11PM +0200, Laurent Vivier wrote:
> > > As the guest OS is paused, we will never receive the unplug event
> > > from the kernel and the migration cannot continue.
> > >
> > > Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> >
> > Well ... what if user previously did
> >
> > pause
> > start migration
> > unpause
> >
> > we are breaking it now for no good reason.
> >
> > Further, how about
> >
> > start migration
> > pause
> >
> > are we going to break this too? by failing pause?
> >
> >
>
> TL;DR: This patch only prevents to migrate a VFIO device as failover allows
> to start a migration with a VFIO device plugged in.
>
> Long Story:
>
> * before this patch:
>
> - pause and start migration and unpause-> fails if we unpause too late
> because we migrate a VFIO device, works otherwise
confused about this one. can you explain pls?
> - start migration and pause before we unplug the card -> hangs forever
> - start migration and pause after we unplug the card -> it works fine
>
> * After this patch:
>
> - pause and start migration and unpause-> fails if we unpause too late
> because of the new error checking, works otherwise
> - start migration and pause before we unplug the card -> fails because of
> the new error checking
> - start migration and pause after we unplug the card -> it works fine
>
> Thanks,
> Laurent
>
next prev parent reply other threads:[~2021-11-02 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 14:43 [PATCH 0/2] failover: don't allow to migrate a paused VM that needs PCI unplug Laurent Vivier
2021-09-29 14:43 ` [PATCH 1/2] migration: provide an error message to migration_cancel() Laurent Vivier
2021-11-02 9:04 ` Juan Quintela
2021-09-29 14:43 ` [PATCH 2/2] failover: don't allow to migrate a paused VM that needs PCI unplug Laurent Vivier
2021-11-02 9:04 ` Juan Quintela
2021-11-02 15:04 ` Michael S. Tsirkin
2021-11-02 15:28 ` Juan Quintela
2021-11-02 17:06 ` Laurent Vivier
2021-11-02 17:08 ` Michael S. Tsirkin [this message]
2021-11-02 17:26 ` Juan Quintela
2021-11-02 17:47 ` Laurent Vivier
2021-11-02 18:09 ` Juan Quintela
2021-11-02 17:43 ` Laurent Vivier
2021-10-06 9:22 ` [PATCH 0/2] " Laurent Vivier
2021-10-21 8:49 ` Laurent Vivier
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=20211102130811-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=lvivier@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).