Hello,
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?
--
Craig Thompson, President
Caldwell Global Communications, Inc.
Try, "virsh autostart VMNAME" pjwelsh
On Mon, Aug 15, 2016 at 2:54 PM, Craig Thompson < president@caldwellglobal.com> wrote:
Hello,
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?
--
Craig Thompson, President
Caldwell Global Communications, Inc.
CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
On Mon, Aug 15, 2016 at 8:54 PM, Craig Thompson president@caldwellglobal.com wrote:
Hello,
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?
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.
-George
Craig,
Try this:
mkdir -p /etc/libvirt/libxl/autostart cd /etc/libvirt/libxl/autostart ln -s /etc/libvirt/libxl/[name-of-vm].xml
I just verified that worked for me... Here is my setup:
[root@host-1 ~]# ls -latr /etc/libvirt/libxl total 24 drwx------. 6 root root 4096 Jun 26 15:31 .. -rw------- 1 root root 1279 Jul 19 12:36 pulp.xml -rw------- 1 root root 1279 Aug 1 12:38 solr.xml -rw------- 1 root root 1300 Aug 4 13:01 workstation.xml -rw------- 1 root root 1306 Aug 8 12:48 atomic-master.xml -rw------- 1 root root 1271 Aug 8 12:48 db.xml drwxr-xr-x 3 root root 111 Aug 16 12:12 . drwxr-xr-x 2 root root 28 Aug 16 12:12 autostart [root@host-1 ~]# [root@host-1 ~]# ls -latr /etc/libvirt/libxl/autostart/ total 0 drwxr-xr-x 3 root root 111 Aug 16 12:12 .. lrwxrwxrwx 1 root root 34 Aug 16 12:12 workstation.xml -> /etc/libvirt/libxl/workstation.xml drwxr-xr-x 2 root root 28 Aug 16 12:12 .
Hope that helps!
Flossy
PS I am running 4.6.1...
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?
--
Craig Thompson, President
Caldwell Global Communications, Inc.
Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare
-
Craig Thompson -
George Dunlap -
PJ Welsh -
Scot P. Floess