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

Re: [Xen-devel] xenstore -- read UUID


  • To: "dinesh chandrasekaran" <dinesh_chan8@xxxxxxxxxxx>
  • From: "Geoffrey Lefebvre" <geoffrey@xxxxxxxxx>
  • Date: Thu, 11 Sep 2008 14:28:37 -0700
  • Cc: xen developers community <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen users community <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 11 Sep 2008 14:29:00 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ctxHnLUzrLfpYVq3ZHn3rexG8CJt+xbWBrMWSZTx2lpcnC4VCrxm0886MZxYoxXVKJ xwHRqwIzBX9jUIjwI522XvCRTGTBNZn5irsYDtd/AbwPDgb4xWwintWwkJC46nXHOJNx 72hRRwqrFj2AuZmEWm1pJuekgwVCn6NiUjpwQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> Hi geoffrey,
>                 the xen_domain_handle_t in the domain handle field is an
> unsigned char array of size 16.
> Where could the UUID be accessed from?
> or how would you relate the d->handle to the domain's uuid (where d is of
> type struct domain *d).
> is all the 16 entries in the d->handle clubbed together to get the domain's
> uuid?
>

Hi dinesh,

d->handle contains the domain uuid.

A uuid is a 16 byte number. Xen and libuuid store uuids as 16 byte
char array. They both define typedefs (xen_domain_handle_t and uuid_t
respectively)  for a 16 byte char array.

If you want to generate a human readable version, you can use
uuid_unparse to generate a 37 character C string from the uuid_t.

Hope this helps.

geoffrey

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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