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

[Xen-API] legacy vbds and new vdis

  • To: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
  • From: Jim Fehlig <jfehlig@xxxxxxxxxx>
  • Date: Tue, 08 May 2007 18:00:01 -0600
  • Delivery-date: Tue, 08 May 2007 16:58:28 -0700
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

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?


xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.