All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: qemu-img help missing backing file
Date: Tue, 30 Mar 2010 14:49:20 +0200	[thread overview]
Message-ID: <4BB1F350.2000100@redhat.com> (raw)
In-Reply-To: <5C4F242F-0AC7-4C25-AE6B-C3D12AFCE091@suse.de>

Am 30.03.2010 14:32, schrieb Alexander Graf:
> 
> On 30.03.2010, at 14:30, Kevin Wolf wrote:
> 
>> Am 30.03.2010 14:22, schrieb Alexander Graf:
>>> Howdy,
>>>
>>> I just wanted to create a backed qcow2 image and was irritated by qemu-img not showing me the correct command line option. It's just missing from the list:
>> [...]
>>> Is this intentional? The actual command still works:
>>>
>>>> agraf@s390t27:~/git/qemu> qemu-img-kvm create -f qcow2 -b /media/studio/images/SUSE/s390/sles11.raw /dev/shm/sles11-zipl.qcow2
>>>> Formatting '/dev/shm/sles11-zipl.qcow2', fmt=qcow2 size=21474836480 backing_file='/media/studio/images/SUSE/s390/sles11.raw' encryption=off cluster_size=0 
>>
>> -b still works to maintain compatibility with older versions. The
>> documented way is -o backing_file=foo (the qemu-img output you quote
>> even contains this option).
> 
> Interesting O_o. Maybe it'd be a good idea to give some examples in the help output? The same way the -e and -b options were having examples there too. That really makes them easier to find.

Feel free to submit a patch. ;-)

Examples sound like an easy way to make these features more visible
again. Even better, but a bit more work, would be to include a
dynamically generated list of all supported options like this:

backing_file: File name of a base image (qcow, qcow2, vmdk)
backing_fmt:  Image format of the base image (qcow2)
encryption:   Encrypt the image (qcow, qcow2)

Kevin

  reply	other threads:[~2010-03-30 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 12:22 [Qemu-devel] qemu-img help missing backing file Alexander Graf
2010-03-30 12:30 ` [Qemu-devel] " Kevin Wolf
2010-03-30 12:32   ` Alexander Graf
2010-03-30 12:49     ` Kevin Wolf [this message]
2010-03-30 13:04       ` Juan Quintela
2010-03-30 13:23         ` 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=4BB1F350.2000100@redhat.com \
    --to=kwolf@redhat.com \
    --cc=agraf@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.