similar to: Enabling auto domU start causing system reboot

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:

List, here''s how I got 4.1 up on suse 11.4 There is a small bug with the xencommons init script preventing xenstored from starting. Add this repo for 4.1 RPM''s ------------- zypper ar http://download.opensuse.org/repositories/Virtualization/openSUSE_11.4 Virt zypper ref zypper in xen-4.1.0_01-106.1 Fix the xen inits  (observe the order here) ------------ chkconfig -s

Hello all, I'm addressing the mailing list following the suggestion of gwd on #centos-virt @freenode IRC. The subject says most of it. Here are the details : - Was running 4.4.x and configured such that /etc/xen/auto domUs would be saved/restored on dom0 shutdown/bootup. - Installation was based on "centos-release-xen" such that "yum upgrade" brough Xen to 4.6.1. After

On Thu, Apr 7, 2016 at 5:46 PM, exvito here <ex.vitorino at gmail.com> wrote: > Hello all, > > I'm addressing the mailing list following the suggestion of gwd on > #centos-virt @freenode IRC. > > The subject says most of it. Here are the details : > > - Was running 4.4.x and configured such that /etc/xen/auto domUs would be > saved/restored on dom0

Hi, Im just setting up a new server which I have nearly complete. I have the DomUs automatically starting by placing the sym links in /etc/xen/auto and by executing /etc/init.d/xendomains on startup however I cannot get them to shutdown gracefully. I have set in /etc/default/xendomains to shutdown and not save but it seems this setting is ignored and the DomUs just get killed. Is

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:

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

On 08/23/2016 01:10 PM, Sarah Newman wrote: > On 08/23/2016 12:59 PM, Craig Thompson wrote: > >> I was thinking that in iterations past, it was possible just to run the hypervisor, put a symlink in /etc/xen/auto, and VMs would be auto-started upon reboot. Maybe I'm wrong, and maybe those older boxes had libvirt installed on them, too. >> > > We haven't had issues

On 08/23/2016 12:59 PM, Craig Thompson wrote: > I was thinking that in iterations past, it was possible just to run the hypervisor, put a symlink in /etc/xen/auto, and VMs would be auto-started upon reboot. Maybe I'm wrong, and maybe those older boxes had libvirt installed on them, too. > We haven't had issues on xen 4.6. We don't use libvirt. Are you sure xendomains is

Try this: systemctl start xendomains.service systemctl enable xendomains.service On 21 January 2016 at 08:48, Francis Greaves <francis at choughs.net> wrote: > I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen > 4.? on CentOS 6.5 on my previous system. I installed using yum install > centos-release-xen. > On shutting down the Hypervisor it used to

After a fresh install, I noticed that shorewall 2.4.0 wasn''t starting automatically under FC4. The startup script installs properly from the rpm: /etc/rc.d/init.d/shorewall ... but the post install "/sbin/chkconfig --add shorewall" produces this in the runlevel symlink directories: /etc/rc.d/rc5.d/S-1shorewall /etc/rc.d/rc0.d/K-1shorewall /etc/rc.d/rc6.d/K-1shorewall

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

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: 4.0.0-1 Severity: normal Tags: squeeze The host runs (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and the message "rebooting now" appears, but nothing happens until "INFO: task xenwatch is

I am trying to a install Centos 5.1 32-bit Xen HVM DomU onto a Centos 5.1 64bit DomU with the default xen installed and the kickstart hangs at random points during the install process. Sometimes retrieving the image, sometimes formatting the filesystem, sometimes installing the packages,etc. I tried upgrading to xen 3.2 and encounter the same problem before rebuilding back to stock Centos 5.1

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

Hi, I''m having some issues with having my domUs shutdown gracefully when my dom0 reboots. Heres my config.sxp. --- snippet --- (actions_after_crash restart) (actions_after_shutdown preserve) (auto_power_on False) (actions_after_reboot restart) (on_crash restart) (on_poweroff destroy) (on_reboot restart) (on_xend_start start) (on_xend_stop shutdown) ___________ When I reboot my

Package: xen-utils-common Version: 4.0.0-1 Severity: important The script /etc/xen/scripts/block contains an error in the part which is checking the sharing of the already created loop devices. This error leads in the case of somespecific file inode values to the wrong report of the loop device as being already used and causes then the domain could not be started with such device at all, there

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