qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Fate of the read-only block drivers?
Date: Wed, 5 May 2010 20:27:20 +0200	[thread overview]
Message-ID: <20100505182719.GA8067@lst.de> (raw)

Currently we have four very simple, read-only block drivers in the
tree:

 - cloop:
	This one is known buggy for non-trivial use and didn't get
	any chance but the usual API changes and cleanup sweeps
	since it was commited in 2004.

 - dmg:
	This one is really grotty and by auditing the code and comparing
	it to dmg2img completely buggy for non-compressed chunks.  It's
	also missing lots of the features in modern dmg image.  Also
	there's no creation tool for Linux.  No non-trivial commits
	since the initial import in 2004.

 - bochs:
	There is an bximage tools to actually create images for it,
	but not to actually add any content to them.  It had one
	non-trivial commit in 2007 to add support for growable formats
	since it's initial commit in 2004.

 - parallels:
	I can't find any way to actually create the image except with
	the parallels image tool which seems to require a commercial
	parallels license.
	No non-trivial commits since the initial import in 2007.

At this point I'm not sure if it's worth bothering to fix these up,
as they're bitrotted and except for cloop there's no reasy way to
actually create test images for them.

Any good reason to keep them, and if yes any good idea for a test plan
to keep them working?

             reply	other threads:[~2010-05-05 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 18:27 Christoph Hellwig [this message]
2010-05-06  9:23 ` [Qemu-devel] Fate of the read-only block drivers? 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=20100505182719.GA8067@lst.de \
    --to=hch@lst.de \
    --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).