similar to: XenStore path entries

Hi friends, I''m developing an architecture using xenbus/xenstore that use DomID to read/write informations over a shared memory with dom0. But always that i restart my DomUs the DomID is increased. I''d like to use always the same DomID for the VMs. Any option? Thanks -- Luciano Barreto _______________________________________________ Xen-users mailing list

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

Hi, Currently libxl removes entries from xenstore "device/" tree only in case of: a) domain destroy (clean all domain directory) b) dom0-initiated device remove But this doesn''t cover all the cases. At least this isn''t done: a) backend domain shutdown, backend-initiated remove b) backend domain destroy (here backend driver doesn''t have chance to signal

On Thu, 11 Apr 2013, Ian Campbell wrote: > On Thu, 2013-04-11 at 05:09 +0100, Jim Fehlig wrote: > > > + /* This will fill xenstore info about free and dom0 memory - if missing, > > > + * should be called before starting first domain */ > > > + if (libxl_get_free_memory(libxl_driver->ctx, &free_mem)) { > > > + VIR_ERROR(_("cannot

This patch (fundamentally) adds support to display the full contents of the xenstore directory entries. During some recent testing, the values of interest were always beyond the ..., so I added -w to override truncation. There is a bit of code cleanup as well (snprintf vs. sprintf), one formatting fix, and comments). There is no change to the behavior of xenstore-ls without -w.

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

On Thu, 2013-04-11 at 05:09 +0100, Jim Fehlig wrote: > > + /* This will fill xenstore info about free and dom0 memory - if missing, > > + * should be called before starting first domain */ > > + if (libxl_get_free_memory(libxl_driver->ctx, &free_mem)) { > > + VIR_ERROR(_("cannot get free memory info")); > > + goto error; >

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

Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some information here but none was helpfull to me. Anyone? I have 4GB memory and a AMD Turion II X2 M500 (

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When starting (or migrating in) a domain, sometimes I get the following exception: [2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain

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

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

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

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

Package: xenstore-utils Version: 4.0.1-2 all it says is: "Description: Xenstore utilities for Xen This package contains the Xenstore utilities." Wow, i never would have guessed that a package called xenstore-utils might contain Xenstore utilities. I'm glad that's cleared up! that just leaves a few tiny, niggling questions: 1. WTF are the Xenstore utilities? 2. What are

Hi, I encountered a problem while porting Solaris as a guest OS on Xen. The problem I found is that when frontend vbd driver get unloaded, it will close the vbd interface by changing the state to XenbusStateClosed. This appears to cause the dom0 hotplug scripts to remove the vbd entry from xenstore for the domU guest, preventing the vbd from being re-attached. So, my questions are: + This

Hey everyone, I''m trying to write a simple python program in dom0 that registers a watch on the xenstore to determine when a domU has shutdown. Is there a particular token I should use? Looking through the tools/python/xen/*.py code, I''ve come across the ''control/shutdown'' token... seems promising? My code is attached below. As is, if fails to call the

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

Hello, After creating and destroying a number of domUs, I noticed that /local/domain/0/backend starts to get cluttered when using XL. The vif, vfb, vkbd, and vbd sections look like this: 270 = "" 271 = "" 272 = "" 273 = "" 274 = "" 275 = "" Where the dom ID is set to an empty value, however the console