All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
	Kevin Wolf <kwolf@redhat.com>,
	devel@lists.libvirt.org
Subject: Re: [PATCH for-12] qed: deprecate the block driver
Date: Mon, 9 Nov 2026 16:42:08 +0000	[thread overview]
Message-ID: <avH34P2rgELLqa4b@redhat.com> (raw)
In-Reply-To: <20261109163431.443983-1-stefanha@redhat.com>

On Mon, Nov 09, 2026 at 09:34:31AM -0700, Stefan Hajnoczi wrote:
> It has been unofficially deprecated on the wiki for many years:
> https://wiki.qemu.org/Features/QED
> 
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  docs/about/deprecated.rst | 13 +++++++++++++
>  1 file changed, 13 insertions(+)

How about bdrv_qed_open also adding

  warn_report_once("QED is deprecated, please switch to qcow2");

for the part of the user population who never reads the docs.

> 
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 0891bbc44de..ab83626af0b 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -526,3 +526,16 @@ If the user requests a modern x86 CPU model (i.e. not one of ``486``,
>  ``athlon``, ``kvm32``, ``pentium``, ``pentium2``, ``pentium3``or ``qemu32``)
>  a warning will be displayed until a future QEMU version when such CPUs will
>  be rejected.
> +
> +Block drivers
> +-------------
> +
> +QED (since 12.0)
> +''''''''''''''''
> +
> +The QED disk image format is not actively maintained and qcow2 has exceeded its
> +features and performance for many years. Since QED was never widely deployed,
> +the format is not required for compatibility reasons. It is unlikely that
> +qemu-img users still need to convert images to or from QED.
> +
> +Use qcow2 instead of QED.
> -- 
> 2.56.0
> 

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-11-09 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 16:34 [PATCH for-12] qed: deprecate the block driver Stefan Hajnoczi
2026-11-09 16:42 ` Daniel P. Berrangé [this message]

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=avH34P2rgELLqa4b@redhat.com \
    --to=berrange@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=kwolf@redhat.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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.