Hi,
There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service.
If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start.
Deleting the symlink from the autostart folder, then starting the libvirtd service works.
Is this a know issue ?
We have found this on 4-5 servers.
Regards,
Pulkit Gupta
On 12/21/2015 05:57 AM, Pulkit Gupta wrote:
Hi,
There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service.
If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start.
Deleting the symlink from the autostart folder, then starting the libvirtd service works.
Is this a know issue ?
We have found this on 4-5 servers.
Are you saying that you can not set any VMs to autostart at any time (which is why an entry gets in there in the first place) .. or that this is a problem only on the first start up after an upgrade?
I do not see the issue on bugzilla.redhat.com
Hi,
It looks like its linked to this bug : https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1267256
I am not sure they will fix it upstream or not though.
Regards, Pulkit Gupta
-----Original Message----- From: centos-virt-bounces@centos.org [mailto:centos-virt-bounces@centos.org] On Behalf Of Johnny Hughes Sent: 21 December 2015 09:28 PM To: centos-virt@centos.org Subject: Re: [CentOS-virt] CentOS 7.2 libvirtd 1.2.17 bug
On 12/21/2015 05:57 AM, Pulkit Gupta wrote:
Hi,
There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service.
If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start.
Deleting the symlink from the autostart folder, then starting the libvirtd service works.
Is this a know issue ?
We have found this on 4-5 servers.
Are you saying that you can not set any VMs to autostart at any time (which is why an entry gets in there in the first place) .. or that this is a problem only on the first start up after an upgrade?
I do not see the issue on bugzilla.redhat.com
-
Johnny Hughes -
Pulkit Gupta