Thank you, Sarah. That was the missing piece.
--
Craig Thompson, President
Caldwell Global Communications, Inc.
-Original message-
From: Sarah Newman
Sent: Tuesday 23rd August 2016 17:14
To: Discussion about the virtualization on CentOS
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
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.
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
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 ..
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