Open navigation

Creating Virtual Machines

RESVRL supports three VM creation flows so you can match the order type to the workload instead of forcing every user into the same billing model. Open Virtual Machine in the member console and click Create to switch between Custom, Plan, and Pay-as-you-go modes.

Creating Virtual Machines

RESVRL supports three VM creation flows so you can match the order type to the workload instead of forcing every user into the same billing model. Open Virtual Machine in the member console and click Create to switch between Custom, Plan, and Pay-as-you-go modes.

Creation entry

Before you submit an order

  • Check which region and host group should run the VM.
  • Decide whether the instance needs a Bridge network, a NAT network, or both.
  • Prepare an SSH public key or decide how the initial password should be managed.
  • If you select any public-facing network, prepare a security group first.

Creation modes

Custom

Custom mode lets you manually choose region, host, image, CPU, memory, storage, bandwidth, duration, networks, and login credentials. Key fields include: region/host, system image, CPU cores, memory, disk, bandwidth, networks, Bridge/NAT, credentials (SSH key or password), and whether to attach a security group. Price is calculated in real time in the order panel before submission. Validation: at least one network must be attached and if a Bridge network is included, a security group is required.

Custom mode form

Plan

Plan mode uses predefined resource bundles. After selecting a plan, the page shows the plan's CPU, memory, disk, bandwidth, and any discounts. You can still choose image, duration, networks, and credentials.

Plan mode form

Pay-as-you-go

Pay-as-you-go is suited for short-term tasks, testing, or workloads with uncertain duration. Billing is flexible and based on usage and actual resource consumption. You must choose region/host, image, networks, credentials, and basic compute configuration (CPU, memory, storage, bandwidth, etc.).

Pay-as-you-go form

Creation steps

  1. Open Virtual Machine in the member console.
  2. Click Create.
  3. Choose Custom, Plan, or Pay-as-you-go.
  4. Select region and host machine.
  5. Select an operating system image.
  6. Configure compute resources or choose a plan.
  7. Select one or more virtual networks.
  8. Select the security group used for public traffic.
  9. Configure the initial login credentials.
  10. Review the calculated price and submit the order.

After filling in the form, the price panel at the bottom shows a breakdown of the selected configuration. Confirm the details and submit the order.

Price panel

What you configure during creation

Image

Available images depend on the selected host machine. Refer to the Supported Systems guide when choosing an image for production workloads.

Compute resources and storage

  • Custom mode: manually set CPU, memory, storage, and bandwidth.
  • Plan mode: use predefined specifications.
  • Pay-as-you-go: optimize for short-term use and flexible cost control.

Networks

A VM must be attached to at least one virtual network. You can attach multiple networks during creation. If a Bridge network is included, configure a security group for public traffic.

Credentials

SSH public keys or passwords are supported. Prefer SSH keys for better security.

Duration and pricing

Price is calculated and displayed in the order panel for Custom and Plan modes. Longer durations may offer discounts, as shown in the console.

After the order is placed

The system creates an order and enters the payment/confirmation flow. After successful payment, you will be directed to the VM details page where you can view system information, image, region, and bandwidth. Actions include starting, stopping, rebooting, resetting credentials, reinstalling the operating system, renewing the service, and adding or removing network interfaces.

Quick checks (first time opening)

  • Confirm the instance has the expected public IP addresses or private IPs.
  • Verify security group rules before exposing SSH, HTTP, HTTPS, or database ports.
  • Log in and update the operating system.
  • Confirm monitoring data is reporting on the monitor page.

Common mistakes

No public access after creation

Check whether you attached only a NAT network or whether the Bridge network is missing the required security-group rules.

Unable to log in

Confirm whether the initial order used an SSH key or password, and use the credential reset action from the instance page if needed.

Wrong size selection

If the workload is not a fit for the current specification, review available upgrade options from the instance page and monitor real resource usage before changing size.