similar to: Bug#422667: xen-utils-common: Init script outputs an error message while Xen is not installed any more

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:

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-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Package: xen-utils-common Version: 3.0+hg11292-2 Tags: patch User: initscripts-ng-devel at lists.alioth.debian.org Usertags: incorrect-dependency When testing dependency based boot sequencing, I discovered a bug in the init.d script for xen-utils-common. It is set to stop in the boot "runlevel" (S), but no script should stop there. Also, xend only depend on $local_fs, but

Package: xen-utils-common Version: 4.4.1-3 I use xen, and I start some domains using symlinks in /etc/xen/auto. On startup, the file /etc/init.d/xendomains is supposed to start them. It does start the domains, but it also throws out a bunch of errors: /etc/init.d/xendomains: line 135: domains: bad array subscript The culprit is this line in /etc/init.d/xendomains:

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:

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

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

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

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

On Sat, 2015-08-22 at 00:24 +0200, Volker Klasen wrote: > Hi Ian, > > you can use the patch I posted in the original report, Uh, how on earth did I miss it! > there are two > places that need to be fixed. I'm using it since November. Thanks. Since loads is a classmethod I think the right fix for that issue is to s/self/cls/ in the body rather than s/cls/self/ in the

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

Source: xen Severity: wishlist Hi, xendomains init and default files in debian folder is not updated from upstream onesfor some years. Some parameters are missed. The more useful parameters when mainly windows domUs are used is XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems to decrease the "overload" caused by windows startup (even if pv drivers are installed).

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

On Thu, 2015-09-10 at 09:06 +0200, Wolfgang Karall-Ahlborn wrote: > After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto > fails with errors like this > > Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. > Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

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: