similar to: /var/lib/xenstored & Xen4CentOS

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

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

I think this may have been asked before, but what would it take to get debuginfo packages built for the Xen4CentOS kernels? If it's just a patch for kernel.spec file that nobody has gotten around to, what is the best starting place for making that patch? Thanks, Sarah

The contents are the wip.testme branch currently on salsa. I combined the wip.initscript and wip.oxenstored into this and added more things today. I think this is pretty gtg and it's smoke tested (in several cases by scping files around instead of doing package build), so it needs a final extra review and test round before putting it in master branch (which I don't want to force push). I

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag on disks with qemu-xen" has been applied to Xen4CentOS. I assume this was on purpose? If not, I can have someone try adding the original patch from http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b

Hans van Kranenburg writes ("[PATCH 06/13] sysconfig.xencommons.in: Strip and debianize"): > Strip all options that are for stuff we don't ship, which is 1) > xenstored as stubdom and 2) xenbackendd, which seems to be dead code > anyway. [1] > > It seems useful to give the user the option to revert to xenstored > instead of the default oxenstored if they really

YaST2 sysconfig can logically group the various sysconfig settings if the files are tagged. Add the missing (YaST specific) tags to xencommons. See for a description http://old-en.opensuse.org/Packaging/SUSE_Package_Conventions/Sysconfig Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Resending: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01140.html

On 03/10/2016 12:05 AM, Sarah Newman wrote: > On 03/09/2016 08:15 PM, Sarah Newman wrote: >> I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups >> within the last 24 hours. I am posting here first in case anyone else has experienced the same issue. >> > > Here is mpstat

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

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

hi guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

hi guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

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

When a message with zero length is sent to xenstore, the body of the message was not processed until the socket or ring had more data to read; this will cause deadlocks if the requestor is waiting on a response to continue. Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov> --- tools/xenstore/xenstored_core.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git

The mystery gets more interesting... I now have a CentOS 7.3 Dell R710 server doing the exact same thing of rebooting immediately after the Xen kernel load. Just to note this is a second system and not just the first system with an update. I hope I'm not introducing something odd. They only "interesting" thing I have done for historical reasons is to change the following

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

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

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