qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vmdk stream-optimised format
Date: Tue, 20 Aug 2013 15:08:59 +0800	[thread overview]
Message-ID: <20130820070859.GA11944@localhost.localdomain> (raw)
In-Reply-To: <90D0FA8B-A032-4608-9CAA-B5BC26DC4D75@alex.org.uk>

On Tue, 08/20 07:51, Alex Bligh wrote:
> 
> On 20 Aug 2013, at 02:42, Fam Zheng wrote:
> 
> > OK, thanks for explaination. That sounds a valid use case for
> > streamOptimized. However I am afraid QEMU and its users benefit not much
> > from this feature anyway, because it's moving a VM away to VMware, :)
> > that might be the reason it's not there yet, and I don't know about any
> > plan to do it in the near future.
> 
> Well, given it is an open source project, the more interoperability
> the better. Even if it just means users need not worry about lock
> in to faster hypervisors ... Being more serious, qemu-img is
> part of the project too.
> 
> > But if someone sends patches for this, I think it is possible to get in.
> 
> I guessed "send code" might be the answer :-)
> 
> What I'm not sure of is whether the streaming format has to be written
> sequentially from as opposed to random writes. I believe the way
> qemu-img convert works, one can't guarantee the writes are
> sequential.
> 
The order of sectors doesn't matter, but granularity should be aligned
to, as the data is compressed cluster by cluster. And no overwrite, of
course. The challenge may be that header comes at the end of file
(well, called footer), which is not decided at create time.

Thanks,
Fam

  reply	other threads:[~2013-08-20  7:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 11:09 [Qemu-devel] vmdk stream-optimised format Alex Bligh
2013-08-19 11:23 ` Fam Zheng
2013-08-19 11:50   ` Alex Bligh
2013-08-20  1:42     ` Fam Zheng
2013-08-20  6:51       ` Alex Bligh
2013-08-20  7:08         ` Fam Zheng [this message]
2013-08-20 10:53           ` Paolo Bonzini
2013-08-20 13:37             ` Alex Bligh
2013-08-20 13:37               ` Paolo Bonzini
2013-08-20 14:02                 ` Alex Bligh
2013-08-20 14:51         ` Stefan Hajnoczi

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=20130820070859.GA11944@localhost.localdomain \
    --to=famz@redhat.com \
    --cc=alex@alex.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).