CentOS virt - Aug 2016 - how to enable auto-start on newer versions of Xen ?

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?



Thanks.



--

Craig Thompson, President

Caldwell Global Communications, Inc.


-----Original message-----
From: PJ Welsh?<pjwelsh at gmail.com>
Sent: Monday 15th August 2016 17:05
To: Discussion about the virtualization on CentOS <centos-virt at
centos.org>
Subject: Re: [CentOS-virt] how to enable auto-start on newer versions of Xen ?

Try, "virsh autostart VMNAME"
pjwelsh

On Mon, Aug 15, 2016 at 2:54 PM, Craig Thompson <president at
caldwellglobal.com <mailto:president at 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 at centos.org <mailto:CentOS-virt at centos.org> 
 https://lists.centos.org/mailman/listinfo/centos-virt
 


_______________________________________________

CentOS-virt mailing list

CentOS-virt at centos.org

https://lists.centos.org/mailman/listinfo/centos-virt



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20160823/85e11243/attachment-0002.html>

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

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 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.
> 
Sorry, I missed the CentOS 7 bit.

Looking at https://github.com/CentOS-virt7/xen/blob/xen-46/SPECS/xen.spec#L613
it looks like xendomains is not enabled by default. It looks like that
happened in
https://github.com/CentOS-virt7/xen/commit/01a31207ef50ec8c664fa0807ac85075dca3aa53.
No clue as to why.

--Sarah