WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] VDI size on local repository always 0

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] VDI size on local repository always 0
From: Dante <dantespace.ml@xxxxxxxxx>
Date: Wed, 5 May 2010 13:42:24 +0200
Delivery-date: Wed, 05 May 2010 04:42:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Ym+PPq64DMKAgRJULsNdbl5Ie3A2y2MpR81NXCwzuoM=; b=JDrfKvl8fdHC9pRZ3lO5/vXBuRU8zyMhmLSmynzkhssrVb0wDhj+Si2H6NSTIhqFIz PpC3HiwljgatIZK4hZLSI4RDESFtiOOuiDVkpO0sa+JEFLIw9KXTXmBR8ZjYvfhhzNCO htRY3WtdfL7/M4CLoPVQbu7tye5X+rH/kv8NY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VW3sI7xqUy0cFwA2RrvOg/haWio/DHhqZffhGA7R0tIUVR85FGmS6WMV2RJE2zCHTf CyfLUzcJRWb9+ieFfc3SU676T4UwiE7FYqaeNBXYzA9jQVmha7fbPTgrzyeepMHynuvn 6ZYaIDyGjdRHhyRVDUHZsIsjN9UiI2AwejWOg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
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
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>