> For the complete documentation index, see [llms.txt](https://docs.denvrdata.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.denvrdata.com/docs/overview/getting-started/launch-a-virtual-machine.md).

# Launch a virtual machine

## Overview

Navigate to the Virtual Machines overview screen by selecting the 'Virtual Machines' item directly from the left navigation menu.  This view will display running and stopped instances.

<figure><img src="/files/nmOUfpDhlK0zwbf3XTqr" alt=""><figcaption></figcaption></figure>

## **Creating a new VM**

To launch a new Virtual Machine instance, click the 'Create Virtual Machine' button:

<div align="left"><figure><img src="/files/VLfK9QIIskmT9bbIbeQH" alt="" width="375"><figcaption></figcaption></figure></div>

Begin by entering a unique name for the instance and highlight the `on-demand` or `reserved` resource pool to use (if your tenant has reservations).

<figure><img src="/files/RBfheeZZrBJu1gTb6FJg" alt=""><figcaption></figcaption></figure>

Select the operating system type and release version.  Denvr Cloud can optionally install current stable releases of GPU drivers and required toolkits. &#x20;

<figure><img src="/files/O6a409gAT5GCnYpXTvXs" alt=""><figcaption></figcaption></figure>

Finally, choose what types of network attached storage to use with your instance, and paste your SSH public key in the 'SSH Keys' box.  Click 'Launch Instance' to begin provisioning.

<figure><img src="/files/AOzvrzd6a54zvoyI2kZ7" alt=""><figcaption></figcaption></figure>

You will be redirected back to the overview screen where the new VM appears. You will notice the VM status changing as it progresses from PENDING to ONLINE.

<figure><img src="/files/H1C4gMZ4eKh9Ay8fbS0g" alt=""><figcaption></figcaption></figure>

Once the Virtual Machine you created reaches ONLINE status, it is ready for use, and you can try pinging it throught the Public IP.

```
% ping 130.250.171.45
PING 130.250.171.45 (130.250.171.45): 56 data bytes
64 bytes from 130.250.171.45: icmp_seq=0 ttl=51 time=46.607 ms
64 bytes from 130.250.171.45: icmp_seq=1 ttl=51 time=43.375 ms
64 bytes from 130.250.171.45: icmp_seq=2 ttl=51 time=43.511 ms
64 bytes from 130.250.171.45: icmp_seq=3 ttl=51 time=44.528 ms
64 bytes from 130.250.171.45: icmp_seq=4 ttl=51 time=43.767 ms
64 bytes from 130.250.171.45: icmp_seq=5 ttl=51 time=44.102 ms
64 bytes from 130.250.171.45: icmp_seq=6 ttl=51 time=43.524 ms
^C
--- 130.250.171.45 ping statistics ---
8 packets transmitted, 7 packets received, 12.5% packet loss
round-trip min/avg/max/stddev = 43.375/44.202/46.607/1.050 ms

```

Connect to the instance using your SSH:

```
$ ssh -i ~/.ssh/id_rsa ubuntu@130.250.171.45
```

{% hint style="info" %}
You don't need to provide the -i parameter to SSH if your private key is the default key (id\_rsa) or your key is setup in `$HOME/.ssh/config` file.
{% endhint %}

You should see output similar to this:

```
kyle@kyles-macbook-pro ~ % ssh ubuntu@130.250.171.45
The authenticity of host '130.250.171.45 (130.250.171.45)' can't be established.
ED25519 key fingerprint is SHA256:zDgLTz7gwIGPBf2uXg0YgVdLkEySO2g+fwLgS99nmdM.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '130.250.171.45' (ED25519) to the list of known hosts.
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

  System information as of Wed Jul  3 14:39:36 UTC 2024

  System load:  0.30029296875      Processes:               239
  Usage of /:   0.3% of 457.75GB   Users logged in:         0
  Memory usage: 0%                 IPv4 address for enp2s0: 172.16.0.143
  Swap usage:   0%

Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status


The list of available updates is more than a week old.
To check for new updates run: sudo apt update


The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@vm-2024070310348308:~$  

```

## **Managing VMs**

The main screen for Virtual Machines serves as a control hub, allowing you to start, stop, delete, and view detailed information about each instance.

Use the 3 vertical dots icon next to each VM for lifecycle actions:

* Start - resume a stopped VM
* Stop - stop a running VM.  Resources are freed, while the root disk remains persisted
* Delete - fully release a VM.  This action can't be undone and removes all instance data

<figure><img src="/files/rrMIPLdI0wOfI0xt87EW" alt=""><figcaption></figcaption></figure>

VM details are provided by selecting the instance Name:

<figure><img src="/files/mbFCSN8G2gfAcdrf4n4d" alt=""><figcaption></figcaption></figure>

## Usage metrics

To track the real-time usage of your tenants' virtual machines, explore the 'GPU Utilization' screen. It offers a graphical and tabular representation of your Virtual Machines' usage, providing daily insights and performance data analysis for up to the last two months.

Each utilization record begins at the moment a Virtual Machine is provisioned and continues until the Virtual Machine is stopped, ensuring accurate and continuous tracking of usage.

<figure><img src="/files/cnVZQ4xZi2HTlsHoIHkM" alt=""><figcaption></figcaption></figure>