From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1ebk-00012e-QS for qemu-devel@nongnu.org; Wed, 06 May 2009 06:44:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1ebf-00011D-Q5 for qemu-devel@nongnu.org; Wed, 06 May 2009 06:44:12 -0400 Received: from [199.232.76.173] (port=35824 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1ebf-000115-I2 for qemu-devel@nongnu.org; Wed, 06 May 2009 06:44:07 -0400 Received: from mail2.shareable.org ([80.68.89.115]:49245) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M1ebf-0007as-40 for qemu-devel@nongnu.org; Wed, 06 May 2009 06:44:07 -0400 Date: Wed, 6 May 2009 11:43:59 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 Message-ID: <20090506104359.GA23364@shareable.org> References: <1241571650-16212-1-git-send-email-alex@csgraf.de> <20090506082810.GB23167@redhat.com> <4A0154E9.7020705@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A0154E9.7020705@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: alex@csgraf.de, nolan@sigbus.net, qemu-devel@nongnu.org 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