Resize a VM
Resizing moves a VM to a different plan without rebuilding it. It lets you add or remove vCPUs and memory, and make the root disk bigger. Your files, IP address, SSH keys and attached volumes stay as they are. The VM is switched off while the change is applied and switched back on automatically.
When to use a resize
How it works
- You pick a new plan. The portal runs a pre-check that says whether the change can be made in place.
- A running VM is stopped. The new vCPU and memory are applied, and the root disk is grown if the new plan’s disk is bigger.
- The VM starts again automatically. A VM that was already stopped stays stopped.
- Billing moves to the new plan’s rate from that moment. Your bill shows the old plan and the new plan as separate lines, with no overlap.
Before you begin
- Take a snapshot first. A resize restarts the VM; a snapshot lets you go back if something goes wrong.
- You need write access to the workspace. Read-only members see the current plan but not Change Plan.
- The VM must be Running or Stopped, with no other operation in progress.
- A VM on a Monthly commitment can’t be resized until the commitment ends.
- Plan for a short outage: running applications stop while the VM restarts.
Resize in the portal
Open Change Plan
On the VM’s page, open the Settings tab. Change Plan is selected. The Current Plan card shows the VM’s vCPU, RAM and disk.
Pick a plan
Open Available Upgrades and select a plan. Each entry shows its vCPU, RAM and disk. A Selected Plan summary confirms the new size, and Billing term lets you choose the term for the new plan.
Run the pre-check
Click Upgrade Plan or Downgrade Plan. The button shows Verifying… while the pre-check runs. If the change can’t be made in place, Resize not possible lists the reasons.
Confirm
The Confirm Resize dialog shows the current and target vCPU, RAM and disk, and a Downtime notice:
- Running VM: “The VM will be stopped, resized, and started automatically.”
- Stopped VM: “The VM is currently stopped. Resize will be applied without auto-start.”
Click Confirm Resize. The VM’s status shows Resizing, then Running (or Stopped).
Resize with the CLI or API
A resize moves the VM to another plan. Pick the target plan in ibee compute plans --vm-type cloud (GET /compute/plans?vm_type=cloud) and send its cpu, ram_mb and disk_gb exactly as listed, plus its billing_catalog with the billing term you want merged in, as on create. The pre-check needs only the size.
--billing-interval HOURLY (or MONTHLY) reads the --plan-id plan from GET /compute/plans and sends its billing_catalog with that billing term merged in. You can pass the whole selection yourself with --billing-catalog JSON instead. These options need CLI 0.8.0 or later; 0.7.0 and earlier can’t resize.
With the API, check first, then resize. The resize also needs an X-Idempotency-Key. Build billing_catalog from the target plan in GET /compute/plans: copy the plan’s billing_catalog and merge in the whole billing_options entry for the term you want (billing_interval, committed, commitment_period, unit_price_minor and the rest), keeping price_currency:
where resize.json is the target plan’s size and billing selection:
Copy every value from the plan rather than typing it: the server checks the selection against its catalog. The example’s unit_price_minor is a placeholder.
The pre-check returns a decision of in_place, migration_required or blocked, with reasons and warnings. The resize returns 202 and an operation_id; poll GET /compute/operations/{operation_id} until status is succeeded. GPU VMs use the same paths under /compute/gpu-vms, with --vm-type gpu plans; the GPU model stays the same.
Verify
Sign in to the VM and check the new size:
On IBEE’s Linux images, the root partition and filesystem grow automatically at boot, so df -h / shows the new size straight away.
What changes and what stays
If the disk didn’t grow (Linux)
Images you built yourself may not grow the filesystem on their own. Grow it by hand:
On Windows, open Disk Management, right-click the C: volume and choose Extend Volume.
Moving to a smaller disk
You can’t shrink a disk in place. To move to a plan with a smaller disk:
- Create a VM on the smaller plan.
- Copy your data to it, for example with
rsync. - Point your DNS records at the new VM’s IP address, check it works, and delete the old VM.
Limits
Troubleshooting
Related pages
- Instance types: every plan’s vCPU, memory and disk
- Create a snapshot: take one before you resize
- Attach volumes: add storage without resizing
- Monitoring: decide whether you need a bigger plan
