From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: 吴兴博 <wuxb45@gmail.com>,
qemu-devel@nongnu.org, "Kirill Batuzov" <batuzovk@ispras.ru>
Subject: Re: [Qemu-devel] disk image: self-organized format or raw file
Date: Wed, 13 Aug 2014 17:42:00 +0200 [thread overview]
Message-ID: <20140813154200.GD3701@noname.redhat.com> (raw)
In-Reply-To: <53EA332C.5020908@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Am 12.08.2014 um 17:30 hat Eric Blake geschrieben:
> On 08/12/2014 08:14 AM, 吴兴博 wrote:
> >>> However FVD seems to have been ignored by community.
> >>
> >> Care to give a pointer to a URL describing the FVD format?
> >>
> >> http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg00398.html
> >
> > This thread could be the clearest message on FVD.
>
> That very message also points out WHY the community has appeared to
> ignore FVD:
>
> "For any feature to be seriously considered for inclusion in QEMU,
> patches need to be posted to the mailing list against the latest git
> tree. That's a pre-requisite for any real discussion."
>
> > It also has a paper published on USENIX conference.
> > https://www.usenix.org/event/atc11/tech/final_files/Tang.pdf
>
> Thanks for the references. Are you interested in posting patches to
> revive the work on that format?
Just to be clear upfront so that you don't waste your time: A new native
image format is not going to be merged. You would have to prove that
your format is capable of replacing qcow2 with all its features, that
it's better in some respect and that qcow2 cannot be extended to provide
the same. Other proposals, including FVD, have failed to provide that
and I'd consider it unlikely to happen this time. (QED fell short of it
and was merged anyway for political reasons; it's clear today that this
was a mistake.)
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-13 15:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 23:38 [Qemu-devel] disk image: self-organized format or raw file 吴兴博
2014-08-12 0:52 ` Fam Zheng
2014-08-12 10:46 ` 吴兴博
2014-08-12 11:19 ` Fam Zheng
[not found] ` <CABPa+v1a7meoEtjLkwygjuZEABTqd8q3efGWJvAsAr-mLTQb-A@mail.gmail.com>
[not found] ` <20140812113916.GB2803@T430.redhat.com>
2014-08-12 12:03 ` 吴兴博
2014-08-12 12:21 ` Fam Zheng
2014-08-12 13:08 ` Kirill Batuzov
2014-08-12 13:23 ` Eric Blake
2014-08-12 13:45 ` 吴兴博
2014-08-12 14:07 ` Eric Blake
2014-08-12 14:14 ` 吴兴博
2014-08-12 15:30 ` Eric Blake
2014-08-12 16:22 ` Xingbo Wu
2014-08-13 1:29 ` Fam Zheng
2014-08-13 15:42 ` Kevin Wolf [this message]
2014-08-12 18:39 ` Richard W.M. Jones
2014-08-12 18:46 ` Daniel P. Berrange
2014-08-12 18:52 ` Richard W.M. Jones
2014-08-12 19:23 ` Xingbo Wu
2014-08-12 20:14 ` Richard W.M. Jones
2014-08-13 15:54 ` Kevin Wolf
2014-08-13 16:38 ` Xingbo Wu
2014-08-13 18:32 ` Kevin Wolf
2014-08-13 21:04 ` Xingbo Wu
2014-08-13 21:35 ` Eric Blake
2014-08-14 2:42 ` Xingbo Wu
2014-08-14 9:06 ` Kevin Wolf
2014-08-14 20:53 ` Xingbo Wu
2014-08-15 10:46 ` Kevin Wolf
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=20140813154200.GD3701@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=batuzovk@ispras.ru \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wuxb45@gmail.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.