From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] Handling ':' on filenames
Date: Mon, 9 Mar 2009 21:11:34 +0000 [thread overview]
Message-ID: <20090309211134.GB2812@shareable.org> (raw)
In-Reply-To: <1236608928-sup-8973@blackpad>
Eduardo Habkost wrote:
> The -drive option has a way to escape colons. For the filename
> "/tmp/a,b,c", you can use:
>
> -drive file=/tmp/a,,b,,c,format=qcow2
>
> Not pretty, but it seems to work.
I wonder how you quote filenames from the monitor.
In my own management scripts I've taken to making a symlink with a
"safe" name to the real image file, and passing the safe name to KVM,
so that it's unambiguous. Causes a bit of fun with qcow2 files, which
refer to their backing files relative to the symlink not the target
file.
-- Jamie
next prev parent reply other threads:[~2009-03-09 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 21:28 [Qemu-devel] [PATCH][RFC] Handling ':' on filenames Eduardo Habkost
2009-03-08 11:28 ` Uri Lublin
2009-03-08 11:49 ` Stuart Brady
2009-03-09 14:32 ` Eduardo Habkost
2009-03-09 21:11 ` Jamie Lokier [this message]
2009-03-09 14:21 ` Eduardo Habkost
2009-03-09 14:27 ` Eduardo Habkost
2009-03-10 3:59 ` Amit Shah
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=20090309211134.GB2812@shareable.org \
--to=jamie@shareable.org \
--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).