> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/unable-to-start-libvirtd-service.md).

# Unable to Start Libvirtd Service

## Problem

* Unable to start ***libvirtd*** service on the KVM host.
* We see "'/etc/pf9/certs/libvirt/cacert.pem': No such file or directory" in */var/log/messages* on the KVM host.
* The complete snippet in */var/log/messages* on the KVM host while starting Libvirt daemon.

{% tabs %}
{% tab title="None" %}

```none
systemd: Starting Virtualization daemon...libvirtd: 756+0000: 15182: info : libvirt version: 4.5.0, package: 10.el7_6.4 (CentOS BuildSystem [http://bugs.centos.org], XXXX-XX-XX-YY:YY:YY, x86-01.bsys.centos.org)libvirtd: 756+0000: 15182: info : hostname: smc02e2b01libvirtd: 756+0000: 15182: error : virNetTLSContextCheckCertFile:112 : Cannot read CA certificate '/etc/pf9/certs/libvirt/cacert.pem': No such file or directorysystemd: libvirtd.service: main process exited, code=exited, status=6/NOTCONFIGUREDsystemd: Failed to start Virtualization daemon.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.8.0 and Higher

## Cause

Not able to start the ***libvirtd*** daemon as the soft links are missing from */etc/pf9/certs/libvirt* directory.

## Resolution

1\. Create a directory in */etc/pf9/certs/libvirt*.

{% tabs %}
{% tab title="None" %}

```none
$ mkdir libvirt
```

{% endtab %}
{% endtabs %}

2\. Recreate the missing soft link in the */etc/pf9/certs/libvirt* directory.

{% tabs %}
{% tab title="None" %}

```none
$ ln -s /etc/pf9/certs/ca/cert.pem cacert.pem$ ln -s /etc/pf9/certs/hostagent/cert.pem clientcert.pem$ ln -s /etc/pf9/certs/hostagent/key.pem clientkey.pem
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/unable-to-start-libvirtd-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.