On Tue, Mar 23, 2010 at 02:22:24PM +0200, Pasi Kärkkäinen wrote:
On Mon, Mar 15, 2010 at 05:57:57PM +0000, Sharadha Prabhakar (3P)
wrote:
> Hi,
> I'm trying to write a Remote Storage driver for XenAPI.
>
For XAPI (used in XenServer and XCP), or for the old XenAPI used in the traditional
Xen/xend?
Never mind, I was reading the virt-tools list before reading libvirt-list :)
-- Pasi
> I see that target-path is used for both storage pools and volumes.
> In the case of XenAPI remote storage, the storage is not mounted on the
> local host where libvirt is running. Storage is maintained in a remote location
only.
> In this case how do I specify target-path and how do I go about creating
> a VM with storage using libvirt APIs with virsh and virt-manager.
> Virt-manager expects me to give an absolute path for target-path. But In my case
> I don't have an absolute path.
> Can I have a target path like this for a particular storage volume
> "/storage pool uuid/storage-vol uuid"? This will help me identify which
storage pool is
> Libvirt talking about and which volume in it. Using this information I can fetch
data from
> The remote location and give it back to libvirt. Is this approach
> ok or does libvirt support my specific remote storage case in some way. Could
someone
> clarify please?
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list