similar to: Bug#695041: "service xendomains stop" sleeps XENDOMAINS_STOP_MAXWAIT seconds for every domain

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

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

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!

Processing commands for control at bugs.debian.org: > close 726827 4.4.0-1 Bug #726827 [xen-utils-4.1] xen-utils-4.1: Xen doesn't start on a laptop with Nvidia Optimus graphics There is no source info for the package 'xen-utils-4.1' at version '4.4.0-1' with architecture '' Unable to make a source version for version '4.4.0-1' Marked as fixed in versions

I second the feeling that hiding xen utilities in /usr/lib/xen-default/bin/ is not very good. I ran into it with pygrub, which is another program widely documented to be in /usr/bin. Seems like slave symlinks with update-alternatives could let these programs be available in the path and still be at versions in sync with the right version of xen. -- see shy jo -------------- next part

Hi all! I have found a bug in xen-utils-common 4.3.0-3... --- xendomains.orig 2012-09-18 00:00:00.000000000 +0200 +++ xendomains 2014-06-03 16:10:12.079731629 +0200 @@ -42,7 +42,7 @@ check_config_name() { - xen create --quiet --dryrun --defconfig "$1" | sed -n 's/^.*(name \(.*\))$/\1/p' + xen create --quiet --dryrun --defconfig "$1" | sed -n

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, On system shutdown the 'xendomains' script appears to detect wrong guests: | Stopping libvirt management daemon: libvirtd. | Clearing ebtables rulesets: filter nat broute done. | Shutting down Xen domains: bev-d6x02(save).Error: Domain '1024' does not exist. | !(shut).Error: Domain '1024' does not exist. |

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

Hi, While booting I am getting Failed to start Xendomains - start and stop guests on boot and shutdown. See ''systemctl status xendomains.service'' for details. When tried to start manually, its also fails service xendomains restart Redirecting to /bin/systemctl restart xendomains.service Job failed. See system journal and ''systemctl status'' for

Hi, I have cloned the official repository and made a branch to try to sort out the issues I have with stock xendomains. When I try to stage my changes, I get this error:- [me@xen3 init.d]# git add xendomains The following paths are ignored by one of your .gitignore files: tools/hotplug/Linux/init.d Use -f if you really want to add them. fatal: no files added I can''t find the rule

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This tripped me up recently too, but i found i needed a different patch: 0 aesop:~# diff -u /etc/init.d/xendomains{.orig,} - --- /etc/init.d/xendomains.orig 2007-04-18 12:04:04.000000000 -0400 +++ /etc/init.d/xendomains 2007-04-18 13:00:28.000000000 -0400 @@ -128,9 +128,9 @@ parseln() { - - name=`echo "$1" | cut -c0-17` +

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal xendomains saves the active domains when shutting down. it get the list of active domains from the following command[1]: xm list | grep -v '^Name' the output of "xm list" is like: lichen:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0

Hi everyone! I''m using Xen 3.1.2 and Heartbeat on a two-node CentOS 5.2 cluster, and I''m having a little problem with the xendomains script.. I applied the patch at http://xenbits.xensource.com/xen-unstable.hg?rev/01c8ccb551b0 but it throws a syntax error when XENDOMAINS_AUTO points to an empty directory.. I think the patch should check if $NAMES (line 333) is empty before using

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important patch I ran into this problem when using xen on Debian/Etch. I have several virtual xen instanses, and I name them using their fully qualified DNS domain name. These machines have failed to start automatically when I booted the host machine, and I just recently found out why. During shutdown, I was messages like this: Error:

Processing commands for control at bugs.debian.org: > reassign 298783 xen-utils-common Bug#298783: xend is stopped before xendomains in debs Bug reassigned from package `sysv-rc' to `xen-utils-common'. > tags 298783 - wontfix Bug#298783: xend is stopped before xendomains in debs Tags were: wontfix Tags removed: wontfix > thanks Stopping processing here. Please contact me if

xendomains init and default are fixed in debian/ and not updated for a long time. This is a commit based on new git when I did fast update and test: https://github.com/Fantu/pkg-xen/commit/4e975f306b8186bdcc02e0165516167d6fe8930b Thanks for any reply and sorry for my bad english. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type:

Source: xen Version: 4.4.0-4 Severity: normal Xendomains init and default files are taken from debian folder instead source and are not updated for some years. Please update them from upstream source. I did a fast update and test of them available here: https://github.com/Fantu/pkg-xen/commit/4d1914776256d209665d490182cf662f70cda619 -- System Information: Debian Release: jessie/sid APT prefers

There is some ugliness in the current version (4.4.1-2) although it doesn't seem to actually break anything in my case. From /var/log/boot: /etc/init.d/xendomains: line 128: domains: bad array subscript Starting Xen domain (from /etc/xen/auto/dnsmaster.cfg).../etc/init.d/xendomains: line 135: domains: bad array subscript