similar to: XenStore communication

Hi all, xend communicates with xenstored using unix domain sockets right? So, would it be possible to convert the unix domain sockets to tcp/ip sockets and let xenstored run on a different machine? Regards, Hayawardh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

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

On Thu, 2005-06-16 at 06:17 +0100, Keir Fraser wrote: > > I suggested that we simply mmap /dev/kmem for the xenstored to access > > the domain0 page for the moment. That doesn''t work: we''ll do something > > else. > > Just use xc_map_foreign_range(), as you would for mapping any other > domain''s xenstore page. So here''s my patch

Hi, I am using xen-4.1-testing with Linux 3.4.3. The hotplug script xencommons echoes that xenstore is not restartable. Can anyone tell me the exact reason why it is not restartable. I tried to restart xenstore by killing the xenstore and restarting it with xencommons but after that VM creation doesn''t work. I used to do the same with the setting <xen-3.4+Linux-2.6.18> and it used

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.

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

Hi, xenstore fails to build: init-xenstore-domain.c:11:32: error: xen/sys/xenbus_dev.h: No such file or directory init-xenstore-domain.c: In function ''build'': init-xenstore-domain.c:37: error: ''IOCTL_XENBUS_BACKEND_SETUP'' undeclared (first use in this function) Christoph -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH

Hi, for debugging purposes I would like to see the existing xenstore watches and the waiters for the watch. The problem is, we got a EEXIST from xenstored while trying to set a watch from our guest. Is there a possibility to see this on the running xenstored? Thanks. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html

Package: xen-utils-common Version: 4.0.0-1 Consider removal of xenstored tdb file (located at /var/lib/xenstored/tdb) before start of xenstored daemon during the boot (or removal during the shutdown/reboot of the server) as proposed by Ian Campbell during our discussions [1]. [1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00111.html -- Peter Viskup

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

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

Hi folks Some time ago I split out the xenstore utils out of the main utils package. I thought myself what could possibly be wrong and found nothing. I was wrong. Xen upstream decided to break the protocol between the client library and the daemon in a subtle way. This was compensated with a change in the daemon. Earlier versions of the library used the kernel access method as default. There is

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

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

As any other daemon, I''d assume it should be possible to restart xenstored (i.e. if it crashed or if, during development, a fix was made to it that needs to be tested). However, as I learned after over a day of digging, things don''t work anymore after doing so: Since the watches are transient, they''re lost with the daemon going away. Right now I specifically need this in

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

I''m looking at building a xenstore-based watchdog, as described at http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html However, being somewhat new to xenstore, I''d appreciate some pointers. - What portions of the xenstore namespace should I use? I''m looking for at least two settings writable by the DomUs: A flag to enable/disable the watchdog

Hans van Kranenburg writes ("Re: [PATCH 08/13] xen init script: rewrite xenstored start logic"): > So the question we should answer first is: What do we allow the user to > set as value? /bin/bash? And how should the init script deal with that? If they specify an absolute path, it should be used. Eg, /home/alice/Xen/xen/tools/xenstore/xenstore If the user specifies /bin/bash