similar to: Xen4CentOS 6 64bit - domUs don't shutdown on dom0 after "yum upgrade" to 4.6.1

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

On Tue, May 24, 2016 at 3:23 PM, George Dunlap <dunlapg at umich.edu> wrote: > > The patches have been backported and are available in 4.6.1-9 from > virt-xen-testing. Please test it and report any problems here. > Thanks for the notice. It doesn't look like the fix went in. See below: # yum repolist | grep xen centos-virt-xen-testing CentOS-6 - xen - testing

George, Thanks a lot for your investigation and feedback. I confirm it works as expected after the change you proposed. Cheers, -- exvito

On Tue, May 24, 2016 at 10:20 PM, exvito here <ex.vitorino at gmail.com> wrote: > On Tue, May 24, 2016 at 3:23 PM, George Dunlap <dunlapg at umich.edu> wrote: >> >> The patches have been backported and are available in 4.6.1-9 from >> virt-xen-testing. Please test it and report any problems here. >> > > Thanks for the notice. It doesn't look like

Currently we hardcode various paths such as $libexec/xen/{bin,boot}, however some downstreams (notably Debian) would like instead to install things into $libexec/xen-X.Y/{bin,boot} as part of allowing multiple versions of the tools packages to be installed. Since this currently involves patching configure its a bit fiddly, provide a configure option for the leaf dir instead, name it

On Mon, Apr 11, 2016 at 6:06 PM, exvito here <ex.vitorino at gmail.com> wrote: > George, > > Thanks a lot for your investigation and feedback. > I confirm it works as expected after the change you proposed. The patches have been backported and are available in 4.6.1-9 from virt-xen-testing. Please test it and report any problems here. -George

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!

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)

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

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:

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.

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

Author: ultrotter Date: 2006-03-21 16:54:07 +0000 (Tue, 21 Mar 2006) New Revision: 127 Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm Log: Stop xend & xendomains on remove, and call update-rc.d on purge... Modified: trunk/xen-3.0/debian/xen-utils-3.0.postrm =================================================================== --- trunk/xen-3.0/debian/xen-utils-3.0.postrm 2006-03-21

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

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)............

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

# 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

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

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