similar to: Bug#395305: /etc/init.d/xendomains parseln() and long domU names

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:

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

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

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

Package: xen-utils-common Version: 3.0+hg11624-2 Severity: normal Hi, Problem shutting down Xen when DomU name contains more than 17 characters. I use fully qualified domain names in DomU names (example: long-domu-name.domain.com) Here's results when i attempt to run the following command: /etc/init.d/xendomains stop long-domname.doma(save)...Error: the domain 'in.com' does

Hello, in the last days I switched from Xen 4.2.1 to Xen 4.2.2 (source from git repository tag 4.2.2) commit a125ec6a4a2f028f97f0bdd8946d347a36dbe76b Author: Jan Beulich <jbeulich@suse.com> Date: Tue Apr 23 18:42:55 2013 +0200 update Xen version to 4.2.2 My "base system" is a debian squeeze. For Xen I use the xl toolstack. Since updating to 4.2.2 the autosave and

Hi Rahul, Thanks for your interest! Our work does not attempt to make any significant contributions to alias analysis, and acts as a client to existing LLVM AA. Furthermore, the options passed to the AESOP frontend scripts are obeyed at compile time, but at link time certain transformations occur unconditionally. Here, AESOP has actually thwarted your experiment by performing inlining just

Hi Timothy, > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further information is available at > > http://aesop.ece.umd.edu > > The main components of the released

On 03/03/2013 02:09 PM, Timothy Mattausch Creech wrote: > Hi, > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further information is available at > >

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

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

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

Package: xen-utils-common Version: 4.1.3-4 Function check_running in /etc/init.d/xendomains incorrectly detects a not running domain as running. As a consequence thereof "/etc/init.d/xendomains stop" needs more than XENDOMAINS_STOP_MAXWAIT * "number of xen domains known to xend" seconds to run. Here is a pseudo call trace: do_stop_shutdown() { ... while read id name

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