WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple

Packer reference for VMware Harbor Virtual Appliance

07.08.2021 by William Lam // 2 Comments

I recently had a need to setup a container registry for a project that I was working on and Harbor was of course my default choice. Although Harbor is pretty easy to setup, I did not want to manually go through the installation each time I needed Harbor and I figured it was time to build my own Harbor Virtual Appliance (OVA), just like I have shown in the past with these reference implementations here and here.

UPDATE (02/03/23) - VMware has productized and is now shipping an official VMware Harbor Virtual Appliance (OVA) as part of the latest Tanzu Kubernetes Grid (2.1) release.

Nice to finally see @project_harbor team release official OVA Appliance w/latest @VMwareTanzu Kubernetes Grid 2.1 release https://t.co/gZIW8SckH9

I still remember team reaching out about productizing what I had built back in 2021 🥳https://t.co/IyquqwZgEK

H/T @vmw_rguske pic.twitter.com/vwWsCtOSBe

— William Lam (@lamw.bsky.social | @*protected email*) (@lamw) February 3, 2023

For those interested, you can find the reference implementation for building a Harbor Virtual Appliance at https://github.com/lamw/harbor-appliance

When deploying the Harbor Appliance, you will find the basic OVF properties that I have encoded including networking, credentials, debugging and advanced settings. Hopefully should be pretty straight forward for anyone who has deployed an OVA before to vSphere.

[Read more...]

Categories // Kubernetes, VMware Tanzu Tags // Harbor, Kubernetes, Tanzu Kubernetes Grid, vSphere with Kubernetes

Passthrough of Intel Iris Xe Integrated GPU on 11th Gen NUC results in Error Code 43

07.07.2021 by William Lam // 49 Comments

I recently ran into an issue after enabling ESXi passthrough of the new Intel Iris Xe Integrated GPU (iGPU), which is available with the latest Intel 11th Gen Pro (Tiger Canyon) NUC and SimplyNUC Topaz. After installing the latest Intel Graphics Driver and rebooting the Microsoft Windows 10 (20H2) VM, I noticed Microsoft Device Manager would show the iGPU device with the following error message:

Windows has stopped this device because it has reported problems. (Code 43)


Unfortunately, this generic error message was not very useful in identifying the underlying issue. I was hoping the process was going to be seamless like it was for enabling passthrough of the iGPU in Intel NUC 10 (Frost Canyon) NUC, especially with the higher execution units for the 11the Gen NUC i3 (48 EU), i5 (80 EU) and i7 (96 EU).

I currently have a case open with the Intel NUC team and see if they can help investigate the underlying issue for their driver. For the time being, it looks like passthrough of the new iGPU is not fully functional when using ESXi 7.0 Update 2 and I will update this blog post if/when I have further updates to share.

Categories // ESXi Tags // GPU, Intel NUC, Iris Xe, SimplyNUC

Quick Tip - vSphere Permission to view vSphere with Tanzu Namespaces

07.06.2021 by William Lam // 6 Comments

If you wish to create a custom vSphere Role that has the ability to view vSphere Namespaces which is part of vSphere with Tanzu, you will need to add the user to the following vSphere Single Sign-On Group: ServiceProviderUsers, which is located under Single Sign On->Users and Groups->Groups (2nd page) within the vSphere UI.


Once added, you can logout and log back in and the user should now see the vSphere Namespaces as shown in the screenshot below. In my example, I have a user named william which is created in the default vsphere.local domain and has been assigned the user the vSphere Read Only role along with this additional SSO group. They will be able to view all resources but will not have permission to make any changes to the infrastructure. If you are using Active Directory, the exact same process works and just make sure you log out and log back in for the changes to take effect.

Categories // VMware Tanzu, vSphere 7.0 Tags // permission, vSphere Kubernetes Service

  • « Previous Page
  • 1
  • …
  • 144
  • 145
  • 146
  • 147
  • 148
  • …
  • 567
  • Next Page »

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

  • Ultimate Lab Resource for VCF 9.0 06/25/2025
  • VMware Cloud Foundation (VCF) on ASUS NUC 15 Pro (Cyber Canyon) 06/25/2025
  • VMware Cloud Foundation (VCF) on Minisforum MS-A2 06/25/2025
  • VCF 9.0 Offline Depot using Synology 06/25/2025
  • Deploying VCF 9.0 on a single ESXi host? 06/24/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...