From: Uri Lublin <uril@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu: block.c: introducing "fmt:FMT:" prefix to image-filenames
Date: Sun, 11 Jan 2009 22:42:58 +0200 [thread overview]
Message-ID: <496A59D2.6070707@redhat.com> (raw)
In-Reply-To: <49671618.3080102@suse.de>
Kevin Wolf wrote:
> Jamie Lokier schrieb:
>> Uri Lublin wrote:
>>> Daniel P. Berrange wrote:
>>>> Yes the format you write into the qcow2 header can still use the
>>>> fmt:qcow2: prefix - just no need to expose that particular qcow2
>>>> specific implementation detail on the CLI.
>>> OK. I'll prepare a patch that adds '-F fmt' to 'qemu-img create -b ...'
>> Will it break backing files whose filename begins with "fmt:"?
>>
>> Just because I hate hidden "some filenames work, some filenames break
>> mysteriously, and of course it's not documented" dodgy hacks.
>
> Uri, now that you are making the change in qcow2 instead of block.c,
> have you thought about using the earlier suggested "filename.img\0qcow2"
> hack? This shouldn't break filenames.
>
Hi Kevin,
1. The change is still in block.c, as the backing file is opened in
bdrv_open2(), and also we must support raw format as a backing_file format (and
basically any format).
2. I thought everyone agreed that "filename.img\0qcow2" would work, but that we
should try a different solution.
3. This patch does not make things worse (with regards to "unsupported
filename"). Without it too, qemu will refuse to run a filename that begins with
"fmt:"
Thanks,
Uri.
prev parent reply other threads:[~2009-01-11 20:43 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
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 [this message]
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=496A59D2.6070707@redhat.com \
--to=uril@redhat.com \
--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.