On Mon, Aug 04, 2008 at 11:02:33AM +0200, Stefan de Konink wrote:
On Mon, 4 Aug 2008, Daniel P. Berrange wrote:
> > - - For iSCSI and related stuff everything was relatively easy, because
> > this would just mean to write the right /dev/blabla to the xenstore.
> > What is your idea to get different drivers working via:
> > virt://pool/volume (so basically blktap vs file vs disk)
>
> My idea was to have a script in /etc/xen/scripts/
Me too, but in order to 'fetch' the actual configuration it is required to
contact libvirt. And query about the pool/volume location. In this way it
would be actually a 'redirection' to blktap or adding a devicepath.
So this script is now written in plain C, but I want to know how you
imagine the driver selection based on connection uri.
You can simply use xen:///
as the URI. There is no need for configurable
URIs since thisis a xen specific script.
Daniel
--
|: Red Hat, Engineering, London -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://ovirt.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|