xen-api
Re: [Xen-API] legacy vbds and new vdis
If you use the new xm which creates stuff via the XenAPI, then a vdi
is created. If you look at tools/python/xen/xm/xenapi_create.py
theres code that basically already does this, but in xm.
If you want to put this into xend for the old api, then I think that
would be fine, but we're going to deprecate and eventually remove the
old SXP based interface.
Hope this helps
Tom
On 9 May 2007, at 01:00, Jim Fehlig wrote:
While moving the cim providers forward on new Xen API functionality I
come across a problem retrieving the uname information of a vbd.
If vbd
is created via Xen API, a vdi had to be created first and is
subsequently retrievable via vdi field of vbd record. However, if
a vm
is 'xm newed' or 'xm created' using a traditional conf file, vdis are
not created and hence not accessible via the vdi field of vbd. So
there
is no way to retrieve (via Xen API) the uname of device backing the
vbd.
I'm considering a patch that creates a 'default' vdi for each vbd when
vms are created outside of Xen API, but not convinced this is the
proper
solution. Suggestions before creating such a patch?
Regards,
Jim
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api
|
|
|