Create a GPU VM
Deploy one or more GPU-enabled virtual machines (VMs) from the IBEE Solutions portal. GPU VMs include NVIDIA GPUs for AI/ML training, inference, rendering, and other GPU-accelerated workloads. The Deploy page is a single scrolling form with a running summary and the Deploy button in the bottom bar.
Before you begin
- An IBEE Solutions account with write access to the workspace.
- A verified account to unlock server deployment (Verify your identity).
- Sufficient wallet credits — the platform checks your balance before deploying (Billing and usage).
Deploy a GPU VM
2. Select a location
Under Location, select a region tab and choose a data center location within it. GPU availability varies by location.
3. Choose a GPU plan
Under Choose Plan, select a plan. Each row lists the GPU model and its Memory, plus vCPU, RAM, Disk, and the price per month and per hour. GPU VMs are billed Hourly.
4. Select the operating system
Pick a source for the boot disk under Operating System:
On Templates, pick an OS family card, then choose a version from the OS Version dropdown.
5. Add SSH keys (Linux)
For Linux images, the SSH Keys section appears (it’s hidden for Windows images). Open Select SSH Keys and pick one or more saved keys, or click Add Key to create a key pair or import a public key. A Linux VM deployed without a key uses password login, shown under Overview → Connection Details. See SSH Keys.
6. Configure the network
Under Network Configuration, choose Internet and VPC access:
- Public IP (default) — direct inbound and outbound IPv4. Optionally pick a VPC and subnet; with a VPC you can also pick a Reserved public IP (required for a private VPC).
- Private + NAT — primary interface in a NAT Gateway VPC with outbound internet only.
- Private only — primary interface in a VPC with no internet route.
Under Firewall, pick a firewall group or click Create Group. If you don’t pick one, the default firewall group is attached automatically.
See Networking for VMs for details — the options are the same as for Cloud VMs.
7. Set VM details
Under VM Details:
- Instances — deploy up to 5 VMs at once. The maximum can be lower when GPU capacity or public addresses in the location are limited, and it’s 1 when you pick a specific Reserved IP.
- Hostname — use lowercase letters, numbers, and hyphens. With more than one instance, this becomes the base hostname and each instance is prefilled as
<base>-1,<base>-2, and so on; edit them under Instance hostnames. Every hostname must be unique.
8. Deploy
Review the summary in the bottom bar, then click Deploy (or Deploy N VMs). The platform first checks your organization’s billing state and wallet balance. If the check passes, provisioning starts and you return to the GPU VMs list. If not, a Billing needs attention popup appears — click Add Credits to top up and return.
Verify
Once provisioned, your GPU VM appears in the GPU Virtual Machines list with status Running. Click it to open the detail page. Overview → Connection Details shows the SSH command (or username and password, or RDP details for Windows).
Confirm GPU access inside the VM:
If nvidia-smi isn’t found, install a compatible NVIDIA driver for your OS inside the VM.
Manage your GPU VM
From the VM detail page, use Actions to control your server:
The detail page has these tabs:
Deleting a GPU VM is permanent and cannot be undone. Back up your data and snapshots before deleting.
Troubleshooting
Deploy shows an error message The portal validates the form when you click Deploy and names the missing item — for example a plan, an OS version, a subnet, or a unique hostname for each instance.
Billing needs attention popup Your organization’s billing state or wallet balance blocks the deploy. Click Add Credits to top up, then return.
nvidia-smi not found
The NVIDIA driver isn’t installed on the selected image. Install a compatible NVIDIA driver inside the VM. The GPU Metrics tab also shows NVIDIA guest driver required until it’s installed.
Server stuck in provisioning Wait a few minutes. If the status does not update, contact IBEE support.
