From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ashwin Pankaj Subject: xenstore reboot/crash watch Date: Tue, 3 Nov 2009 15:50:45 +0530 Message-ID: <4AF003FD.4080902@lsi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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 ? 2. Why can't xenstore-ls, xenstore-read et al "see" this key ? 3. docs/misc/xenstore.txt has this to say - "WATCH ||? Adds a watch. can be a to watch or @. In the latter case may have any syntax but it matches (according to the rules above) only the following special events which are invented by xenstored: @introduceDomain occurs on INTRODUCE @releaseDomain occurs on any domain crash or shutdown, and also on RELEASE and domain destruction When a watch is first set up it is triggered once straight away, with equal to . Watches may be triggered spuriously. The tx_id in a WATCH request is ignored." So would the following python code register watch for restart events of ANY domain - 'watch = xswatch("@releaseDomain", watch_func, xshandle())' ? - Regards, Ashwin