qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent.Vivier@bull.net>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [Qemu-devel] Re: [RFC][PATCH] Modify loop device to be able to manage partitions of the image disk
Date: Wed, 16 Jan 2008 16:55:18 +0100	[thread overview]
Message-ID: <1200498918.4687.18.camel@frecb07144> (raw)
In-Reply-To: <478E1B57.7090609@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]

Le mercredi 16 janvier 2008 à 08:57 -0600, Anthony Liguori a écrit :
> > Le mardi 15 janvier 2008 à 23:54 +0000, Daniel P. Berrange a écrit :
[...]
> >>> 2- I'd like to mount qcow2 or others disk image formats, so perhaps it's
> >>> easier to modify loop device driver (but perhaps you know another magic
> >>> tool ?)
> >>>       
> >> There has been some work in this area wrt to Xen - the DM-Userspace project
> >> had some working code providing a device mapper target calling out to a 
> >> userspace daemon to handle non-raw file formats like qcow. I don't
> >> know what the state of it is now wrt to upstream kernel / device-mapper,
> >> or even whether it is more than just 'proof of concept', but the project
> >> page is here with some info:
> >>
> >>   http://wiki.xensource.com/xenwiki/DmUserspace
> 
> FWIW, I still think a userspace block device is the Right Way to support 

I agree with you, it was my first idea too, but it introduces complexity
to manage communications between the kernel part of the driver and the
userspace daemon: I don't like complexity.

> these sort of things.  dm-userspace turned out to be difficult as device 
> mapper has some rather strict requirements about alignment that some 
> formats (like qcow) cannot satisfy.
> 
> The loop driver is a terrible base to start from as it does not preserve 
> data integrity.
[...]

But everyone already uses loop as it is currently, so why not to add
more supported formats for the disk image ?
Why do you say it doesn't preserve data integrity ?

Regards,
Laurent
-- 
----------------- Laurent.Vivier@bull.net  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-16 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 18:22 [Qemu-devel] [RFC][PATCH] Modify loop device to be able to manage partitions of the image disk Laurent Vivier
2008-01-15 18:27 ` [Qemu-devel] Re: [kvm-devel] " Daniel P. Berrange
2008-01-15 23:40   ` Laurent Vivier
2008-01-15 23:54     ` Daniel P. Berrange
2008-01-16  0:30       ` Laurent Vivier
2008-01-16 14:57         ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2008-01-16 15:55           ` Laurent Vivier [this message]
2008-01-16 11:51 ` [Qemu-devel] [RFC][PATCH] Modify loop device to be able to managepartitions " Sergey Bychkov
2008-01-16 12:51   ` Laurent Vivier

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=1200498918.4687.18.camel@frecb07144 \
    --to=laurent.vivier@bull.net \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).