similar to: question on xenbus priv in dom0

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!''

Hi, I am writing a small application to watch for xenstore events. I want to know when a specific domain shutdown or reboot. It is best to watch it via xenbus interface, but how? Is there any event or node can give me such an event? If not, I must periodically scan the domains (using libxc interface) to detect if a domain dies, but that is not as good as xenbus approach. Many thanks. Hieu

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.

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

# 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

Hello I have a lot of problem using the xenbus api (in xen-3.0-testing). I had to modify the network backend driver (file netback.c), and each call to a xenbus function in a virtual machine make my machine reboot (not the virtual, the real machine). for example, I ''ve add this line of code (wich is useless):

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

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

Hi, Anybody please tell me how to have a PV Linux with graphics? I succesfully created some PV Linux with debootstrap and xen-tools. But then all the images must be started with "xm create -c" command, and everything then is console, with no X Window. In short, I want to have PV Linux, but with X. How to do that? Thanks, H _______________________________________________ Xen-users

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

Hi, This patch series fixes the S3 resume of a domain running xenstored and a frontend over xenbus (xen-netfront in my use case). As device resume is happening before process resume, the xenbus frontend resume is hanging if xenstored is not running, thus causing a deadlock. This patch series is fixing that issue by deferring the xenbus frontend resume when we are running xenstored in that same

hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT

The attached patch: 1. Converts the shutdown driver and xend to use the store instead of control messages, 2. Includes Anthony''s xenstore notification code, and 3. Changes xend so that sysrq''s are no longer sent as "special case" shutdown messages. Store keys are cheap, so making the sysrq delivery less obscure is good. I think I have made all of the

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

Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel <david.vrabel at citrix.com>wrote: > > On 05/03/14 15:09, Karl Johnson wrote: > > > I've been using Xen4CentOS for the last 3 months. It's working fine and > > > dom0/domUs are stable but the server does a kernel panic when doing a > > >