Displaying 20 results from an estimated 50000 matches similar to: "Can some help me about "xenstore-write"?"
2008 Jul 31
1
Can PV Guest use xenbus_printf to write information to xenstore?
Hi :
As I want to know the information of the VMs that currently runing on the
same physical machine, I''d like to get those VM''s information from xenstore,
such as macaddress. Indeed, what I want is IP address, so, if guest can
write things to xenstore, I''d like it write its IP address into xenstore and
let domain0 reads it directly.
So, can anybody tell me whether a PV
2012 Feb 02
0
xenstore-write: could not write path backend/vbd/1/2050/hotplug-error
After a few times of building xen by source, I can''t start domU anyway. I
tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again,
but the problem is still exist.
There are xenstore-write errors in /var/log/xen/xen-hotplug.log:
xenstore-write: could not write path backend/vbd/1/2050/hotplug-error
xenstore-write: could not write path
2010 Jul 12
0
xenstore-write segfault
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
2013 Jun 21
0
Xen Security Advisory 57 - libxl allows guest write access to sensitive console related xenstore keys
-----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
2012 May 29
1
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
Package: xcp-xapi
Version: 1.3.2-6
Severity: important
Tags: upstream
xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning.
This breaks 'dynamic memory control' feature.
Steps to reproduce:
1) Setup any PV virtual machine with static-memory-min < static-memory-max
2)
2011 Feb 08
0
[PATCH] libxl: allow guest to write "control/shutdown" xenstore node
# 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
2007 Dec 06
0
[PATCH] xen: Make xen-blkfront write its protocol ABI to xenstore
Frontends are expected to write their protocol ABI to xenstore. Since
the protocol ABI defaults to the backend's native ABI, things work
fine without that as long as the frontend's native ABI is identical to
the backend's native ABI. This is not the case for xen-blkfront
running 32-on-64, because its ABI differs between 32 and 64 bit, and
thus needs this fix.
Based on
2007 Dec 06
0
[PATCH] xen: Make xen-blkfront write its protocol ABI to xenstore
Frontends are expected to write their protocol ABI to xenstore. Since
the protocol ABI defaults to the backend's native ABI, things work
fine without that as long as the frontend's native ABI is identical to
the backend's native ABI. This is not the case for xen-blkfront
running 32-on-64, because its ABI differs between 32 and 64 bit, and
thus needs this fix.
Based on
2013 Jan 11
1
xenstore entry for "can migrate" or "can suspend"?
I''m looking for what I need to write to xenstore from a VM to say whether or
not it supports migration and/or suspension. On older versions of NetBSD,
suspend/migration isn''t supported and on newer versions it still has
issues. Therefore I want to let the XenServer toolstack, etc.
not offer the option to the end user.
--
Stephen
2012 Mar 23
2
Xenstore daemon is not running after boot; although can be started manually later. Any pointers why ?
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
2012 Mar 23
2
Xenstore daemon is not running after boot; although can be started manually later. Any pointers why ?
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
2013 Jul 06
1
[PATCH 1/2] xenstore: don't die on access-denied child nodes in 'xenstore ls'
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
2006 Aug 02
0
[PATCH] xenstore-chmod
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.
2012 May 03
1
Bug#640381: error xenstore-read: couldn't read path backend/vbd/6/768/node
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
2010 Aug 03
1
oops when access xenstore in hvm guest
Hi,
I use follow code get xenstore ring and event channel, then i wrapped writing and reading function to operate it ,but it came to oops:
struct xenstore_domain_interface {
char req[XENSTORE_RING_SIZE]; /* Requests to xenstore daemon. */
char rsp[XENSTORE_RING_SIZE]; /* Replies and async watch events. */
XENSTORE_RING_IDX req_cons, req_prod;
XENSTORE_RING_IDX rsp_cons,
2016 Mar 30
1
Re: Accessing xenstore from libvirt
Daniel P. Berrange wrote:
> On Wed, Mar 30, 2016 at 10:53:45AM +0200, Marin Bek wrote:
>> Hi,
>>
>> is it possible to access xenstore through libvirt? Or at least any other
>> programatic means other than calling xenstore-read/write through shell?
>>
>> I understand it is somewhat of a security risk but still...
>
> No, we don't expose this kind of
2012 Aug 24
2
Bug#666135: XenStore tdb vs. reboot
Hello,
I noticed a strace delay when running "virsh list" on my Xen-4.1.3 test
server. On further investigation I noticed that in XenStore there were
multiple /vm/$UUID entries suffixed by -$VERSION, especially I hat 16 entries
for my dom0. For each reboot of the host I get a new entry.
After disabling Xend I get the following output after a reboot:
> root at xen5:~# xenstore-ls
2012 Aug 24
2
Bug#666135: XenStore tdb vs. reboot
Hello,
I noticed a strace delay when running "virsh list" on my Xen-4.1.3 test
server. On further investigation I noticed that in XenStore there were
multiple /vm/$UUID entries suffixed by -$VERSION, especially I hat 16 entries
for my dom0. For each reboot of the host I get a new entry.
After disabling Xend I get the following output after a reboot:
> root at xen5:~# xenstore-ls
2012 Oct 22
0
access xenstore from Dom U
Hey, I am new to Xen. Recently I have some problems about using xenstore to
setup communication between Dom 0 and Dom U.
I have successfully installed Xen on Centos 6 and launch a Dom U with
Centos 5. "xm" and "virsh" works fine on my machine.
I can also use comments for xenstore to access values in Dom 0, such as
xenstore-list, xenstore-read, and xenstore-write. But I
2008 Apr 08
0
Allow xenstore client utilities to be built statically.
The attached patches enable the xenstore client utilities
(xenstore-read/write and friends) to be built statically and against
uclibc. This is useful for utility domains where a small userspace is
desired.
Both static building with glibc and linking with uclibc seem to have
problems with threading and so the static version of the library is
built without thread support. This is OK since none of