similar to: Xen 4.1 auto shutting down of DomUs at reboot

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

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

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

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 wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. For some reason the DomUs (CentOS

I would like to have xen auto start the domUs when the dom0 is rebooted. System is FC4 for both dom0 and domU. 1GB ram, etc. I''ve enabled xend as chkconfig --add xend and it works fine. I''ve enabled xendomains as chkconfig --add xendomains and it works fine as long as I don''t have any domain config file in /etc/xen/auto. If I add a file and reboot dom0, the host

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

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:

Hi, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

Hi Francis. Personally I would gracefully shutdown all the VM?s first, before attempting to shutdown the xen hypervisor. Are you getting any fsck errors when restarting those VM?s? Kind Regards, Keith On 21 Jan 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

Hey all, I have moved 10_Linux to 50_Linux and ran update-grub which is fine. The problem I have is that there is xen-syms in /boot And that is being put first in the boot list which is incorrect. How do you make /xen.gz at the top so it is booted first? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi guys, Having a weird issue with a Dom0. When we were running 2.6.18.8 kernel the server would lock up every 2 weeks for no reason. Its been a difficult one to resolve as there are no errors. We have now upgraded to 2.6.32.13 and the lock ups are more often. For example today it crashed in the morning, then it was rebooted and it crashed again about 5 hours later, no logs. The

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:

Hi, Ive built a new server using xen debian lenny packages. Im trying to firewall dom 0 which i can do ok but it then blocks access to the dom Us. Has anyone managed to do this successfully? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, Having a problem getting a domu to boot correctly. When I enter xl create guest it boots straight into grubdom. If I enter the config location in grubdom t boots as expected. The location of the grub.cfg is the same in my domu config as what in entering but just will not work. Any ideas? Ian .

What is the best kernel to run? is it better to run 3.4.4 or one from xen git? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello, I''m using my dom0 on a RHLE 4.4 with xen 3.0.4-1. My domUs work on the same O/S, and any virtual disk is composed by 5 files : disk = [

Hi, Im trying to compile kernel 3.0.4 inside Centos 5 DomU The steps I do are Make bzImage Make modules Make modules_install Depmod -a mkinitrd /boot/initrd.img-3.0.4 3.0.4 but them im getting this -bash-3.2# mkinitrd /boot/initrd.img-3.0.4 3.0.4 ls: /etc/modprobe.d/*.conf: No such file or directory No module ehci-hcd found for kernel 3.0.4, aborting. If I exclude the

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

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Hi, from my testing xm reboot and xm shutdown does not work for Solaris DomUs yet, is this correct? regards Bernd This message posted from opensolaris.org