How To Enable Auto-start On Newer Versions Of Xen ?

Home » General » How To Enable Auto-start On Newer Versions Of Xen ?
General 6 Comments


In days past, all I had to do was create /etc/xen/auto and put a symlink in there to the config file for each VM I wanted to have started automatically.

Since updating to 4.6, this doesn’t work.  Period.

I’m having a hard time finding what needs to change in order to get VMs to auto start on reboot of a server.  Can someone please point me to documentation that I have missed or share the gold nugget?

6 thoughts on - How To Enable Auto-start On Newer Versions Of Xen ?

  • Since you’re speaking of upgrading, I assume you’re using CentOS 6?
    What version of the xen packages are you using?

    There’s a bug in the upstream 4.6 xendomains scripts (which start things from /etc/xen/auto) when they run on RHEL-based systems. That should have been fixed in the xen-4.6.1-9 Virt SIG package.


  • PJ,

    I didn’t have virsh installed (libvirt-client).  After having installed it, it still didn’t see the process:

    virsh autostart testvm error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to ‘/var/run/libvirt/libvirt-sock’: No such file or directory

    Then, after having installed libvirt, it gives essentially the same error.

    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.

    If I need to install libvirt, what does this mean overall?  What am I changing?  What other process needs to run or be started upon boot on a  CentOS 7.x box?


  • We haven’t had issues on xen 4.6. We don’t use libvirt.

    Are you sure xendomains is enabled? Maybe in the past it was enabled by default but isn’t now.

    If it is enabled, have you tried running the xendomains init script manually with bash -x to see where it’s going wrong? You need to add ‘set -x’ to
    /usr/lib64/xen/bin/xendomains as well for full output.