Hi guys,
from file XendVDI.py:
class XendQCoWVDI(XendVDI):
def __init__(self, uuid, sr_uuid, qcow_path, cfg_path, vsize, psize):
XendVDI.__init__(self, uuid, sr_uuid)
self.auto_save = False
self.qcow_path = qcow_path
self.cfg_path = cfg_path
self.physical_utilisation = psize
self.virtual_size = vsize
self.auto_save = True
self.other_config['location'] = 'tap:qcow:%s' % self.qcow_path
def get_location(self):
return self.other_config['location']
class XendLocalVDI(XendVDI):
def __init__(self, vdi_struct):
vdi_uuid = vdi_struct['uuid']
sr_uuid = vdi_struct['SR']
XendVDI.__init__(self, vdi_uuid, sr_uuid)
self.auto_save = False
self.cfg_path = None
self.name_label = vdi_struct.get('name_label','')
self.name_description = vdi_struct.get('name_description', '')
self.physical_utilisation = 0
self.virtual_size = 0
self.type = vdi_struct.get('type', '')
self.sharable = vdi_struct.get('sharable', False)
self.read_only = vdi_struct.get('read_only', False)
self.other_config = vdi_struct.get('other_config', {})
As you can see no physical utilisation and virtual size value in local
repository. So, how could it possible to check vdi size?
Thanks,
Dante
On Wed, May 5, 2010 at 1:42 PM, Dante <[email protected]> wrote:
> Hello guys,
> I'm working on a cloud computing project involving Xen Hypervisor. I
> looked for the issue described in the subject in old posts but no success.
> I'm using the local storage repository and I can't set physical_utilisation
> and virtual_utilisation via xen API because XendVDI.py has hardcoded the 0
> value for local repository while is passed for QcoW storage repoistory.
> Any reason why is VDI implemented in this way? I have to use a
> workaround and set size in description field to retrieve this information
> but it's quite annoying since there is a field dedicated to it.
> Posting this question in both xen-devel and xen-api mailing list. I
> think the question is cross-mailing-list. Sorry for duplication.
>
> Thanks in advance for your help!
> Dante
>
_______________________________________________
xen-api mailing list
[email protected]
http://lists.xensource.com/mailman/listinfo/xen-api
