Provision an Arm Neoverse VM on Google Cloud

In this section, you provision a Google Axion C4A VM on Google Cloud Platform (GCP) using the c4a-standard-4 machine type, which provides 4 vCPUs and 16 GB of memory.

Note

For general guidance on setting up a Google Cloud account and project, see the Learning Path Getting started with Google Cloud Platform .

Provision a Google Axion C4A VM in the Google Cloud Console

Open the Google Cloud Console and go to Compute Engine > VM instances, then select Create instance. Give the instance a name, and choose your preferred Region and Zone.

Under Machine configuration, set the series and machine type:

  • Set Series to C4A
  • Set Machine type to c4a-standard-4

Image Alt Text:Google Cloud Console VM creation page with C4A series and c4a-standard-4 machine type selectedCreating a Google Axion C4A VM in the Google Cloud Console

Under OS and storage, select Change and choose an Arm64-based image. For this Learning Path, select SUSE Linux Enterprise Server with the Pay as you go license type, then select Select to apply.

Under Networking, enable Allow HTTP traffic and Allow HTTPS traffic, then select Create to launch the VM.

After the instance starts, select SSH next to the VM in the instance list to open a browser-based terminal session.

Alternatively, if you have the gcloud CLI installed, you can connect from a local terminal using gcloud. From the SSH dropdown, select View gcloud command and run that command from your terminal.

Image Alt Text:Google Cloud Console VM instances list with SSH button highlighted for a running C4A instanceConnecting to a running C4A VM using SSH

A new browser window opens with a terminal connected to your VM.

Image Alt Text:Browser-based terminal window displaying a command prompt on a SUSE Linux system running on Google Axion C4ATerminal session connected to the VM

What you’ve learned and what’s next

You’ve successfully created a Google Cloud C4A virtual machine running on Arm Neoverse-V2 and opened an SSH session. Next, you’ll install OpenJDK and run a comprehensive PAC/BTI validation script.

Back
Next