similar to: Report on Xen-4.6rc2 from virt7-xen-46-candidate

On Tue, Sep 8, 2015 at 11:25 PM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > Hi > > I gave the new Xen-4.6rc2 a spin on a CentOS 7 virtualisation guest > (nested-xen). I haven't yet started testing guests, but rather looked at the > install itself. > > One issue, I found, was with xenstored.service and the corresponding > unit-file: > > [root at

Hey, What do you mean by doesn't do forking? It allows forking processes if the application can do that. It doesn't fork them by default but ,is it really needed? If xenstored is testing to be run under systemd and not forks itself because of it, that's another thing. Eliezer On 09/09/2015 12:40, George Dunlap wrote: > I think because systemd doesn't do forking, that it

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

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

On Wed, Sep 9, 2015 at 12:25 PM, Eliezer Croitoru <eliezer at ngtech.co.il> wrote: > Hey, > > What do you mean by doesn't do forking? > It allows forking processes if the application can do that. > It doesn't fork them by default but ,is it really needed? > If xenstored is testing to be run under systemd and not forks itself because > of it, that's another

Hi all, i just stumbled over a strange performance issue with my Xen setup. I use centos-virt Xen since a long time on my workstation and usually never check performance. However, yesterday I booted into the 3.18.25-19 Dom0 kernel *without* Xen and found the system noticably more responsive. That triggered me into running a simple kernel compile benchmark and compare the results:

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

Package: xen-utils-common Version: 4.4.1-9+deb8u4 Severity: normal Dear Maintainer, I have a server with a large number of domUs set to auto-start. For the first time I have booted it with all of them needing to start from cold, but the xendomains service only got part way through. syslog showed nothing notable about the domains starting? Apr 16 14:57:45 snaps xendomains[4631]: Starting

On Mon, Sep 7, 2015 at 11:02 PM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > First of all, I fully agree, that forked repos are undesirable. However, to > the casual observer (like me), there are hardly any ressources for Xen on > CentOS 7. There are some beta packages, as announced in the start if this > thread, with the latest update being 4.4.2 on 4th of august. I

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

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access

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

Package: xen-utils-common Version: 4.4.1-2 Severity: normal For correct operation under SE Linux the start script needs to assign correct security labels to firectories it creates. Note that restorcon doesn't cause any problems if run twice. If it's executable then you can safely run it. Below is a patch that demonstrates how to solve this problem. --- xen.old 2014-10-12

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

Greeting, We are about to update the centos-release-xen package to point to Xen 4.8 rather than 4.6. I'll push the update next week. As a reminder, you can "pin" your installation to Xen 4.6 by installing centos-release-xen-46 and then removing centos-release-xen. And for the more adventurous, that update will come with a new package centos-release-xen-410 to install Xen 4.10.

At long last, I'd like to announce beta packages for CentOS 7, available from the community build system. Start by installing the centos-release-xen: rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-3.el7.x86_64.rpm This will set up yum repositories for both the eventual release repositories (enabled by default), and the community build

On 09/04/2015 04:39 PM, T.Weyergraf wrote: > > > On 09/03/2015 09:50 PM, Chuck Meade wrote: >> Hi Thomas, > Hi Chuck >> >> This may be old news at this point, but I had 100% identical behavior >> to yours when I tried virtx7-44-testing. >> After looking around a bit I tried "virtx7-44-candidate", in a sibling >> directory to

When installing xen-utils-V in a driver domain domU, it drags in xen-utils-common, which also contains the init script for xenstored and xenconsoled. Installing the package will fail right away, because it exits non-zero after checking whether it's running in a xen dom0 or not: systemd[1]: Starting LSB: Xen daemons... xen[7215]: Starting Xen daemons: (warning). systemd[1]: xen.service:

Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential