> 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/frequently-asked-questions/ways-to-access-vm-instances.md).

# Ways to Access VM Instances

## Problem

How to access the VM Instances?

## Environment

* Platform9 Managed OpenStack - v5.4 and Higher

## Answer

There are two ways to access VM Instances.

**1. Access through Console from Clarity UI.**

Please follow the steps mentioned in the knowledge base article: <https://platform9.com/docs/openstack/virtual-machines-access-instances-via-console>

{% hint style="info" %}
**Info**

Please note that while accessing the VM from the console, it will display either a graphical user interface (GUI) or a command-line interface (CLI) based on the below configuration/s:

* Operating System.
* Runlevel/target at which the OS is operating.
  {% endhint %}

For the Virtual Machine (VM) with a graphical user interface (GUI), the console will automatically open the GUI access. However, to access the VM through the console using the command-line interface (CLI), adjust the system configuration accordingly. Specifically, configure the system to operate at *runlevel 3/multi-user.target*.

**2. Access through CLI.**

Please follow the below steps:

* SSH to the hypervisor.
* Run the below command: (This will list all running VMs on the hypervisor)

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

```bash
sudo virsh list
```

{% endtab %}
{% endtabs %}

* To access the CLI, run the below command, with correct VM ID:

```bash
sudo virsh console <VM ID>
```

{% hint style="info" %}
**Info**

Please note that the second method will allow access to all virtual machines, regardless of the operating system they are running.
{% endhint %}


---

# 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/frequently-asked-questions/ways-to-access-vm-instances.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.
