> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/troubleshooting/linux-kvm/troubleshooting-issues-image-access.md).

# Problems Accessing Images in Catalog

If you have uploaded your virtual machine images to the designated image catalog folder on your host that's been assigned the image catalog role, and you still don't see those images in your images section of Platform9 UI, here are some common reasons why.

### Permissions Not Set Correctly on your Image File

We require that the image file located in the image catalog folder is readable by the 'pf9' user and 'pf9group' group on your host that's been assigned the image catalog role. Making the image world readable will work as well. Please fix the permissions for your image file, and refresh the Platform9 Images UI in 5 minutes to see if the Image appears.

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

```bash
# Make Image file world-readable
chmod o+r <image-file-path>
```

{% endtab %}
{% endtabs %}

### Image Files Missing Right Metadata or Not Recognizable

Platform9 internally runs [qemu-img (QEMU disk image utility)](http://linux.die.net/man/1/qemu-img) on the image file to discover its type and metadata about it. If the file is not recognized by qemu-img, we try to process it as a raw image file (extension .raw, .img, .dat, .bin), and if that fails, then we report failure to recognize the file (and the file won't be reported in your image catalog).

Try running qemu-img on the image file and see what results you get.

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

```bash
sudo qemu-img info <image-file-path>
```

{% endtab %}
{% endtabs %}

Please read this article for more information on [Supported Image Types and File Formats](/managed-openstack/images/images-supported-types-formats.md)


---

# 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://docs.platform9.com/managed-openstack/troubleshooting/linux-kvm/troubleshooting-issues-image-access.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.