similar to: Git problems when modify xendomains

Hi, Ever since xl become the preferred toolstack, I have had problems using the xendomains startup/shutdown script. Having retested today, it seems that the issues are now reduced down to xendomains being unable to restart previously saved domains. Here is a typical session using xl running Xen 4.2.2 on Ubuntu 64 12.04 bit server, using stock Dom0 kernel (3.2.0-43-generic)

Hi, so here is finally my upgrade report for my testsystem. I tried to upgrade to xen3 while xen2 (hypervisor, dom0 kernel + 1 domU) was running: 1) if xen2 (adams latest packages in this case) were installed and we would release our package as it is, we would generate the following enviorment: # apt-get upgrade -u Reading package lists... Done Building dependency tree... Done The following

Author: tha-guest Date: 2006-03-03 18:08:48 +0000 (Fri, 03 Mar 2006) New Revision: 70 Modified: trunk/xen-3.0/debian/changelog trunk/xen-3.0/debian/control trunk/xen-3.0/debian/xen-utils-3.0.postinst Log: The "Sorry for the step back, but I guess it''s more a 2 steps forwards" commit - Added the xen package again, because we believe there is a valid upgrade

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

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

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

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

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

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

Hello, I have the following error with Xen 4.2.4-33 when stopping xendomains: Shutting down Xen domains: Domain-0(skip) xen101(save).. xen101(save)............ xen102(save). An error occurred while saving domain: Error: Domain '9' does not exist. ! (shut). An error occurred while shutting down domain: Error: Domain '9' does not exist. ! xen102(save)............