similar to: Bug#414294: xen-utils-common: /etc/init.d/xendomains fail to save domains with "long" names

-----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: 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: 3.0.3-0-2 Severity: normal Tags: patch When shutting down xen domains with '/etc/init.d/xendomains stop' most of the time not all domains are stopped when the script finishes. As it turns out the xendomains-script queries running domains by executing 'xm list', this command replies its usage info sometimes instead of giving proper output. I

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

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

Hi All, Everytime I upgrade to a new version of Xen (just did 4.2.1 this weekend) I find the xendomains script completely unusable. I use xl exclusively and the behaviour is slightly different to what the script appears to be expecting. Am I the only one that has this problem? I have an Ubuntu 12.04 based Xen server and a Scientific Linux 6.3 based server and both suffer the same problem. I am

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Content-Type: multipart/mixed; boundary="===============0382030028==" MIME-Version: 1.0 From: Albert Dengg <a_d@gmx.at> To: Debian Bug Tracking System <395305@bugs.debian.org> Subject: xen-utils-common: here is a small patch to correctly handle long domU names in parseln Message-ID: <20070317182707.16837.48971.reportbug@audhumbla.dengg.priv.at> X-Mailer: reportbug 3.31

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

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:

Control: tag -1 +patch (experimenting with http://www.donarmstrong.com/posts/control_at_submit/ ...) Hi Thomas, I think it is as simple as the following, which works for me with xl and xm. Does it work as you expect/want with xe? Ian. >From 88f10bc8dbf96dd2c32f12259249f8be70fd01a4 Mon Sep 17 00:00:00 2001 From: Ian Campbell <ijc at hellion.org.uk> Date: Thu, 19 Jul 2012 16:19:09

On one of my xen hosts a virtual machine does not start at boot. I can see that xendomains gives an error: service xendomains start Starting auto Xen domains: fszeleNo handlers could be found for logger "xend" Error: Disk isn't accessible No handlers could be found for logger "xend" Error: Disk isn't accessible An error occured while creating domain fszele: Usage: xm

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

# 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

So, let's get started! One of the first changes we might want to do is move away /etc/sysconfig/xendomains... We should put it either in /etc/default/xendomains (since it's an init script configuration) or /etc/xen/xendomains (since it's xen related)... Which one do you prefer? As for the way to do it I propose a dpatch file that changes the two files in the upstream tarball that

Hello all I''ve just installed xen 4.1.1 on my server and was tryoing to tweak xendomains script to work with new xl schema but I can´t get it to save domains. It does start them with some changes I made to it but when I issue service xendomains stop I just get [ OK ] but domains stay running. Has xendomains script been ported to work with 4.1.1 or is there another alternative to it.

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, 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:

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