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/
Home Products Support Community News


[Xen-devel] xenstore reboot/crash watch

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xenstore reboot/crash watch
From: Ashwin Pankaj <ashwin.pankaj@xxxxxxx>
Date: Tue, 3 Nov 2009 15:50:45 +0530
Delivery-date: Tue, 03 Nov 2009 02:21:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090812)

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 <wpath>|<token>|?
             Adds a watch.

             <wpath> can be a <path> to watch or @<wspecial>.  In the
             latter case <wspecial> 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 <path> equal to <wpath>.  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,

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>