From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: xenstore reboot/crash watch Date: Wed, 04 Nov 2009 11:12:55 +0000 Message-ID: <4AF161B7.90809@eu.citrix.com> References: <4AF003FD.4080902@lsi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AF003FD.4080902@lsi.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ashwin Pankaj Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Ashwin Pankaj wrote: > Hi, > > I tried googling this one - but documentation on @releaseDomain key in > xenstore seems scanty. > > 1. If a client registers a watch for this key - does it get called > every time a domain restarts / crashes ? > yes > 2. Why can't xenstore-ls, xenstore-read et al "see" this key ? > this is not a database key. this is just a special event. > So would the following python code register watch for restart > events of ANY domain - 'watch = xswatch("@releaseDomain", > watch_func, xshandle())' ? > yes it seems right. but it's not a restart event, the event is there to notify that one or multiple domain(s) are dead. -- Vincent