Hi Jevgeni,
After upgrading to 4.11.1.0, by default we require that hosts are secured using
a new CA framework. To do that you can run provisionCertificate API against all
your KVM hosts and CPVM/SSVM hosts which will secure and onboard them to use
CloudStack issued x509 certificates.
By def
Resolved the problem by following changes in /etc/libvirt/libvirtd.conf
listen_tls=0
listen_tcp=1
Now I can move running instances between hosts!
BUT - new problem
The instances, running on freshly added host are not accessible over TCP
from LAN. When I open console for these instances, then the
My host is running on Centos7.
tried to set "LIBVIRTD_ARGS=-l" in
/etc/sysconfig/libvirtd
But nothing changed
On Tue, Sep 18, 2018 at 8:42 PM Nicolas Bouige wrote:
> Hello Jevgeni,
>
> Whats is your linux distribution ?
> On ubuntu 16.04, We ran into the same problem few month ago and we had
Hello Jevgeni,
Whats is your linux distribution ?
On ubuntu 16.04, We ran into the same problem few month ago and we had to
modify the libvirt-bin.service as well.
'ExecStart=/usr/sbin/libvirtd $libvirtd_opts' >> 'ExecStart=/usr/sbin/libvirtd
-l $libvirtd_opts'
Add the "-l" before $libvirtd_o