> For the complete documentation index, see [llms.txt](https://netmind-power.gitbook.io/netmind-power-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://netmind-power.gitbook.io/netmind-power-documentation/rent-gpus/virtual-machine.md). # Virtual Machine ## Connect to Your Machine After you make the payment, you should now see a dashboard with your newly rented machine. If you do not see the IP Address and Port, you may need to manually refresh the browser page. You can find the instance's "Public IP" as shown below.

Then you can use command like this (assume your public ip is "32.49.34.11"): ``` chmod 600 your_ssh_private_key.pem && ssh -i your_ssh_private_key.pem ubuntu@32.49.34.11 ``` ## Expose Your Service Your service can be easily exposed through the "Public IP" shown on the page. The only thing to note is that you need to ensure that the port your application listens to appears in the "inound rules" of the firewall configuration. You can find the firewall configuration in the virtual machine instance details ## Key Paris To ensure the security of your connection, we require you to create and use a "Key Pairs" to do the SSH login for a virtual machine instance. You can create and manage your "key paris" under "GPU Clusters" - "Key Pairs", or create new "Key Pairs" while creating virtual machine instances. ## Volumes When you find that the disk space of your rented virtual machine instance is insufficient, you can create a volume and then mount this volume to the virtual machine instance. It's important to note that volumes are billed separately and charges begin immediately upon creation (even if the volume has not yet been mounted to the virtual machine instance).

After creating a volume, you can choose to mount it either from the volume list page or from the virtual machine details page *** ## Machine status

Status	Explation	Billing
ACTIVE	The VM is running, and all resources are allocated. This is the standard working state.	Billed
SHUTOFF	When a VM is stopped, it transitions to a SHUTOFF state, where billing continues for all resources, as they remain reserved exclusively for that VM. To prevent ongoing billing costs, ensure the virtual machine is either HIBERNATED or DELETED.	Billed
HIBERNATED	When a VM is HIBERNATED, its configuration and root disk data are saved, and all hardware resources from the VMs flavor are de-allocated. Billing continues only for attached resources and the data from the root disk saved to persistent storage.	Partially Billed
DELETED	The VM is permanently removed, and all resources are de-allocated.	Not Billed

Transitional status:

Status	Explation	Billing
HIBERNATING	The VM is transitioning into a HIBERNATED state.	Not Billed
RESTORING	The VM operating system and software are restarting from HIBERNATION and returning to an ACTIVE state.	Not Billed
STARTING	The request to start the VM has been accepted.	Not Billed
STOPPING	The VM is being stopped. This is the transition state between ACTIVE and SHUTOFF.	Not Billed
REBOOTING	The VM is being restarted, simulating the process of unplugging and rebooting a physical machine.	Not Billed
CREATING	The request to create the VM has been accepted.	Not Billed
BUILD	The VM is being built with the specified configuration.	Not Billed
DELETING	The VM is being deleted.	Not Billed
ERROR	The VM is stuck in an error state. The last operation on the virtual machine was unsuccessful.	Not Billed

--- # 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://netmind-power.gitbook.io/netmind-power-documentation/rent-gpus/virtual-machine.md?ask=&goal= ``` `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.