Skip to main content

Region, Hardware and Firmware

Select the data center region, hardware, and firmware for a Virtual Server

Region

Virtual Servers may be deployed across any of data center regions. CoreWeave's data center regions are broken up into three geographical buckets - US East, Central and West. Each provides redundant 200Gbps+ public Internet connectivity from Tier 1 global carriers, and are connected to each other using 400Gbps+ of dark fiber transport to allow for easy, free transfers of data within CoreWeave Cloud.

note

It is generally advised to select the data center region closest to your location.

Deployment method: CoreWeave Cloud UI

From the CoreWeave Cloud UI Virtual Server deployment menu, click the Region expandable, then select the region in which to host the Virtual Server by clicking on it.

Hardware

CoreWeave Cloud offers several high-performance NVIDIA GPUs and CPUs for Virtual Servers. The amount of memory with which a Virtual Server runs can also be specified.

Deployment method: CoreWeave Cloud UI

From the CoreWeave Cloud UI Virtual Server deployment menu, click the Hardware expandable, then select the hardware kind (GPU or CPU) and the hardware itself. Clicking the GPU tab will display all available GPU options, and clicking the CPU tab will do the same for CPU types.

note

For more information on hardware, see Node Types.

The GPU Count, Core Count, and Memory amount (in Gi) are chosen using the sliders at the bottom of the section.

Each hardware selector also displays a meter registering the availability of that hardware type per region.

Resource definition (YAML only)

In the CRD's YAML manifest, the .spec.resources.definition field is used as a way to describe the chosen resources. The default value of this field is a - this is just a placeholder, which can be changed to any string.

Example in plain text:

  spec:
region: LAS1
resources:
cpu:
count: 4
type: amd-epyc-milan
definition: a
memory: 12Gi

Firmware

Firmware identification information for Virtual Servers is set by the Virtual Machine Instance (VMI). The firmware's UUID (MAC address) is set by the BIOS, and its system-serial number is set by the VMI's SMBIOS.

The firmware's UUID defaults a randomly-generated alphanumeric string. Both numbers are static across Virtual Server restarts.

It is optional to set these; if not set, they will have randomly-generated defaults.

note

You can read more about virtual hardware firmware configuration in the Kubevirt documentation, or see how its exposure is implemented in CoreWeave by viewing our API reference.

Deployment method: CoreWeave Cloud UI

In the Cloud UI, firmware options must be set using the YAML editor. Firmware options are not currently exposed through the YAML manifest by default, so they must be added to the key-value map in the manifest.

Example in plain text:

firmware:
uuid: 5d307ca9-b3ef-428c-8861-06e72d69f223
serial: e4686d2c-6e8d-4335-b8fd-81bee22f4815