similar to: xenbus api

Hi I manage my hypervisor with HTTP protocol. The command : - POST /xend/node?op=shutdown HTTP/1.0 and - POST /xend/node?op=reboot HTTP/1.0 doesn''t seems to be active. Xend replies me a status code 200 (ok) but no reboot nor shutdown. Regards. Fabien Hermenier _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

The attached patch adds support for simple waiting for a watched key to change to a certain value. This patch is necessary for the netfront driver (separate patch). regards, Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch ports the Linux implementation of xenbus, in order to do that very simple threading support is introduced. Apart of that numerous fixes for 64 bit are included. Mini-os now compiles (for 64bit) but requires memory management and threading fixes before it works as well as 32bit version. Gregor _______________________________________________ Xen-devel mailing list

This implements a suggestion by Keir to remove the xenbus "ignore state transitions on shutdown" code for kernels without a shutdown callback. Signed-off-by: David Lively <dlively@virtualiron.com> Signed-off-by: Ben Guthro <bguthro@virtualrion.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I''m getting this error message when starting xend daemon: "XENBUS: Unable to read cpu state", but I''m not getting any warning or error while booting Dom0. Any idea on what could cause this ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

# HG changeset patch # User Paul Durrant <paul.durrant@citrix.com> # Date 1322574403 0 # Node ID 51692288a6e84c941f9e5049c73b7246bab97f70 # Parent e1e952982cf1d7a0c38a7822a8b5e78ba04b5ba5 Fix hvmloader xenbus segment array length. c/s acc408d667e1 had this one too short for handling a write. This incremental patch rectifies the problem. Signed-off-by: Paul Durrant

Hello everyone, Im testing *PV* with an *openSUSE 10.3 x64* guest machine (using a *SLES 10 SP1 x64 as host, Xen 3.0*) and when I created that guest machine everything went fine except when I rebooted the machine, this message appears when it''s loading drivers: "*XENBUS: Waiting for devices to initialise: 295s...* " and waits until the seconds pass and since it does not

Hi, there. I am running CentOS 4.4 on HVM Domain. And I tried Para-virtual driver for HVM Domain. Hunged up then "modprobe xenbus". My Domain-0 information: OS: CentOS 4.4 xen: 3.0.4.1 kernel: 2.6.16.33-xen_3.0.4.1 My HVM Domain information: OS: CentOS 4.4 Kernel: 2.6.9-42.0.10.EL PV Drv: xen-unstable.hg I traced the source code. I think problem at line:132 in xenbus_xs.c. It stopped

This patch is cleaning code in xenbus.c by VBD_SHOW macro. VBD_SHOW macro can be applied show functions with corresponded to ''physical_devices'' and ''mode'' attributes. And corresponding ''device_create_file'' and ''device_remove_file'' function can be inserted into ''xenvbd_sysfs_addif'' and

drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For guests compiled with CONFIG_SMP, smp_wmb and smp_mb would be sufficient, so mb() and wmb() here are only needed if a non-SMP guest runs on an SMP host. Switch to virt_xxx barriers which serve this exact purpose. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> ---

drivers/xen/xenbus/xenbus_comms.c uses full memory barriers to communicate with the other side. For guests compiled with CONFIG_SMP, smp_wmb and smp_mb would be sufficient, so mb() and wmb() here are only needed if a non-SMP guest runs on an SMP host. Switch to __smp_XXX barriers which serve this exact purpose. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- This is

Previously, I used to run 2.6.18 kernel built from Xen sources. I just tried to run a 2.6.25.1 domU kernel on top of Xen 3.2 - after changing domU''s config file here and there, I successfully booted the guest, but I''m still unable to use xm console. When I start the domain, it displays all kernel and bootup messages, but I don''t get any prompt after the bootup is

changeset: 7144:fe401301929e tag: tip user: emellor@ewan date: Fri Sep 30 08:59:28 2005 +0100 summary: Change rebooting specification so that we can have domains crash and stay make dist failed with above changset on FC4. make[3]: Entering directory `/media/sdb2/usr/src/redhat/SOURCES/xen-unstable.hg/linux-2.6.12-xen0'' CHK include/linux/version.h

Is it supposed to be possible to write to the same struct file instance from multiple threads/processes? Looking at xenbus_dev_write() I can''t see how such writes would be serialized, yet assuming that user mode code always writes full messages it would seem consistent to allow such. Thanks, Jan _______________________________________________ Xen-devel mailing list

Hi, In domU, we can''t use xenbus to access anything outside of the domain''s home. That means we are being restricted from reading/writing to other domain''s xenstore. That is perfectly fine, and nobody complains here. But in dom0, do we have the exception? Since dom0 is trusted, I think we can be allowed to access to all other domU''s xenstore. Is that

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> This is a patch to the xenbus_client.c file that fixed up whitespaces, tabs errors found by the checkpatch.pl tools. Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_client.c | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> This is a patch to the xenbus_client.c file that fixed up whitespaces, tabs errors found by the checkpatch.pl tools. Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_client.c | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> This is a patch to the xenbus_client.c file that fixed up whitespaces, tabs errors found by the checkpatch.pl tools. Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_client.c | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff --git

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using