On Tue, Apr 13, 2021 at 15:56:57 +0530, shafnamol N wrote: >> Hi, >> >> I am using *CentOS 8*. I have built *libvirt* with the following method: >> >> $ meson build -Dsystem=true > >$ ninja -C build > >$ ninja -C build install >> > >But the problem is when i started it > > >> # systemctl start libvirtd > .Job for libvirtd.service failed because the control process exited > .with error code. > >See "systemctl status libvirtd.service" and "journalctl -xe" for details. > .> >>i tried to get the status of libvirt > > > ># systemctl status libvirtd > > > >libvirtd.service - Virtualization daemon > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; > >vendor preset: enabled) > > Active: failed (Result: exit-code) > > >> What will be the problem?
>Well, what does the log say? >https://www.libvirt.org/kbase/debuglogs.html <https://www.libvirt.org/kbase/debuglogs.html> I have edited /etc/libvirt/libvirtd.conf file based on https://www.libvirt.org/kbase/debuglogs.html Then restarted libvirt # systemctl restart libvirtd.service Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details. >There is not enough info to figure out what the problem is. Including >the output of 'journalctl -xe' as suggested would be useful. # journalctl -xe -- Unit libvirtd.service has failed. -- -- The result is failed. Apr 15 09:12:33 csg-dellemcsvr0 systemd[1]: libvirtd-ro.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libvirtd-ro.socket has entered the 'failed' state with result 'service-start-limit-hit'. Apr 15 09:12:33 csg-dellemcsvr0 systemd[1]: libvirtd-admin.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libvirtd-admin.socket has entered the 'failed' state with result 'service-start-limit-hit'. Apr 15 09:12:33 csg-dellemcsvr0 systemd[1]: libvirtd.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit libvirtd.socket has entered the 'failed' state with result 'service-start-limit-hit'. On Tue, Apr 13, 2021 at 4:29 PM Pavel Hrdina <phrd...@redhat.com> wrote: > On Tue, Apr 13, 2021 at 03:56:57PM +0530, shafnamol N wrote: > > Hi, > > > > I am using *CentOS 8*. I have built *libvirt* with the following method: > > > > $ meson build -Dsystem=true > > $ ninja -C build > > $ ninja -C build install > > I would recommend to never to this again. In general installing upstream > projects into any distribution like this is asking for a lot of trouble. > The upstream project can change files owned by other packages and break > them and running yum update can override anything the upstream project > installed. > > Ideally you want to create in case of CentOS RPM package and install > that instead. If that's not possible you should install upstream project > into /usr/local/ directory which distribution packages usually don't > touch at all. > > In case of libvirt you can do the following steps: > > meson build > ninja -C build dist > rpmbuild -tb build/meson-dist/libvirt-{version}.tar.xz > > The resulting RPMs will be in ~/rpmbuild/RPMS/{arch}/ > > you can install all of them but you can also install only what you are > interested in. > > > But the problem is when i started it > > > > # systemctl start libvirtd > > Job for libvirtd.service failed because the control process exited > > with error code. > > See "systemctl status libvirtd.service" and "journalctl -xe" for details. > > > > i tried to get the status of libvirt > > > > # systemctl status libvirtd > > > > libvirtd.service - Virtualization daemon > > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; > > vendor preset: enabled) > > Active: failed (Result: exit-code) > > > > What will be the problem? > > > > Thanks for the help in advanc.... > > There is not enough info to figure out what the problem is. Including > the output of 'journalctl -xe' as suggested would be useful. > > Pavel >
