All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>, Cornelia Huck <cohuck@redhat.com>,
	QEMU Developer <qemu-devel@nongnu.org>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] German BSI analysed security of KVM / QEMU
Date: Mon, 16 Oct 2017 17:24:04 +0200	[thread overview]
Message-ID: <20171016152404.GD5145@localhost.localdomain> (raw)
In-Reply-To: <20171016133812.GB11975@redhat.com>

Am 16.10.2017 um 15:38 hat Daniel P. Berrange geschrieben:
> > Another thing that made me a bit sad is that they mention qed as a
> > better performing alternative for qcow2. Even in 2017, people keep
> > spreading this nonsense. :-(
> 
> Probably because when you google for QED you inevitably hit this article
> near the top:
> 
>   https://www.phoronix.com/scan.php?page=news_item&px=OTY0MQ
> 
> And there's little clear information on QEMU website to show that QED
> is essentially an obsolete experiment.
> 
> Perhaps some clear update to this page would help, and also in the
> qemu docs
> 
>   https://wiki.qemu.org/Features/QED

I updated the wiki page, maybe this will help a bit.

We could also consider printing a warning when you create a new image in
an obsolete native qemu format (i.e. qcow1 and qed).

Kevin

  parent reply	other threads:[~2017-10-16 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  9:10 [Qemu-devel] German BSI analysed security of KVM / QEMU Stefan Weil
2017-10-13  9:37 ` Cornelia Huck
2017-10-13  9:44   ` Daniel P. Berrange
2017-10-13  9:53     ` Cornelia Huck
2017-10-16 13:22     ` Kevin Wolf
2017-10-16 13:38       ` Daniel P. Berrange
2017-10-16 13:47         ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-10-16 15:24         ` Kevin Wolf [this message]
2017-10-13 10:30   ` [Qemu-devel] " Stefan Weil

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=20171016152404.GD5145@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.