similar to: Xenstore access permission to a specific domain

Which is the Kernel API (Xenbus API) that is available to do a similar action as "xenstore-chmod"?? Thx, Venkat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1322568055 0 # Node ID 6da8c30fb198adc15136a867a8303b7de3804bcf # Parent fa9deee858b84d4c4fbb5f9523fa5adb7aac3a35 docs: XenBus page has been transfered to new wiki Signed-off-by: Ian Campbell <Ian.Campbell@citrix.com> diff -r fa9deee858b8 -r 6da8c30fb198 docs/misc/xenstore.txt --- a/docs/misc/xenstore.txt Tue

Is it possible to create a custom directory tree inside Xenstore using any of the Xenstore-utilities?? For example, "/local/domain/0/Customdir". Thx, Venkat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

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

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

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

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.

Dear xen-devel, There''s a race condition in xenfs (xenstore driver) that causes userspace utility xenstore-watch to crash. Normally, the userspace process gets an "OK" from xenfs and then the watch fires immediately after. Occasionally, this happens the other way around: the watch fires before the driver sends "OK", which confuses the xenstore-watch client. It seems

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

Can the XenStore database be accessed by domU''s? If so, could it be used to pass small amounts of data back and forth between dom0 and domU''s using XenStore key entries? If this is possible, it would seem that this could eliminate the need to create a "device" driver for a simple communication path. Also, what type of Guest Fedora Kernel would be needed to

Hi, Can anyone please tell me how to get ".probe" function in "struct xenbus_driver" called? I want to do one simple test of event channel communication between peer modules of domU and dom0. I wrote one backend and one frontend driver (I tried registered as misc/blk/input device) where I put in all my xenbus routines, but cannot get .probe called after insmod my module, I

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

Hi, I want to know how everything communicates with XenStore. Do domUs use the front-end/back-end driver to dom0 and then the back-end driver contacts xenstored? In particular, how do the xenstore-* commands work on a dom0 and domU? And when should unix-domain sockets be used to communicate with xenstored? Thanks, Hayawardh _______________________________________________ Xen-users mailing

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

Hi, xenstore fails to build: init-xenstore-domain.c:11:32: error: xen/sys/xenbus_dev.h: No such file or directory init-xenstore-domain.c: In function ''build'': init-xenstore-domain.c:37: error: ''IOCTL_XENBUS_BACKEND_SETUP'' undeclared (first use in this function) Christoph -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH

Hi, Is there a way to change the permission for a specific path in XenStore? And can you do that from with in a C program? Thanks Julian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- hw/xen_disk.c | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git

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 -

Hi all, I think this is a serious bug, existing in the pvops 2.6.31.13 (also existing in linux 2.6.35); In the xenbus driver (drivers/xen/xenfs/xenbus.c), the function of xenbus_file_read has a section of source code like this: if (ret != sz) { if (i == 0) i = -EFAULT; goto out; } /* Clear