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

Re: [Xen-devel] Q: How to find own domid or uuid from domU?


  • To: "Andrew D. Ball" <aball@xxxxxxxxxx>
  • From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
  • Date: Thu, 18 May 2006 17:59:51 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 18 May 2006 10:00:13 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LWNFwF+OpvvBnU69F4fKqjkN7lUPIz0zLwdpJ2IHA01e2ngoGIDlwmsHSrUvoadQHLlcMwjZawmOJYfrCKlAy321FhAhvl2zAM/wGzh1/iznQnqgNu31J7fWbv2+2fIe2NKKVzPDamf20ACdSL97PMyESilTeiAqLL1rCOgPTI4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 5/18/06, Andrew D. Ball <aball@xxxxxxxxxx> wrote:
Good!  I've been strapped for time, but will eventually get around to it
perhaps.  Mike Day's been doing excellent work on it.

I think it would be nice if the attribute were called uuid and not vm
with "/vm/" prepended.  I suppose it's fine to keep "vm" as a shortcut,
but a separate UUID attribute is more important, IMHO.

There's a uuid node under the vm path.  I.e. you'd do:
vmpath=$(xenstore-read vm)
uuid=$(xenstore-read $vmpath/uuid)

I think exposing this through sysfs would be wrong, there's no need to
make the kernel aware of any of this.

   christian

_______________________________________________
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®.