WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / VMware Cloud Foundation / Workaround for single NIC using NFS storage with VCF 9.0

Workaround for single NIC using NFS storage with VCF 9.0

07.15.2025 by William Lam // 1 Comment

VMware Cloud Foundation (VCF) 9.0 brings additional flexibility by supporting multiple types of principal storage: vSAN (OSA/ESA), Fibre Channel & NFS v3 that users can now choose from.


Right before heading out for PTO a couple of weeks ago I was experimenting with NFS as my principal storage for deploying my initial VCF 9 Fleet with a Minisforums MS-A2 system. While the MS-A2 does have multiple network adapters that are supported with ESXi 9.0, I only had the ethernet NIC connected.

While a single NIC can be used to deploy VCF 9.0, especially when using vSAN as the principal storage. However, in my testing with NFS and a single NIC, the migration from Virtual Standard Switch (VSS) to Virtual Distributed Switch (VDS) ran into some issues.

Note: When using NFS as your principal storage, the NFS network must reside in its own dedicated VLAN (e.g. can not be shared with the ESXi Management Network)

Upon further troubleshooting, as I was still able to connect to the vCenter Server, I immediately saw the problem. The single NIC had already been migrated to VDS, but the VMkernel interface and respective portgroup for the NFS traffic was still on the VSS, which no longer had connectivity.


The fix was straight forward, using the vSphere UI in vCenter Server, initiate the migration of the NFS VMkernel interface and ensure you are selecting the distributed portgroup that has already been created.


Once the NFS VMkernel is running on the VDS which is backed by our single NIC, you can then restart the VCF Installer deployment and it will pick up right where it had left off!

Categories // VMware Cloud Foundation Tags // nfs, VCF 9.0

Comments

  1. *protectedWoody says

    10/11/2025 at 8:17 am

    Hi,

    I encountered an error during the validation phase while deploying VCF 9 using NFS storage.

    Under NFS Datastore Configuration, the remediation message states:
    Ensure that the datastore is mounted on the host.

    I tried mounting the NFS datastore on vSwitch0 using a second VMkernel for NFS traffic, but then received another error:

    vSwitch0 cannot have more than one VMkernel.

    Could you please advise on how I should proceed with the validation and deployment?

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Realtek Network Driver for ESXi 11/12/2025
  • Quick Tip - Configure Nested ESX Cores per CPU for Optimal Licensing 11/11/2025
  • Quick Tip - VCF 9.0.1 upgrade files now available on Broadcom Support Portal (BSP) 11/10/2025
  • Auditing ESX DCUI Logins 11/10/2025
  • Capturing Kasa Smart Plug Power Metrics using VCF Operations Management Pack Builder 11/07/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...