Deploy a Vultr Cloud GPU instance with a dedicated NVIDIA GPU for AI, ML, HPC, visual computing, or VDI.
Vultr Cloud GPU instances are virtual machines that run with a fraction of a GPU or one or more full GPUs designed to run AI applications, machine learning, high-performance computing (HPC), visual computing, and virtual desktop infrastructure (VDI). Cloud GPU instances include a dedicated GPU device capable of running multiple applications depending on your resource requirements. Certain Cloud GPU plans can also boot from a bootable Block Storage volume instead of local storage. The volume carries its own operating system and persists independently of the instance, so you can destroy the instance and deploy a replacement from the same volume without reinstalling. The plan's local NVMe drives are presented to the guest entirely as scratch space.
Follow this guide to provision Vultr Cloud GPU instances using the Vultr Console, API, CLI, or Terraform.
For plans that boot from Block Storage, the volume and the instance must be in the same location.
Navigate to Compute and click Instances.
Click Create Instance +.
Under Plan, select Cloud GPU.
Select a GPU family from the sidebar, such as NVIDIA HGX B200, NVIDIA A100 PCIe, or AMD MI300X, based on your workload requirements.
Select a plan from the list based on your vCPU, memory, storage, bandwidth, and price requirements. Plans that boot from Block Storage show Bootable Block Volume in the Storage column instead of a fixed local storage size.
Under Location, select a Vultr location for the instance.
Click Configure.
On plans that boot from Block Storage, select the target volume in the Bootable Block Storage section, or create a new one:
On plans that boot from Block Storage, select an Attachment Method:
The Summary shows the selected volume in the Boot Storage field.
On other plans, under Image Selection and Configuration, select an image source. Available tabs depend on the plan:
Under Server Settings, optionally select an IP Address, SSH Keys, a Startup Script, and a Firewall Group. Plans that boot from Block Storage do not show the Startup Script option.
Enter a value in the Server 1 Hostname field and the Server 1 Label field to identify the instance.
Configure Additional Features for the instance.
linuxuser non-root user with sudo privileges as the default user account instead of root.Review the Summary, then click Deploy to provision the instance.
0 Comments
Be the first to comment and share your perspective with the community.