From: Jamie Lokier <jamie@shareable.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: alex@csgraf.de, nolan@sigbus.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2
Date: Wed, 6 May 2009 11:43:59 +0100 [thread overview]
Message-ID: <20090506104359.GA23364@shareable.org> (raw)
In-Reply-To: <4A0154E9.7020705@redhat.com>
Kevin Wolf wrote:
> If apps want to be sure that they are accessing a local file, they must
> ensure not to have a colon in the file name. Otherwise this specifies a
> protocol for the qemu block layer.
>
> Btw, we could use a way to escape colons in a file name. Using such
> files isn't possible currently.
Escaping:
Because I'm not sure how QEMU parses colons, spaces, commas, quotes
and who knows what other special characters in these options, and
because the monitor might use different parsing when reading a disk
image name, my management scripts always create symlinks to the disks,
and pass the names of the symlinks instead to the command line and the
monitor.
It's quite awkward for qcow2 delta files, because they contain the
name of their backing file, it can be relative, cannot be overriden,
and is resolved relative to the management script's symlinks, and they
can be stacked more than one deep... But most of the time it is
solvable by making a set of symlinks in a little directory hierarchy.
I'd be quite happy with file:///path/to/file%20containing%20spaces.vhd
working, on the command line and in the monitor, in the the way file
URIs are meant to work.
-- Jamie
next prev parent reply other threads:[~2009-05-06 10:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 1:00 [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 alex
2009-05-06 8:28 ` Daniel P. Berrange
2009-05-06 9:14 ` Kevin Wolf
2009-05-06 9:31 ` Daniel P. Berrange
2009-05-06 9:40 ` Alexander Graf
2009-05-06 9:57 ` Avi Kivity
2009-05-06 10:00 ` Kevin Wolf
2009-05-06 10:06 ` Daniel P. Berrange
2009-05-06 10:13 ` Daniel P. Berrange
2009-05-06 10:15 ` Avi Kivity
2009-05-06 10:15 ` Alexander Graf
2009-05-06 13:11 ` Anthony Liguori
2009-05-06 10:16 ` Kevin Wolf
2009-05-06 10:23 ` Alexander Graf
2009-05-06 10:24 ` Daniel P. Berrange
2009-05-06 10:09 ` Alexander Graf
2009-05-06 13:09 ` Anthony Liguori
2009-05-06 13:59 ` Avi Kivity
2009-05-06 14:08 ` Anthony Liguori
2009-05-06 14:14 ` François Revol
2009-05-06 13:12 ` Anthony Liguori
2009-05-06 13:39 ` Daniel P. Berrange
2009-05-06 13:43 ` Anthony Liguori
2009-05-06 13:50 ` Kevin Wolf
2009-05-06 13:59 ` Anthony Liguori
2009-05-06 14:11 ` Kevin Wolf
2009-05-06 14:39 ` Anthony Liguori
2009-05-06 14:48 ` Alexander Graf
2009-05-06 14:49 ` Avi Kivity
2009-05-06 16:51 ` Anthony Liguori
2009-05-08 17:00 ` Jamie Lokier
2009-05-06 14:49 ` Kevin Wolf
2009-05-06 13:08 ` Anthony Liguori
2009-05-06 10:43 ` Jamie Lokier [this message]
2009-05-06 12:59 ` Anthony Liguori
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=20090506104359.GA23364@shareable.org \
--to=jamie@shareable.org \
--cc=alex@csgraf.de \
--cc=kwolf@redhat.com \
--cc=nolan@sigbus.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).