Did you know that Google Cloud now gives you two ways to run VMware Cloud Foundation (VCF)? This blog explains what the new VMware solution on Google Cloud asks of your team, and how Xtravirt helps you choose and run the right model.
In September, we wrote about the countdown to Google Cloud’s new self-managed VMware offering. On 27 October 2026, Google made it generally available as VMware solution on Google Cloud across 22 regions and named Xtravirt among its launch partners. Our customers are already asking the right question: “Which model is right for us?”
Xtravirt, a Broadcom partner and VMware Cloud Foundation specialist, resells VCF subscriptions, plans and runs migrations, and operates VCF platforms as a managed service. The first thing to settle is your operating model: who owns the software stack above the hardware, and how much of that ownership does your team want?
Two models, one platform
Google Cloud VMware Engine (GCVE) is Google’s managed service, running VCF 5.2. Google handles host patching, software updates and hypervisor lifecycle, while your administrators work with role-based vCenter privileges. You hand routine maintenance to Google and get turnkey operations in return.
VMware solution on Google Cloud runs VCF 9.x on dedicated Compute Engine Z3 bare-metal nodes in your own Google Cloud project. Your team gets full root access to ESX, vCenter, NSX and the rest of the VCF stack, and decides when to patch, upgrade or hold a version. If your roadmap points to VCF 9, you can run it in Google Cloud today.
Both models give your VMware workloads a home in Google Cloud, and each suits a different kind of team.
What full administrative access gives your architects
With root and hypervisor-level access, your architects can apply custom host configurations, kernel drivers and compliance agents. You connect your backup and security monitoring tools to the stack as you do on-premises, with no provider-specific proxy layer in between. If you protect your VCF estate with Veeam today, you can carry that design across.
Lifecycle scheduling moves to your side of the line. You plan patches and upgrades against your own change calendar, using the VCF Operations lifecycle tooling you run in your data centre. If your business works around fixed change freezes, such as retail peaks or financial year-end, you schedule upgrades around those dates yourself.
Your VMware estate inside your own VPC
Google connects the bare-metal nodes straight to subnets in your own Virtual Private Cloud (VPC), with no private services access peering in between. Your VMware virtual machines sit on the same network as BigQuery, Google Kubernetes Engine (GKE) and Google’s AI services, so your data teams can bring systems of record such as Oracle and SQL Server into analytics and AI projects without rewriting the applications that hold them.
The commercial model: your licence, Google's hardware
VMware solution on Google Cloud works on a bring-your-own-licence (BYOL) basis. You bring your portable VCF subscription, and Google charges for the bare-metal nodes underneath it, with no fee for the solution itself. You can run those nodes on demand, or apply committed use discounts (CUDs), including Flex CUDs, and existing Google Cloud spend commitments.
Cost is a fair question, and the answer depends on density. Z3 nodes are large, so compare cost per workload rather than cost per node. Two VCF 9 capabilities raise the number of workloads each host carries: NVMe Memory Tiering, which extends usable memory onto local NVMe storage, and vSAN Express Storage Architecture (ESA), which runs on the Z3’s local NVMe drives. Broadcom cites total cost of ownership reductions of up to 40% from memory tiering and up to 39% on storage compared with traditional external arrays. Your own figure depends on your workload profile, and an assessment gives you the number for your estate.
Storage can drive your node count as much as compute does. If your workloads need more capacity than vSAN on the Z3 nodes provides, you can add Google Cloud NetApp Volumes instead of adding bare-metal nodes. You can mount NetApp Volumes as supplemental NFS datastores, with snapshots, cloning and replication, or attach iSCSI block storage to guest workloads. With memory tiering stretching each host’s memory and NetApp Volumes carrying the extra capacity, you can size your cluster for the compute your workloads need and scale storage separately.
Xtravirt resells VCF subscriptions, so the team that sizes your licence also designs the platform that runs on it. Build capacity planning into the assessment stage. Google allocates bare-metal hardware through its standard Compute Engine capacity process, and your timeline needs room for it.
Extend your data centre, or protect it
If you run VCF on-premises today, look hardest at the hybrid design. You can run the Google Cloud environment as a workload domain connected back to your existing on-premises management domain, or deploy a dedicated management stack in the cloud if you prefer separation. With the workload domain option, your team manages cloud capacity with its existing policies and processes.
VMware solution on Google Cloud doubles as a disaster recovery site. You can run it cold, warm or as a pilot light, replicating with VMware Live Recovery or HCX, and scale up bare-metal nodes when a business continuity event calls for them.
This matches the phased approach to VCF adoption that we recommend: you adopt the components and locations you need, in the order your business needs them.
Who owns what
Full administrative control means your organisation owns the VCF stack. Google manages the data centres, the bare-metal hardware and the physical network fabric. It provides qualified ESX node images, monitors host health, replaces failed hardware and notifies you before it carries out host maintenance. Google has no access to your VCF credentials. Your team, or your chosen partner, owns the rest:
- VCF architecture, deployment and cluster sizing, including node placement across Google’s availability domains
- Patching, upgrades and lifecycle management, moving to new ESX versions once Google has qualified them for the hardware
- Placing hosts into maintenance mode ahead of Google’s scheduled hardware maintenance
- NSX networking, firewall policy, DNS and encryption
- Integration of backup, disaster recovery and security tooling
Google publishes Terraform modules and a solution toolkit that automate node preparation and VCF Installer deployment, and live patching in VCF 9 cuts the number of host reboots. The decision for your organisation is whose engineers run the platform day to day.
How Xtravirt helps
At Xtravirt, VMware Cloud Foundation is what we do. We are Broadcom 2025 Partner Awards winner for Expert Advantage Consulting Services and have worked with Google Cloud on GCVE since 2024. Google named us among its featured partners for VMware solution on Google Cloud at launch.
For Superdry, our team built a landing zone and GCVE environment within two weeks of sign-off. We then migrated close to 100 servers in short bursts around planned change windows, so key retail dates ran without disruption. Backup jobs fell from days to minutes, and key systems gained 70 to 80% in throughput. Read the Superdry case study.
We built our GCVE 123 methodology on that project: Assess, Pilot, Migrate. Our GCVE Readiness Assessment maps your current estate and licensing, then sizes and prices your future options, so you can compare the two Google models on your own numbers before you commit.
VMware solution on Google Cloud makes a third option possible, which Google calls the partner-managed model. You take administrative control and the VCF 9 platform, and hand day-to-day operations to Xtravirt Managed Services. Our engineers, including the operations team at our delivery centre, run VCF estates for customers today, covering lifecycle management and support through one accountable point of contact. You keep control of the design and the change calendar, and your internal team spends its time on business projects.
Choosing your model
Google Cloud VMware Engine suits you if you want Google to run the platform lifecycle and VCF 5.2 meets your needs. If it does, staying on it is a sound choice.
VMware solution on Google Cloud fits teams that need root-level access, custom integrations, native VPC placement or VCF 9 capabilities in Google Cloud, and have the people to run it.
VMware solution on Google Cloud with Xtravirt Managed Services gives you that control and platform without building a new operations function.
Ask us to review your estate, licence position and team before you choose a model. We will recommend the option that fits best for you, even if that means staying where you are. Find out more about how Xtravirt works with Google Cloud.