From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1hX9-0006mo-WD for qemu-devel@nongnu.org; Wed, 06 May 2009 09:51:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1hX5-0006kn-Ci for qemu-devel@nongnu.org; Wed, 06 May 2009 09:51:39 -0400 Received: from [199.232.76.173] (port=36629 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1hX5-0006ki-5D for qemu-devel@nongnu.org; Wed, 06 May 2009 09:51:35 -0400 Received: from mx2.redhat.com ([66.187.237.31]:42676) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M1hX4-0000L9-Hj for qemu-devel@nongnu.org; Wed, 06 May 2009 09:51:34 -0400 Message-ID: <4A0195A3.7090205@redhat.com> Date: Wed, 06 May 2009 15:50:27 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 References: <1241571650-16212-1-git-send-email-alex@csgraf.de> <20090506082810.GB23167@redhat.com> <4A0154E9.7020705@redhat.com> <20090506093143.GC23167@redhat.com> <4A015F06.7050102@redhat.com> <4A018CD8.6000200@codemonkey.ws> <20090506133920.GK23167@redhat.com> In-Reply-To: <20090506133920.GK23167@redhat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: alex@csgraf.de, nolan@sigbus.net, Avi Kivity , qemu-devel@nongnu.org Daniel P. Berrange schrieb: > All I care about from libvirt POV, is that there is a way to give QEMU an > absolute file path for a disk, and guarentee that QEMU will treat this as > a local file path, and not try any access protocols, other than 'open(2)'. > Various options from this thread.... > > - Treat any path starting with / as local file > - Allow file: as a prefix > - Allow file:/// as a prefix, real URI style > - Add a protocol=file flag to -drive > > Pick one, pick several, suggest more. Any of these options would work as > far as I'm concerned, and we could easily support several. I think the > first is desirable because that's the natural thing users will try when > launching QEMU directly. I think we all agree that file: is a reasonable option for libvirt which covers all cases of colons (even relative paths starting with http:), so let's take this one. If you want to magically do the right thing for users invoking qemu manually, I think we should rather go for: 5) Treat anything as local file which has a protocol prefix that doesn't match a known protocol This would mean that vvfat:xyz uses the vvfat protocol, but foo:bar is a local file because the protocol foo doesn't exist. I think this variant is less confusing magic than checking for a completely unrelated character like /. Kevin