Google Cloud Adds Self-Managed VMware Cloud Foundation on Bare Metal

Google Cloud announced the general availability of a self-managed VMware solution that runs VMware Cloud Foundation 9.x directly on dedicated bare metal across 22 regions. According to InfoQ's report, the release grants customers full root access across ESXi, vCenter, and NSX. The bare-metal architecture sits alongside Google Cloud's existing managed VMware Engine, matching customer-operated offerings from Oracle and AWS. By deploying unmanaged Z3 hardware, Google transfers lifecycle management, patching, and Broadcom licensing back to customer infrastructure teams and integration partners.

This report examines node specifications, deployment mechanics, operational trade-offs, and architecture boundaries of Google Cloud's unmanaged VMware release. The analysis is designed for cloud architects, infrastructure directors, and virtualization engineers evaluating VMware migrations, Broadcom license portability, or hybrid consolidation strategies. Enterprise teams can determine whether direct root control on dedicated cloud hardware outweighs the operational overhead of manually driving upgrades through VMware tools. Readers will find comparisons against Google-managed VMware Engine, setup prerequisites, storage options, partner-managed alternatives, and unannounced details regarding pricing and migration tooling.

What Google Cloud shipped

The bare-metal platform introduces an unmanaged operating model running VMware Cloud Foundation 9.x on dedicated z3-highmem-192-highlssd-metal instances. Each server node provides 96 physical cores on fourth-generation Intel Xeon processors, 1.5 TB of memory, 72 TB of local NVMe storage, and 200 Gbps networking. Google provisions the hardware and steps back, granting tenant teams root access across ESXi hypervisors, vCenter Server, and NSX network controllers. Group product manager Sunny Dua and director of product management Prashanth Bungale confirmed that Broadcom's launch of VMware Cloud Foundation 9.x drove the creation of this self-managed deployment option.

A key pillar of this release is subscription portability. Abhay Kumar, who oversees hyperscaler relationships in Broadcom's VMware Cloud Foundation division, noted that license portability lets enterprise customers transfer existing subscriptions and run workloads unchanged on Google Cloud. Clients bring their own VMware Cloud Foundation licenses rather than buying bundled software through Google Cloud. Operating across 22 initial regions, this model matches customer-managed capabilities offered by Oracle Cloud VMware Solution since 2020 and AWS through Amazon Elastic VMware Service, while Microsoft Azure VMware Solution remains an exclusively provider-managed service.

What changed for builders in Google Cloud

For systems architects, the launch establishes two distinct operating tiers in Google Cloud. The existing Google Cloud VMware Engine runs VMware Cloud Foundation 5.2 on ve1 and ve2 node families, where Google manages the hypervisor lifecycle, restricts tenants to role-based vCenter privileges, and controls patching. Conversely, the bare-metal offering runs VMware Cloud Foundation 9.x, unlocking full root access across all software layers. Engineering teams are no longer delayed by cloud provider certification cadences when validating new hypervisor capabilities or custom networking, because authority over the VMware stack belongs entirely to the customer.

The bare-metal architecture executes VMware vSAN on local NVMe storage and supports NetApp Volumes as an external datastore target. Google's announcement highlights financial gains, citing up to 40% lower server total cost of ownership from NVMe memory tiering and up to 39% lower storage total cost of ownership through vSAN Express Storage Architecture. However, Google shared these numbers without publishing a baseline or evaluation methodology. Launch customer GXO Logistics only described an early assessment rather than active production execution, meaning enterprise teams must independently verify these efficiency figures on their specific application workloads.

How to install or upgrade Google Cloud

Deploying a self-managed VMware Cloud Foundation environment requires satisfying network prerequisites before launching bare-metal instances. Administrators must enable the Google Cloud project for VLAN-based networking and configure a Virtual Private Cloud network with an 8896-byte maximum transmission unit to support encapsulated virtualization traffic. In addition, engineers must establish dedicated subnets for management traffic, vSAN storage, vMotion migrations, and two distinct NSX network segments. Once network prerequisites are in place, Google provisions physical nodes using a VMware solution toolkit that operators execute either through the cloud console or automated Terraform configurations.

# Initialize and apply the VMware solution toolkit modules using Terraform
terraform init
terraform apply

The automated toolkit provisions bare-metal ESXi hosts with spread placement, configures VMkernel interfaces and Cloud DNS records, and deploys the VMware Cloud Foundation Installer appliance with a pre-validated configuration. After this initial automation completes, Google steps back and hands full operational ownership to the customer. Hypervisor maintenance, security updates, and major software upgrades do not arrive through Google Cloud channels; instead, customer operations teams or contracted system integrators must plan and execute patching through VMware Cloud Foundation Operations tools using their portable Broadcom software subscriptions.

Gotchas and compatibility in Google Cloud

The primary trade-off of self-managed VMware is shifting operational responsibility from the cloud provider back to customer teams. Launch partner Xtravirt noted that full control over a VMware Cloud Foundation estate is only worthwhile if an organization wants that maintenance duty. While some enterprises require root control, others want cloud agility without tasking engineers with hypervisor patching during off-hours. For organizations lacking internal administrative capacity, Google highlighted six systems integrators—Accenture, HCL, IBM, Infosys, Tata Consultancy Services, and Wipro—that deliver managed operations on top of the customer-owned bare-metal stack.

Notable commercial and technical omissions accompany this general availability launch. Google Cloud published no pricing schedules, provided no service level agreement terms, and omitted the names of the 22 initial launch regions. Additionally, Google offers no native migration path or automated conversion tools to transition workloads from VMware Engine's managed VMware Cloud Foundation 5.2 environment to the self-managed 9.x architecture. While AWS has supported VMware Cloud Foundation 9.0 and 9.1 since July, Google Cloud customers must consult Google sales accounts or authorized partners to confirm local availability and commercial terms.

What to watch after Google Cloud

In upcoming quarters, infrastructure architects should monitor Google Cloud's regional expansion beyond the initial 22 regions and watch for official migration pathways connecting managed VMware Engine clusters to bare-metal nodes. The managed model absorbed Broadcom's software release cycles and licensing adjustments for enterprise tenants. By shifting to customer-operated infrastructure, organizations must verify whether internal teams can handle Broadcom's ongoing update cadence directly. Prospective customers should also watch whether Google Cloud publishes transparent list pricing, cluster sizing documentation, and uptime service level agreements for the dedicated Z3 hardware.

Cloud competition will accelerate as customer-operated virtualization stacks become standard hyperscaler options. With Oracle Cloud VMware Solution operating since 2020 and Amazon Web Services expanding its Elastic VMware Service with VMware Cloud Foundation 9.x releases, Google Cloud's launch underscores an industry shift toward customer hypervisor sovereignty over managed abstractions. Technology leaders will monitor how launch partners price operational support services, and whether production adopters substantiate Google's claimed 40% server and 39% storage cost efficiencies before moving large-scale on-premises VMware environments to bare-metal cloud infrastructure.