From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] qemu: block.c: introducing "fmt:FMT:" prefix to image-filenames
Date: Thu, 8 Jan 2009 18:52:56 +0000 [thread overview]
Message-ID: <20090108185256.GA8669@redhat.com> (raw)
In-Reply-To: <496642BD.4010706@redhat.com>
On Thu, Jan 08, 2009 at 08:15:25PM +0200, Uri Lublin wrote:
> The purpose of this prefix is to
> 1. Provide a way to know the backing file format without probing
> it (setting the format upon creation time).
> 2. Enable using qcow2 format (and others) over host block devices.
> (only if the user specifically asks for it).
>
> If no fmt:FMT: is provided we go back to probing.
I still don't like the fact that this is inventing a second syntax
for specifying format that's different to the syntax used for the
existing -drive parameter, which is
-drive file=/some/path,format=qcow2,....other disk options...
> backing file format is qcow2 (even though it's on a host block device)
> $ qemu-img create -b fmt:qcow2:/dev/loop0 -f qcow2 /tmp/uuu.qcow2
I'd prefer to see a '-F' flag to specify format of backing file and
leave syntax of existing -b arg alone
$ qemu-img create -F qcow2 -b /dev/loop0 -f qcow2 /tmp/uuu.qcow2
> force backing file format to raw (no probing)
> $ qemu-img create -f raw /tmp/image1.raw 10G
> $ qemu-img create -b fmt:raw:/tmp/image1.raw -f qcow2 /tmp/image1.qcow2
$ qemu-img create -F raw -b /tmp/image1.raw -f qcow2 /tmp/image1.qcow2
> Use together with other protocols, e.g. nbd
> $ qemu-nbd -v -n --snapshot -t -k /tmp/uuu.socket
> fmt:qcow2:/tmp/images/uuu.qcow2 &
Should just add a -f arg to qemu-nbd to specify format so it
follows qemu-img style, eg
$ qemu-nbd -v -n --snapshot -t -k /tmp/uuu.socket \
-f qcow2 /tmp/images/uuu.qcow2 &
> $ qemu-img info nbd:unix:/tmp/uuu.socket
> $ qemu-system-x86_64 -snapshot -hda nbd:unix:/tmp/uuu.socket
>
> Or fat
> $ qemu-system-x86_64 -hda fmt:qcow2:/tmp/uuu.qcow2 -hdb
> fat:floppy:/tmp/images
This is unneccessary, since -hda is deprecated, and there's a
new -drive arg that already has ability to set format explicitly,
as well as many other flags that you need when setting up disks.
$ qemu-system-x86_64 \
-drive index=0,format=qcow2,file=/tmp/uuu.qcow2 \
-drive index=1,format=fat:floppy,file=/tmp/images
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-01-08 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 18:15 [Qemu-devel] qemu: block.c: introducing "fmt:FMT:" prefix to image-filenames Uri Lublin
2009-01-08 18:52 ` Daniel P. Berrange [this message]
2009-01-08 19:04 ` Anthony Liguori
2009-01-08 19:09 ` Uri Lublin
2009-01-08 19:13 ` Daniel P. Berrange
2009-01-08 19:15 ` Uri Lublin
2009-01-08 23:18 ` Jamie Lokier
2009-01-08 23:23 ` Anthony Liguori
2009-01-09 0:15 ` Jamie Lokier
2009-01-09 9:17 ` Kevin Wolf
2009-01-11 20:42 ` Uri Lublin
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=20090108185256.GA8669@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=uril@redhat.com \
/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).