Back for a fifth year, the Extreme Performance Series will continue the tradition of exploring some of the exciting work being done at Broadcom. The following series of blog posts is all new for 2025 and will be released starting during the week of VMware Explore.
Holodeck 9.1 deploys nested VCF 9.1, 9.0.x and 5.2.x labs. HoloRouter, host requirements, download location, deployment commands and known issues.
Short answer: Holodeck is VMware’s free toolkit for deploying a nested VCF lab. It runs on a single ESX host or on a vSphere cluster. The current release, Holodeck 9.1, deploys VCF 9.1.0.0, 9.0.x and 5.2.x, plus VVF. You download the HoloRouter OVA from the Broadcom Support Portal and upload the VCF Installer and ESX binaries to it. Then you run New-HoloDeckConfig and New-HoloDeckInstance in PowerShell on HoloRouter. It is a lab tool only; VMware does not support it.
Holodeck environment overview (from the official Holodeck documentation)
Holodeck VCF 9: which release deploys which VCF version
The table below is taken from the official Holodeck release notes. Each release lists the minimum ESX version for the physical host.
For VCF 9.0.0.0, 9.0.1.0 and 9.0.2.0, the docs recommend VCF Installer 9.0.2.0. VCF Installer 9.0.0.0 is no longer supported for nested deployments.
If you want 9.1.0.0, use VCF Installer 9.1.0.0.
Starting with 9.0.2, -InstanceID is mandatory. The Day 2 tasks that used to run with -Interactive now live in Update-HoloDeckInstance.
What is HoloRouter?
HoloRouter is a Photon OS appliance, delivered as an OVA, and it is the backbone of every Holodeck lab. The Holodeck PowerShell module comes built into it. HoloRouter provides these services to the nested environment:
DNS, DHCP and NTP
L3 routing between the nested VLANs and a firewall
BGP peering with the NSX Tier-0 gateway
A proxy for the VCF Installer
Job scheduling
An optional webtop desktop on port 30000 of the management IP
Holodeck 9.1 adds several services, all on the fixed vcf.lab domain behind HTTPS: Technitium DNS, HashiCorp Vault, Authentik SSO, an internal CA, and an optional GitLab (“Enable GitOps”) that can trigger deployments from a pipeline.
Default networking uses the 10.1.0.0/20 range for Site A and 10.2.0.0/20 for Site B. The VLANs are 0 and 10–25 for Site A and 40–58 for Site B. You can pass your own /20 CIDR, a VLAN start value and a DNS domain instead. The deployment runs against a centralized JSON config and is idempotent: if it fails, you rerun the same command and it continues where it stopped.
VCF 9 home lab requirements for Holodeck
These are the recommended physical host resources from the official pre-requisites. Holodeck 9.1 applies soft validation: it warns you instead of blocking when you are below them.
Target
Single site CPU / RAM / disk
Dual site CPU / RAM / disk
VCF 9.1
48 / 650 GB / 2.2 TB
96 / 1.5 TB / 5 TB
VCF 9.0 (VCF Automation, vSAN OSA)
24 / 325 GB / 1.1 TB
48 / 768 GB / 2.5 TB
VCF 9.0 (VCF Automation, vSAN ESA)
32 / 325 GB / 1.1 TB
64 / 768 GB / 2.5 TB
VVF 9.1
24 / 512 GB / 2 TB
48 / 1 TB / 4 TB
VVF 9.0
12 / 256 GB / 1 TB
24 / 512 GB / 2 TB
VCF 5.2
16 / 384 GB / 2 TB
32 / 1 TB / 4 TB
Other requirements from the docs:
Target: a stand-alone ESX host or a vCenter-managed cluster. vSphere 8.0 U3 and 9.0 are tested. Use SSD/NVMe storage and have NTP running on every target host.
Switch: MTU 9000 on the vSS, vDS or NSX segment.
Port group: a dedicated trunk port group (VLAN 4095 on a vSS) with Promiscuous mode, MAC address changes and Forged transmits set to Accept. An NSX overlay segment with matching segment profiles also works.
HoloRouter: 6 vCPU, 12 GB RAM and 75 GB disk, plus one external IP per Holodeck environment.
Memory tiering: not recommended for nested labs.
Licensing: VCF 9.x runs in “License Later” mode for 90 days (60 days for 5.2.x). After that you must license or redeploy.
Holodeck 9.0 / 9.1 deployment flow
Download. Get the HoloRouter OVA (and optionally the Offline Depot OVA) from the Holodeck product files on the Broadcom Support Portal. The docs say you must be signed in with an entitled account. The VCF Installer OVA and the ESX ISO come from the VCF downloads and need a Broadcom account with VCF entitlement.
Deploy HoloRouter. Deploy the OVA to the ESX host or the vCenter. Connect one external port group for management and the trunk port group for Site A/B. Set the password, and enable SSH and webtop if you want them.
Stage the binaries. Copy the binaries into the matching version folder, for example /holodeck-runtime/bin/9.0.2.0/ or /holodeck-runtime/bin/9.1.0.0/.
Create a config and deploy. SSH to HoloRouter and run the commands shown below.
scp /<local-path>/<ESX ISO File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/
scp /<local-path>/<VCF Installer OVA File Name> root@<Holorouter-IP>:/holodeck-runtime/bin/9.0.2.0/
ssh root@<holorouter-ip>
pwsh
New-HoloDeckConfig -Description <Description> -TargetHost <vCenter/ESX IP or FQDN> -Username <user> -Password <password>
New-HoloDeckInstance -Version "9.0.2.0" -InstanceID <id> -ManagementOnly -vSANMode OSA
If you leave out -ManagementOnly, you get a full stack: a 4-host management domain plus a 3-host workload domain. Optional switches add more components:
-NsxEdgeClusterMgmtDomain adds an NSX Edge cluster in the management domain.
-DeployVcfAutomation deploys VCF Automation.
-DeploySupervisorMgmtDomain or -DeploySupervisorWkldDomain deploys a Supervisor.
-DepotType Offline uses the offline depot.
-ProvisionOnly deploys only the nested hosts and the VCF Installer, for a manual greenfield install.
-VVF deploys VVF instead of VCF.
In a new PowerShell session, reload the config with Get-HoloDeckConfig and then Import-HoloDeckConfig -ConfigId <id> -Site a. In 9.1, -Site is mandatory. Use one config per deployment.
Known issues worth knowing before you start
Pre-check error “No trunk port groups found”. Create the trunk port group (VLAN 4095 plus the three security settings) and rerun the check.
Pre-check error “NTP service is not running on target host”. Configure and start NTP on the physical host.
DNS resolution fails during deployment. This happens if you gave HoloRouter an upstream DNS server as an FQDN instead of an IP address. Use an IP. The release notes include a DNSMASQ ConfigMap fix.
VVF 9.0.0.0 with VCF Installer 9.0.2.0 fails at “Generate Workload Domain Runtime Data Model”. Download the vCenter 9.0.2.0 bundle as well, then resume.
VCF 5.2.x ends with “No route to host” at Sync-HolodeckComponents. You can ignore it; VCF 5.2 has no VCF Operations to query.
vSAN ESA uses more nested storage than expected. Plan disk space above the minimum.
Older 9.0/9.0.1 issues are fixed in 9.0.2. These include the expired NSX Edge OVF certificate (Broadcom KB 424034) and “Validate NSX Install Image is Available”. Use the current release.
I hit a different problem myself: Holodeck 9.0.2 stuck at the VCF Installer bundle step. The fix is in the related post below.
Holodeck was presented at VMware Explore 2025 in session CODEQT1247LV, “Automagically Deploy VMware Cloud Foundation 9.0 in Homelab Using VMware Cloud Foundation Holodeck Toolkit”:
At today’s VMware Explore general session, Chris Wolf showcased Intelligent Assist for VMware Cloud Foundation — bringing AI-powered assistance directly to our users.
Today at VMware Explore’s general session you saw Chris Wolf demonstrate Intelligent Assist for VMware Cloud Foundation, providing AI-powered assistance for our users. In this blog, we’ll take a step behind the curtain to see how these capabilities are running in VCF, using AI features that […]
Today at hashtag#VMwareExplore, Broadcom and AMD announced an expanded collaboration to deliver private, secure, and high-performance AI infrastructure for enterprises.
Artificial Intelligence (AI) is rapidly transforming industries, and Generative AI (Gen AI) is pushing the boundaries of what’s possible, creating new content and redefining value creation. However, enterprises face significant challenges in AI adoption, especially concerning privacy, data […]
VMware Private AI Services Now Included in VCF Subscription Big news from today’s VMware Explore general session with Chris Wolf 🎉 What was once sold separately is now part of the platform — VCF Private AI Services are now included in your VMware Cloud Foundation subscription.
This marks a major step forward in unleashing the power of Private AI, fueled by Broadcom and NVIDIA innovations.
Enterprises can get tremendous productivity and business transformation from AI. With VMware Private AI Foundation with NVIDIA, Broadcom and NVIDIA aim to unlock AI and unleash productivity with lower TCO. Recently with VCF 9.0, Broadcom and NVIDIA released several features in VMware Private AI Foundation with NVIDIA to further our mission of providing private and … Continued The post Unleashing the Power of Private AI: New Innovations from Broadcom with NVIDIA appeared first on VMware Cloud…Read More
The Communities Lounge is the main place for the VMware community to meet and reconnect at Explore, right at the center of the event. I like to think of it as one of the great train stations of old cities. It carries a timeless feeling: the place where journeys cross, where you meet faces […]
VMware Explore 2025 in Las Vegas Day 1 Recap | August 25, 2025 If you heard the collective buzz across the Venetian Convention and Expo Center today, that was Day 1 of VMware Explore in Las Vegas coming to life. You crushed it—140 sessions across all four tracks, endless hallway conversations, and a few “just … Continued The post VMware Explore 2025 in Las Vegas | Day 1 Recap appeared first on VMware Explore Blog.
Continuing on from the VMware Data Services Manager (DSM) 9.0 introductory videos from my most recent post, these next two videos look at how to configure VMware Cloud Foundation (VCF) Automation in VCF 9.0 with DSM to provide a true DBaaS (Database as a Service) experience to your VCF tenants […]
Things to do in Las Vegas beyond the casinos, for VMware Explore attendees with a free afternoon or an extra day.
I hope you’re enjoying yourselves in the spectacular city of Las Vegas! While the Strip is world-famous for its casinos and neon lights, there’s so much more waiting for you beyond the roulette tables. If you find yourself with a bit of spare time, here are some gems you won’t want to miss.
Welcome to Fabulous Las Vegas Sign
Kick off your adventure at the iconic “Welcome to Fabulous Las Vegas” sign, located at the southern end of the Strip. It’s the ultimate photo stop and a must-see landmark for every visitor. Arrive early in the morning if you’d like to beat the crowds and grab your selfie without waiting in line.
Ride the Deuce Bus Along the Strip
One of the easiest—and most affordable—ways to explore Las Vegas is the Deuce bus, which runs 24/7 along the Strip. For just a few dollars, you can travel all the way from the Las Vegas sign to downtown. Along the ride you’ll pass mega-resorts, quirky hidden gems, and plenty of photo-worthy spots.
💡 Tip: Tickets are simple to get—just download the RideRTC app
Downtown Las Vegas – Fremont Street
At the end of the bus ride, you’ll land in downtown Las Vegas, the birthplace of the city’s casino culture. Don’t miss Binion’s Casino, where you can take a free photo with one million dollars in cash (yes, real bills!).
By night, Fremont Street transforms into a festival of sound and light, with live music stages, street performers, and the jaw-dropping Fremont Street Experience—a massive canopy that comes alive with LED animations and booming music.
Take a Break From the Strip
When the neon starts to feel overwhelming, step into nature. Just a short drive away lies Red Rock Canyon, a breathtaking desert escape with scenic drives and hiking trails. Or head to Lake Mead, the vast reservoir created by the Hoover Dam. Whether you swim, kayak, or simply relax by the shore, it’s the perfect place to recharge away from the Strip.
Day Trips Beyond Las Vegas
Looking for a true bucket-list experience?
Grand Canyon, Arizona – Standing on its rim and gazing into its endless depths is a moment you’ll never forget.
Antelope Canyon, Arizona – If your journey takes you further east, its smooth sandstone walls, painted in red and gold, create one of the most photogenic spots on Earth.
💡 Tip: To easily browse and book tours, check out the GetYourGuide app
Now Is the Time to Explore!
Las Vegas isn’t just about entertainment—it’s a gateway to adventures, culture, and some of the most stunning natural wonders in the American Southwest. So pack your curiosity, grab your camera, and start discovering!
No in-place upgrade from Aria Operations for Logs 8.18 to VCF Operations for Logs 9.0: deploy fresh, run both, move integrations, then retire 8.18.
Short answer: there is no in-place upgrade from Aria Operations for Logs 8.18.x to VCF Operations for Logs 9.0. Deploy VCF Operations for Logs 9.0 fresh, keep 8.18.x running for historical logs, move integrations and log sources to the new instance, optionally transfer old logs, then decommission 8.18.x (KB 402314).
With the release of VMware Cloud Foundation (VCF) 9.0, Aria Operations for Logs has officially been rebranded as VCF Operations for Logs. However, if you were expecting a simple in-place upgrade, there’s an important caveat: no direct in-place upgrade is supported.
Instead, administrators must deploy VCF Ops for Logs 9.0 as a fresh installation and gradually migrate integrations and data sources from their existing Aria Ops for Logs 8.18.x environment.
Why No In-Place Upgrade?
VMware Aria Operations for Logs version 8.18.x does not support an in-place upgrade path to version 9.0. The architectural and platform changes introduced in VCF 9.0 require a clean deployment.
This means that if you are currently running Aria Ops for Logs 8.18.3, you cannot simply apply an upgrade package. Instead, both versions must temporarily coexist while you complete the transition.
Recommended Migration Approach
Broadcom’s official upgrade guidance outlines the following steps:
Deploy VCF Ops for Logs 9.0
Set up a fresh instance of VCF Ops for Logs in your environment.
Keep your Aria Ops for Logs 8.18.3 instance online, but start unconfiguring existing integrations.
This ensures that historical log data remains accessible, even though new logs will be directed elsewhere.
Reconfigure Integrations on 9.0
Point all your log sources, agents, and integrations to the new VCF Ops for Logs 9.0 instance.
Validate ingestion pipelines to confirm that logs are flowing properly.
Leverage Log Transfer if Needed
Broadcom provides guidance for log transfer, allowing you to move log data from the old environment to the new one.
Decommission the Old Instance
Once all integrations and data have been verified in the new platform, you can safely retire your 8.18.3 deployment.
Key Takeaways
Rebrand Only in Name? Not Quite. While the product name has changed from Aria Ops for Logs to VCF Ops for Logs, the lack of in-place upgrade means the transition is more than cosmetic.
Parallel Operations Are Required. You’ll need to run 8.18.3 and 9.0 side by side during the migration phase.
Fresh Deployment Is Mandatory. Treat this as a new installation rather than an upgrade.
Plan for Migration Effort. Reconfiguring all integrations and log sources can be time-intensive, so schedule accordingly.
Summary
If your organization relies heavily on VMware Aria Operations for Logs today, be prepared for a stepwise migration process rather than a straightforward upgrade. By planning the deployment of VCF Ops for Logs 9.0 carefully—and keeping the old instance online for historical data—you can ensure a smooth transition without losing valuable log visibility.
For more details, consult Broadcom’s official documentation: