qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: alex@csgraf.de, nolan@sigbus.net, Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2
Date: Wed, 06 May 2009 15:50:27 +0200	[thread overview]
Message-ID: <4A0195A3.7090205@redhat.com> (raw)
In-Reply-To: <20090506133920.GK23167@redhat.com>

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

  parent reply	other threads:[~2009-05-06 13:51 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 [this message]
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
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=4A0195A3.7090205@redhat.com \
    --to=kwolf@redhat.com \
    --cc=alex@csgraf.de \
    --cc=avi@redhat.com \
    --cc=berrange@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).