qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata


From: Jorge Lucángeli Obes
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
Date: Tue, 29 Jul 2008 00:05:35 -0300

On Mon, Jul 28, 2008 at 11:48 PM, Nathaniel McCallum
<address@hidden> wrote:
> On Mon, Jul 28, 2008 at 10:11 PM, Jorge Lucángeli Obes <address@hidden>

>> problem. Personally, I just want to have some way of avoiding the
>> command-line options that doesn't involve scripts.

> I'm not disagreeing, but it is really interesting that something that is
> "extremely useful" is rejected for lacking "conceptual integrity".  I don't
> have any numbers, but I suspect the most common use case of virtualization
> is one image file, one configuration and no snapshots.  Yet most
> virtualization solutions go for those designs which have "conceptual
> integrity" but are far more complex than needed by the majority of users
> (*cough*VMWare API*cough*).  I think those features are important and I
> don't want to cut them.  I just think there should be some way to optimize
> the user experience for the most common case without sacrificing the rest of
> the features.

I agree with your most common use case (which is incidentally my use
case), but I also think that the best way of serving that use case is
with an image file and a configuration file. As I see it, in that use
case, anything better than command-line options and scripts holding
them, is "extremely useful" - that's the point I was trying to make.
qcow2 snapshots were kind of a quick hack, a configuration file seems
more coherent.

Regards,
Jorge




reply via email to

[Prev in Thread] Current Thread [Next in Thread]