similar to: xenstored segfault

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Tags: squeeze I have 3 VM running. I have upgraded debian squeeze to 6.0.1 (new kernel package 2.6.32-31) and restarted my server. VM were still running. After reboot I could not start xend service (from init.d). I got following errors: kern.log: Mar 22 15:07:30 router kernel: [53888.212756] xenstored[7232]: segfault at 7fff056b5ff8 ip

Hi, I''d be very interested to hear: does anyone have a stable working amd64 machine (in 64bit mode)? if so, which kernel do you use, and which version of xen / hg tree do you use? linux-2.6-xen.hg compiles fine over here, but reboots during boot. so fast I can''t see anything. (sorry, my laptop has no serial port. so I can''t capture a log file.) 2.6.16-rc4-git8 plus

Waay back at the end of 3.0.3 dev cycle I brought up the issue of XenD running far too many xenstore transactions per-request http://lists.xensource.com/archives/html/xen-devel/2006-10/msg00487.html Short summary: # nc -U /var/lib/xend/xend-socket GET /xend/domain/test Resulted in approx 16 xenstore transactions for a domain with one disk and one NIC - this increases as # of devices

I''ve been trying to track down just why talking to XenD is resulting in so much CPU time being comsumed by both xend & xenstored. As a test case, I''m running ''virsh dominfo demo'' which results in a single HTTP request to Xend to fetch domain info, eg ''GET /xend/domains/demo'' Run this in a tight loop & I''ll see xenstored

Hi, My base system is Gentoo x64, and I compiled my kernel with Xen paravirtualization support. The kernel can boot without any problem in native mode. But when boot in Xen mode, I cannot start the xenstored service. This is my grub config file: title Gentoo x64 kernel-3.2.11-gentoo root (hd0,2) kernel /boot/kernel-3.2.11-gentoo root=UUID=38213e99-588e-4a7d-a215-8835f7afb1c4\

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

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, xend start should test for /var/run/xenstored before running xenstored. on (k)ubuntu at least /var/run is a tmpfs, so after each reboot it is empty and you need to re-create all directories. a simple test -e ... || mkdir ... would prevent people from running into problems. maybe this is simple enought to get into xen-unstable before 3.0.2? Thanks, Andreas

Package: xen-utils-4.0 Version: 4.0.1-2 Hi, When you change XENCONSOLED_ARGS in /etc/default/xend, there's no normal way to apply it. Even if you do '/etc/init.d/xend stop', that doesn't stop xenconsoled, despite the fact the analogous 'start' action did start it. There isn't even a separate init script action to stop it, it has to be killed manually. Same goes for

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

Hans van Kranenburg writes ("[PATCH 08/13] xen init script: rewrite xenstored start logic"): > -XENSTORED="$ROOT"/bin/xenstored > +# In /etc/default/xen, the user can set XENSTORED, which has to be either > +# 'xenstored' or 'oxenstored'. In here, we add the version specific path. > +if [ -n "$XENSTORED" ]; then > +

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

On Thu, Jun 4, 2015 at 11:57 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Thu, Jun 4, 2015 at 6:03 AM, Sarah Newman <srn at prgmr.com> wrote: >> By default, /var/lib/xenstored is mounted tmpfs in centos 5 but this doesn't appear to be true for Xen4CentOS. This can cause performance issues as >> mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=446089

On Thu, Jun 4, 2015 at 6:03 AM, Sarah Newman <srn at prgmr.com> wrote: > By default, /var/lib/xenstored is mounted tmpfs in centos 5 but this doesn't appear to be true for Xen4CentOS. This can cause performance issues as > mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=446089 > > I'm not sure if this should be part of xencommons, but if not, adding a tmpfs mount

Hi All, I just tried a new installation of Ubuntu 10.04 (64bit) + Xen and am having some trouble starting XEN. I am using the latest mercurial checkout (4.0.2-rc2) and the only change I made was to Config.mk to enable building the OCAML version of xenstored. " CONFIG_OCAML_XENSTORED ?= y". I am using the same kernel I built earlier for a similar Ubuntu 10.04-64bit / Xen 4.0.0

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

Package: xen-utils-4.1 Version: 4.1.3-4 Severity: important Tags: patch Bug presented in sid, with patch attached. Similar bug is also present in stable and testing versions. How to reproduce: Install xen-utils-4.1 in a domU, and run: /etc/init.d/xen start Expected result: xenstored running (or to have any other easy way to get it running within a domU) xenstored is not just something

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal There should be a clean and clearly defined way to restart all the Xen daemons in the case of error. If the file /var/lib/xenstored/tdb is corrupt then you must stop xenstored, rm the file, and then restart it. Currently there is no defined way of doing this so the solution is to kill -9 the process, rm the file, and then reboot. --

Hello Andreas, On 10/11/05, Andreas Jellinghaus <aj at dungeon.inka.de> wrote: > Peter Koch pointed me to your posting on openssh-devel mailing list. I am very glad that he did. > I'm one of the opensc people, and from my point of view your idea > is a good one. The current openssh-opensc code has a number of issues, > for example the ssh-agent does not test the pin

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is