similar to: Bug#591456:

Package: xen-utils-common Version: 4.0.0-1 Severity: important When Xen is configured in routed mode, restarting xend fails because the script hotplugpath.sh is missing. Please see below for more information. *** root at eliott:~# /etc/init.d/xend restart Restarting Xen daemons: xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory

Package: xen-utils-common Version: 4.4.1-5 Severity: important Dear Maintainer, I tried to upgrade xen-utils-4.4 depending on xen-utils-common. Here is aptitude answer: ... Param?trage de xen-utils-common (4.4.1-5) ... insserv: Service xenstored has to be enabled to start service xendomains insserv: Service xenconsoled has to be enabled to start service xendomains insserv: exiting now!

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

This fast-track covers the SMF-related changes for dom0. This is a final draft, so any comments by the end of the week please... Man pages are attached. thanks john SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, While updating my xen package today, I was prompted with a config file conflict. --- /etc/xen/scripts/hotplugpath.sh 2013-04-28 01:51:20.899778510 +0800 +++ /etc/xen/scripts/hotplugpath.sh.dpkg-new 2013-04-19 19:39:55.000000000 +0800 @@ -1,12 +1,10 @@ SBINDIR="/usr/sbin" BINDIR="/usr/bin"

What follows below is an outline of what we''re changing in Xen startup for Fedora 8. I know historically when getting into initscripts you tend to hit distro specific issues. So I''m posting this to see if there''s any interest from others in having these changes integrated upstream. I''d like to thing that with a few minor tweaks this is general enough to be

*After running intensively (i.e. running >10 guests and migrating them all into other machines etc.) , I wasn''t able to * *run xen tools as the following messages show. * ** ># xm list Error: (9, ''Bad file descriptor'') Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP

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

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

Package: xen-utils-common Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Severity: important Please modify the init scripts in a manner similar to the following to give the correct SE Linux labels. Failing to correctly label them may result in Xen not working correctly when SE Linux is enabled. --- /etc/init.d/xen.orig 2012-06-24 10:29:04.000000000 +1000 +++ /etc/init.d/xen 2012-06-24

Hi all, I have some serious problems making Xen run. I have spent a couple of days looking in Google and trying a lot of different things, but none of them has worked. I hope you can help me... First of all: xen was running smoothly on my machine, but suddenly (I think I haven''t changed any configuration) it doesn''t work anymore. I am using a Debian 4.0 with Xen 3. When

I am sponsoring this fasttrack for John Levon. It is set to expire on 3/14/2007. Note that this is an externally visible case. liane --- SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted under Xen virtualisation.

Processing commands for control at bugs.debian.org: > reassign 628912 xen-utils-common 4.0.1-2 Bug #628912 [xen-utils-4.0] xenconsoled and xenstored stopping unhandled by init script Bug reassigned from package 'xen-utils-4.0' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2. Ignoring request to alter fixed versions of bug #628912 to the same values

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

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

Package: xen-utils-common Version: 3.4.2-3 Severity: normal If one daemon is running but the others are not then the stop script will fail. It should use the pid file for each daemon and try to stop them independently. Note that the fact that Xen shouldn't get into this state is not relevant, daemons do periodically fail, relevant system control scripts should be able to stop them even

Hi, A few people are having problems with the new console daemon and I''ve tracked the problem down to the order in which daemons are started. Here''s what currently happens: 1) xend (the script in tools/misc) start will launch xcs and consoled 2) xend (the python server) will launch xenstored whenever it needs it This creates a bit of a chicken and the egg problem since

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, I have recompiled xen-3_3.4.3~rc3-1 in Lenny, together with the 2.6.32-10 kernel. While my dom0 boots without issue under Xen, xend refuses to start. I have cut/past my xend.log is bellow. Is there any reason why a backport of this version of Xen wouldn't work in Lenny? Should I try the already compiled SID binaries in Lenny without trying to build myself? Cheers, Thomas When I start

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