All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: "Ben Chaney" <bchaney@akamai.com>,
	qemu-devel@nongnu.org, "Fabiano Rosas" <farosas@suse.de>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Alex Williamson" <alex@shazbot.org>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Hamza Khan" <hamza.khan@nutanix.com>,
	"Mark Kanda" <mark.kanda@oracle.com>,
	"Joshua Hunt" <johunt@akamai.com>,
	"Max Tottenham" <mtottenh@akamai.com>,
	"Steve Sistare" <steven.sistare@oracle.com>
Subject: Re: [PATCH v4 0/8] Live update: tap and vhost
Date: Mon, 2 Feb 2026 09:06:51 -0500	[thread overview]
Message-ID: <aYCvexnciB7THTkr@x1.local> (raw)
In-Reply-To: <4b4e5317-9bbe-45c3-8c10-41cc448c5d22@yandex-team.ru>

On Thu, Jan 29, 2026 at 04:58:41PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> On 28.01.26 23:39, Ben Chaney wrote:
> > Tap and vhost devices can be preserved during cpr-transfer using
> > traditional live migration methods, wherein the management layer
> > creates new interfaces for the target and fiddles with 'ip link'
> > to deactivate the old interface and activate the new.
> > 
> > However, CPR can simply send the file descriptors to new QEMU,
> > with no special management actions required.  The user enables
> > this behavior by specifing '-netdev tap,cpr=on'.  The default
> > is cpr=off.
> > 
> > Signed-off-by: Ben Chaney <bchaney@akamai.com>
> Hi!
> 
> I'd like to note again, that I'mvworking on an alternative solution for live-updating
> virtio-net+TAP, passing FDs through unix domain socket, which:
> 
> 1. Doesn't require second migration channel
> 2. Doesn't use CPR: the whole TAP state, including negotiated parameters
> and opened FD are natively passed as usual migration state structure.
> (look here: https://lore.kernel.org/qemu-devel/20251030203116.870742-7-vsementsov@yandex-team.ru/ )
> 3. Still should be compatible with CPR, and may be used in context of CPR-update
> 
> The latest version was
> 
> [PATCH v9 0/8] virtio-net: live-TAP local migration
> https://lore.kernel.org/qemu-devel/20251030203116.870742-1-vsementsov@yandex-team.ru/
> 
> and I plan to post v10 soon.

Yes, thanks for re-raising this.  If we have similar features being
proposed, we should always discuss whether we should stick with one of them
if that'll work for all.

IIUC Vladimir's solution looks indeed superior in that it has less
constraints, and also works for CPR mode.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2026-02-02 14:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 20:39 [PATCH v4 0/8] Live update: tap and vhost Ben Chaney
2026-01-28 20:39 ` [PATCH v4 1/8] migration: stop vm earlier for cpr Ben Chaney
2026-02-02 13:31   ` Fabiano Rosas
2026-01-28 20:39 ` [PATCH v4 2/8] migration: cpr setup notifier Ben Chaney
2026-02-02 14:01   ` Fabiano Rosas
2026-01-28 20:39 ` [PATCH v4 3/8] vhost: reset vhost devices for cpr Ben Chaney
2026-01-28 20:39 ` [PATCH v4 4/8] cpr: delete all fds Ben Chaney
2026-01-28 20:39 ` [PATCH v4 5/8] tap: common return label Ben Chaney
2026-01-28 20:39 ` [PATCH v4 6/8] tap: cpr support Ben Chaney
2026-02-04 13:05   ` Markus Armbruster
2026-01-28 20:39 ` [PATCH v4 7/8] tap: postload fix for cpr Ben Chaney
2026-01-28 20:39 ` [PATCH v4 8/8] tap: cpr fixes Ben Chaney
2026-01-29 13:58 ` [PATCH v4 0/8] Live update: tap and vhost Vladimir Sementsov-Ogievskiy
2026-02-02 14:06   ` Peter Xu [this message]
2026-02-02 15:42     ` Chaney, Ben
2026-02-03  9:57       ` Vladimir Sementsov-Ogievskiy
2026-02-03 19:17         ` Peter Xu
2026-02-03 19:46           ` Chaney, Ben
2026-02-03 20:04             ` Mark Kanda
2026-02-03 20:47               ` Peter Xu
2026-02-04  7:56                 ` Vladimir Sementsov-Ogievskiy
2026-02-04 16:34                   ` Peter Xu

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=aYCvexnciB7THTkr@x1.local \
    --to=peterx@redhat.com \
    --cc=alex@shazbot.org \
    --cc=armbru@redhat.com \
    --cc=bchaney@akamai.com \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=hamza.khan@nutanix.com \
    --cc=jasowang@redhat.com \
    --cc=johunt@akamai.com \
    --cc=mark.kanda@oracle.com \
    --cc=mst@redhat.com \
    --cc=mtottenh@akamai.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=steven.sistare@oracle.com \
    --cc=sw@weilnetz.de \
    --cc=vsementsov@yandex-team.ru \
    /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.