qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2


From: Alexander Graf
Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2
Date: Wed, 6 May 2009 11:40:00 +0200


On 06.05.2009, at 11:31, Daniel P. Berrange wrote:
On Wed, May 06, 2009 at 11:14:17AM +0200, Kevin Wolf wrote:
Daniel P. Berrange schrieb:
Perhaps only enable these remote URIs with the -drive parameter, when
an explicit fmt=http option is set. But can this be layered into the
other protocols, eg could the remote URI be in qcow, vmdk, etc formats,
or are you assuming the remote uri is raw file ?

It should work with all formats. This is why fmt=http is wrong. It's not
a format, but a protocol.

Then I'd prefer we add a protocol=XXX option for magic protocols. This
would be easier to use & clearer than requiring escaping of magic
characters, eg

  -drive file=/some/path:with:colons,protocol=file
  -drive file=http://some/path,protocol=uri

For compatability, we could make it such that if protocol=XXX was left out, it could try and "guess" it, in same way QEMU does if format=XXX is left out
for content format.

I like that idea, yes.

Unfortunately it is out of scope of this patch. The problem you're describing with qemu taking on remote connections exists today already with NBD support. Right now there are 2 protocols implemented in qemu that I'm aware of:

- file (local)
- nbd (remote)

and I just add another remote one:
- http (remote)

So your concerns do apply today already. Maybe you want to come up with a patch to implement a protocol= parameter to -drive?

Alex





reply via email to

[Prev in Thread] Current Thread [Next in Thread]