qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] Add tar container format
Date: Thu, 13 Aug 2009 17:57:04 -0500	[thread overview]
Message-ID: <4A849A40.3080205@codemonkey.ws> (raw)
In-Reply-To: <1249486402-10824-1-git-send-email-agraf@suse.de>

Alexander Graf wrote:
> For that we still need to enable the qemu blockery to support stacking though.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
>   

This feels like a bit too much of a one-off to me.  I'm concerned that 
it's something we'd have to support long term that wouldn't have very 
many users beyond your particular use-case.

So far, we only support image formats that are dedicated to virtual 
machines.  We support http and nbd but those are generic protocols, not 
necessarily special formats.  tar and dzip seem arbitrary.  Why not zip, 
rar, bzip2, or any other format?

You could do all of this by making use of a fuse filesystem.

I'd almost rather see something like gio integration so that this sort 
of generic filesystem stuff could live somewhere else.  I'm curious what 
others think though.  Does it seem reasonable to include this type of 
functionality?

  reply	other threads:[~2009-08-13 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 15:33 [Qemu-devel] [PATCH] Add tar container format Alexander Graf
2009-08-13 22:57 ` Anthony Liguori [this message]
2009-08-13 23:08   ` Alexander Graf
2009-08-13 23:13     ` Anthony Liguori
2009-08-13 23:15       ` Anthony Liguori
2009-08-15 20:36       ` Christoph Hellwig
2009-08-17 12:05     ` [Qemu-devel] " Paolo Bonzini

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=4A849A40.3080205@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --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).