All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: Peter Xu <peterx@redhat.com>,
	qemu-devel@nongnu.org, Juraj Marcin <jmarcin@redhat.com>,
	Fabiano Rosas <farosas@suse.de>,
	Markus Armbruster <armbru@redhat.com>,
	Prasad Pandit <ppandit@redhat.com>
Subject: Re: [PATCH v2 0/2] migration: feature removals for 11.0
Date: Tue, 17 Feb 2026 09:47:08 +0000	[thread overview]
Message-ID: <aZQ5HObOS3RGwf-4@redhat.com> (raw)
In-Reply-To: <aZQ0q2r6w3OkSP2f@angien.pipo.sk>

On Tue, Feb 17, 2026 at 10:29:38AM +0100, Peter Krempa wrote:
> On Thu, Jan 15, 2026 at 17:55:01 -0500, Peter Xu wrote:
> > v2:
> > - Added R-bs
> > - Updated description for removing zero-blocks [Markus]
> > - Squashed the "fd: to file" test removal into the 2nd patch
> > - I dropped the COLO patch, I have a local patch to remove colo migration
> >   completely, but looks like we won't do it..  Let's leave it for later but
> >   do the rest first
> > 
> > This series removes two deprecated features for 11.0.
> > 
> > Please review, thanks.
> > 
> > Peter Xu (2):
> >   migration: Remove zero-blocks capability
> >   migration: Remove fd: support on files
> > 
> >  docs/about/deprecated.rst             | 20 -------------
> 
> Note that per the 'MAINTAINERS' file, changes to any deprecations ought
> to be CC'd to the libvirt list for visibility.
> 
> In this case we've forgotten about the deprecation and didn't fix it
> before the qemu cahnge was pushed. I'll send out patches soon, but keep
> in mind to *always* CC the libvirt list with deprecations.

I'm suprised  to see libvirt broken at all here.

AFAIR, the 'fd:' protocol inadvertantly gained support for targetting
plain files, which the deprecation aimed to then revert (remove). The
actual removal though seems to have targetted anything which is not a
socket, which includes pipes, which libvirt was using.

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



  reply	other threads:[~2026-02-17  9:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 22:55 [PATCH v2 0/2] migration: feature removals for 11.0 Peter Xu
2026-01-15 22:55 ` [PATCH v2 1/2] migration: Remove zero-blocks capability Peter Xu
2026-01-16  8:49   ` Markus Armbruster
2026-01-15 22:55 ` [PATCH v2 2/2] migration: Remove fd: support on files Peter Xu
2026-02-17  9:29 ` [PATCH v2 0/2] migration: feature removals for 11.0 Peter Krempa
2026-02-17  9:47   ` Daniel P. Berrangé [this message]
2026-02-17  9:55     ` Peter Krempa
2026-02-17 10:08       ` Daniel P. Berrangé
2026-02-17 11:25   ` Markus Armbruster
2026-02-18 21:21     ` Peter Xu
2026-02-19  7:23       ` Markus Armbruster
2026-02-23 10:00         ` Daniel P. Berrangé
2026-02-23 15:56           ` 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=aZQ5HObOS3RGwf-4@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=farosas@suse.de \
    --cc=jmarcin@redhat.com \
    --cc=peterx@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.