> 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/5.4/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/5.4/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.platform9.com/managed-openstack/5.4/troubleshooting/linux-kvm/troubleshooting-issues-image-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.