similar to: Ill-advised use of xs_open flag 1UL<<2 by Debian

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

XenStore puts in queued watch events via a thread and notifies the user. Sometimes xs_unwatch is called before all related message is read. The use case is non-threaded libevent, we have two event A and B: - Event A will destroy something and call xs_unwatch; - Event B is used to notify that a node has changed in XenStore. As the event is called one by one, event A can be handled before

Hi everyone, I''m trying to start up domU on xen for ARM (Cortex-A15 Fast models). I follow the instructions to build xen-tools with this link: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling. But there seems to be something wrong when I start up domU. First, I get errors in create domU with xl: root@(none):/home/xiaogw# xl create domU-config xc: error:

While on entry to xs_unwatch, there may be an event on its way from xenstored (eg in the ring or in the local kernel), all such events will definitely come before the reply to the unwatch command. So at the point where the unwatch reply has been processed (after xs_talkv), any such now-deleted watch events will definitely have made it to libxenstore''s queue where we can remove them. As

Source: xen Version: 4.17.3+10-g091466ba55-1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-arm at lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond

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

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.

Processing commands for control at bugs.debian.org: > forcemerge 644125 466683 Bug #644125 [xenstore-utils] xenstore-utils has completely inadequate description Bug #466683 [xenstore-utils] xenstore-utils: The package description doesn't say what the utilities contained in the package are for. Severity set to 'normal' from 'minor' Marked as found in versions xen/4.0.1-2.

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

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

tags 466683 +patch thanks commit 765ac4708e4dd8a6fea0028d631a7c3363b286b7 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 10:30:17 2013 +0100 * debian/changelog: Update * debian/templates/control.main.in: Update descriptions for some packages. diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..e5b25ef 100644 --- a/xen/debian/changelog +++

Hey! I am following the steps at http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM. I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box has 12GB of physical memory and runs Ubuntu 13.04. When I do "xe vm-start", I get the following: The server failed to handle

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

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

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

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

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,

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

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