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.