Displaying 20 results from an estimated 20000 matches similar to: "Bug#760270: xen: Update xendomains init and default files to rispective upstream version"
2014 Sep 02
1
Bug#760270: xen: Update xendomains init and default files to rispective upstream version
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
2014 Dec 11
2
Bug#772809: Update debian xendomains init and default to latest xen upstream
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).
2014 Nov 14
1
Bug#769543: xen-utils-common: missing xen-init-name
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:
2014 Aug 22
0
Update xendomains init and default of xen 4.4 packages
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:
2014 Sep 27
5
Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service 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
2007 Apr 18
0
Bug#395305: /etc/init.d/xendomains parseln() and long domU 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`
+
2007 Mar 10
0
Bug#414294: xen-utils-common: /etc/init.d/xendomains fail to save domains with "long" 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:
2012 May 04
1
[PATCH] tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains
# 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
2014 Dec 10
0
Processed: closing 760270
Processing commands for control at bugs.debian.org:
> close 760270
Bug #760270 [src:xen] xen: Update xendomains init and default files to rispective upstream version
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
760270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760270
Debian Bug Tracking System
Contact owner at bugs.debian.org
2008 Sep 11
1
Error in /etc/init.d/xendomains if using option XEN_DOMAINS_AUTO_ONLY=true - saving of the domains always fails / shutdown is called
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
2008 Sep 11
1
Error in /etc/init.d/xendomains if using option XEN_DOMAINS_AUTO_ONLY=true - saving of the domains always fails / shutdown is called
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
2012 Jul 06
4
Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot
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
2010 Sep 08
1
Bug#596048: xen-utils-common: /etc/init.d/xendomains stop saves images world readable
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:
2016 Apr 17
5
Bug#821254: systemd[1]: xendomains.service start operation timed out.
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
2015 Sep 10
4
Bug#798510: xen-utils-common: xendomains domU auto-starting fails after upgrade to Debian 8
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:
2014 Dec 06
1
Bug#772274: xen-utils-common: when upgrading package: insserv: Service xenstored has to be enabled to start service xendomains
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!
2012 Jun 25
0
Failed to start Xendomains
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
2015 Nov 05
0
Bug#798510: Bug#798510: xen-utils-common: xendomains domU auto-starting fails after upgrade to Debian 8
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:
2012 Jul 19
1
Bug#680528: xen-utils-common: Please disable xendomains auto-start
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
2011 Aug 31
0
xendomains not starting at boot
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