similar to: Allow xenstore client utilities to be built statically.

Signed-off-by: Matthew Daley <mattjd@gmail.com> --- tools/xenstore/xenstore_client.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/tools/xenstore/xenstore_client.c b/tools/xenstore/xenstore_client.c index 3ac214b..996ee64 100644 --- a/tools/xenstore/xenstore_client.c +++ b/tools/xenstore/xenstore_client.c @@ -134,8 +134,13 @@ static void do_ls(struct

Hello, I''ve modified tools/xenstore/xenstore_client.c to include a new utility, xenstore-chmod. This utility permits developers and administrators to manually change the permissions on arbitrary locations in XenStore from the command line. This is often helpful if you''re trying to debug an application that relies on XenStore and is encountering difficulties with permissions.

The entries in xenstore have permission attributes. The attributes can be easily altered by xenstore-chmod, however, I cannot find a easy way to see them. I''ve modified xenstore_client.c to raise a new utility. The utility checks the permission and makes an easy-look output. Please tell me any suggestions. Thanks. Signed-off-by: Frank Pan <frankpzh@gmail.com> ---

When i try to compile xen 3.0-devel with "make world", i''ve got the following compile error: gcc -m32 -march=i686 -Wall -W -g -Wp,-MD,.xenstore_read.o.d -I../../tools/libx c -I../../xen/include/public -I../../xen/include/public -I../../linux-2.6-xen-sp arse/include/asm-xen/linux-public -c -DCLIENT_read -o xenstore_read.o xenstore _client.c xenstore_client.c:16:16: xs.h: No

Package: xenstore-utils Version: 3.2.0-3 Severity: minor Description: Xenstore utilities for Xen This package contains the Xenstore utilities. I would hope that there would be a more descriptive description for this package, so I could know if I really need it. (Yes, I'm a newbie to the world of XENU ... I suppose I would already know if I wasn't new to this.) -- System Information:

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

# HG changeset patch # User Rusty Russell <rusty@rustcorp.com.au> # Node ID b0de1894df67ac7c7d905bf61cdf0210b42752cc # Parent ba5d5bd28edf8bce89bdf9fc64047ee4f1dceded Xenstore watch rework Change watches to all fire simultaneously, removing priority argument. Watches no longer fired back to connection/domain which caused event. Fix up testsuite to match Use state enum, rather than return

# HG changeset patch # User john.levon@sun.com # Date 1161090130 25200 # Node ID afeef751f9dafa771726bcfb00b29a10b0baeabd # Parent 7147e57f18552bbb8d25155cc1c635315283ee31 On Solaris, GCC is configured to use Sun''s LD. Fix the build to use the correct flags, and link against libsocket where necessary. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/config/Linux.mk

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

Hello, This patch allows userspace tools on a domU to setup a watch on the xenstore. It does this by intercepting XS_WATCH requests written to /proc/xen/xenbus and then re-submitting the request to the in-kernel xenstore interface, in linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c. When a callback occurs, an in-kernel function is invoked, which then reconstructs a response in the format

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1297182367 0 # Node ID a46b91cd8202726aecd9ddefd8e75faff48144d6 # Parent deaa7bc1a7ff6cfad7865394cb8b7205741004c9 libxl: allow guest to write "control/shutdown" xenstore node. The PV shutdown/reboot/suspend protocol requires that the guest acknowledge a request by clearing the node therefore it is necessary

Package: xenstore-utils Version: 4.0.1-2 all it says is: "Description: Xenstore utilities for Xen This package contains the Xenstore utilities." Wow, i never would have guessed that a package called xenstore-utils might contain Xenstore utilities. I'm glad that's cleared up! that just leaves a few tiny, niggling questions: 1. WTF are the Xenstore utilities? 2. What are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory XSA-57 version 3 libxl allows guest write access to sensitive console related xenstore keys UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= The libxenlight (libxl) toolstack library does not correctly set permissions on

Package: xenstore-utils Version: 4.17.0+74-g3eac216e6e-1 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m15.9s ERROR: FAIL: Broken symlinks: /usr/bin/xenstore-control -> ../lib/xen-common/bin/xen-utils-wrapper (xenstore-utils) cheers, Andreas

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

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.

I''m looking at building a xenstore-based watchdog, as described at http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html However, being somewhat new to xenstore, I''d appreciate some pointers. - What portions of the xenstore namespace should I use? I''m looking for at least two settings writable by the DomUs: A flag to enable/disable the watchdog

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: grave Justification: renders package unusable This packages should depend on the 3.4 version of xenstore utils and library, because it the Lenny versions are installed, xend crashes instead of starting up. (Many users choose to run lenny/sid hybrid systems, with lenny as default, so it's completely plausible that the wrong package will be

tail /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vbd/6/768/node /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected xenstore-read: couldn't read path backend/vbd/6/5632/node xenstore-read: couldn't read path backend/vbd/6/768/node

Hi All , I am using xen 3.2.0 which i have built form source ,I could initially boot Dom 0 and some DomUs. But today when i tried to boot a DomU with birdge enabled it didnt work giving an error .... Error: Device 0 (vif) could not be connected. Hotplug scripts not working. After that I checked my var/log/messages and It gave lots of xenstore-write