similar to: xenstore situation

I''ve seen some people asking why exposing xenstore attributes via sysfs could be useful. Here''s why I would really like to see such a patch make it into Xen: I''ve been working on getting domU''s to know enough about themselves to be manageable. I require a 128-bit UUID for each domU, and I require that each domU be able to determine its own UUID in userspace.

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

While on entry to xs_unwatch, there may be an event on its way from xenstored (eg in the ring or in the local kernel), all such events will definitely come before the reply to the unwatch command. So at the point where the unwatch reply has been processed (after xs_talkv), any such now-deleted watch events will definitely have made it to libxenstore''s queue where we can remove them. As

Hi, Anybody (Christian?) could please tell me if we can get the support for registering watch with /proc/xen/xenbus? (..OK, I know that we will change it this /proc stuff to a device soon) So far we can only do read/write/rm. I really miss the xen watch feature. Many thanks, Hieu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This allows tools in the python directory to properly link to libxenstore.a on x86-64. --- tools/xenstore/Makefile.orig 2005-06-09 12:56:34.000000000 -0500 +++ tools/xenstore/Makefile 2005-06-09 13:48:06.000000000 -0500 @@ -20,6 +20,9 @@ BASECFLAGS+= -I. CFLAGS+=$(BASECFLAGS) +ifeq ($(XEN_TARGET_ARCH),x86_64) +CFLAGS += -fPIC +endif LDFLAGS=$(PROFILE) -L$(XEN_LIBXC)

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

Added two new sets of compile flags, and pass them to the check scripts, so libraries and includes are searched there also. Resend this patches because they suffered some modifications and where scattered along the mailing list. Please review, thanks Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On Thu, 2005-06-16 at 06:17 +0100, Keir Fraser wrote: > > I suggested that we simply mmap /dev/kmem for the xenstored to access > > the domain0 page for the moment. That doesn''t work: we''ll do something > > else. > > Just use xc_map_foreign_range(), as you would for mapping any other > domain''s xenstore page. So here''s my patch

Hey Keir, I committed the last of the big outstanding tools blockers for 4.2 yesterday. Currently they are still in staging because they added some new xenstore paths which tickled the leak detector in the test system What do you think of doing an rc0 release next week? There''s still some smaller issues remaining but I think they can wait until rc1. Ian.

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

Signed-off-by: Jerone Young <jyoung5@us.ibm.com> -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi folks Some proposed changes: * Fixiate the API/ABI of some libs, for the stable version, including - libxenctrl, - libxenstat, - libxenstore. As upstream don't know what abinames are for, roll own abinames. * Add libxenctrlX, libxenstatX, libxenstoreX, if abinames may be different or libxenX if the abinames should the same for all libs. * Add libxen-dev including - static

Package: xen-utils-common Version: 4.0.0-1 Consider removal of xenstored tdb file (located at /var/lib/xenstored/tdb) before start of xenstored daemon during the boot (or removal during the shutdown/reboot of the server) as proposed by Ian Campbell during our discussions [1]. [1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00111.html -- Peter Viskup

tags 466683 +patch thanks commit 765ac4708e4dd8a6fea0028d631a7c3363b286b7 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 10:30:17 2013 +0100 * debian/changelog: Update * debian/templates/control.main.in: Update descriptions for some packages. diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..e5b25ef 100644 --- a/xen/debian/changelog +++

Ian Campbell wrote: > + * Expand on the descriptions of some packages. (Closes: #466683) Trivial typo here: > Package: libxen-dev > Section: libdevel > Depends: libxen- at version@ (= ${binary:Version}), libxenstore3.0 (= ${binary:Version}), ${misc:Depends} > Description: Public headers and libs for Xen > This package contains the public headers and static libraries for

Hi, I am using xen-4.1-testing with Linux 3.4.3. The hotplug script xencommons echoes that xenstore is not restartable. Can anyone tell me the exact reason why it is not restartable. I tried to restart xenstore by killing the xenstore and restarting it with xencommons but after that VM creation doesn''t work. I used to do the same with the setting <xen-3.4+Linux-2.6.18> and it used

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

Hi, for debugging purposes I would like to see the existing xenstore watches and the waiters for the watch. The problem is, we got a EEXIST from xenstored while trying to set a watch from our guest. Is there a possibility to see this on the running xenstored? Thanks. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to