From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Lyu Mitnick <mitnick.lyu@gmail.com>
Subject: Re: [Qemu-devel] GSoC - QCOW2 <-> QED image converter
Date: Wed, 6 Apr 2011 17:52:49 +0200 [thread overview]
Message-ID: <20110406155249.GA29963@lst.de> (raw)
In-Reply-To: <4D9C8391.102@redhat.com>
On Wed, Apr 06, 2011 at 05:15:29PM +0200, Kevin Wolf wrote:
> Am 06.04.2011 17:06, schrieb Christoph Hellwig:
> > On Wed, Apr 06, 2011 at 07:41:37AM +0100, Stefan Hajnoczi wrote:
> >> Yes, split images are not supported by block/vpc.c.
> >
> > I'm working on that feature for vmdk right now, which is quite
> > interesting as vmdk really is two different format both claiming
> > to be vmdk, of which one is simply a text file telling how other
> > vmdk images are glued together.
>
> Last time I checked the other one wasn't a single format either, but
> rather something like ten different subformats.
The binary vmdk files have a few different revisions too, yes.
> Anyway, if you're working on split VMDK images, I should probably stop
> advertising it as a GSoC project?
I didn't know it was advertised, but there's indeed no need to duplicate the
work.
next prev parent reply other threads:[~2011-04-06 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 18:56 [Qemu-devel] GSoC - QCOW2 <-> QED image converter Lyu Mitnick
2011-04-05 9:15 ` Stefan Hajnoczi
2011-04-05 18:03 ` Lyu Mitnick
2011-04-06 6:41 ` Stefan Hajnoczi
2011-04-06 11:13 ` Lyu Mitnick
2011-04-06 12:46 ` Stefan Hajnoczi
2011-04-06 15:06 ` Christoph Hellwig
2011-04-06 15:15 ` Kevin Wolf
2011-04-06 15:52 ` Christoph Hellwig [this message]
2011-04-06 23:10 ` Lyu Mitnick
2011-04-11 18:11 ` Christoph Hellwig
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=20110406155249.GA29963@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=mitnick.lyu@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.