WilliamLam.com

Quick Tip - How to monitor when ESXi filesystem and partitions are filling up?

by // 3 Comments

Here is another tidbit on how you can leverage the power of vSphere Events, which now includes over 2K+ as of vSphere 8.0 Update 1 to help monitor when an ESXi filesystem and/or partition is low on disk space.

With vSphere 6.7 or later, we have two events that you can use to help alert when either an ESXi ramdisk (e.g. /var) or VFAT partition (e.g. bootbanks) has filled up.

  • Ramdisk: esx.problem.visorfs.ramdisk.full
  • VFAT: esx.problem.vfat.filesystem.full.other

When either of these occur, you can easily find them under the Monitor->Events section for an ESXi host as shown in the screenshot below.

[Read more...]

ESXi on ASUS PN64-E1

by // 23 Comments

There are not many small form factor kits out there right now that supports Thunderbolt 4, so I was really interested in what ASUS had to offer with their release of the PN64-E1.


I have actually never worked with an ASUS kit before, so I was definitely looking forward to getting my hands on one of this system and see what capabilities it can enable for the VMware community. I initially learned about this platform last year with their PN64, but in speaking with ASUS, they mentioned I should really check out their newest offering, the PN64-E1, which has several new enhancements over their previous model.

So here is your first look at the ASUS PN64-E1!

UPDATE (02/20/25) - 128GB (2x64GB) DDR5 SODIMM memory is fully functional with PN64-E1, please see this blog post for more information.

[Read more...]

Benefits of VM Templates (VMTX) in vSphere Content Library

by // 13 Comments

A commonly miss-understood capability of the vSphere Content Library is managing and distributing Virtual Machine Templates (VMTX), which was introduced in vSphere 6.7 Update 2.

When vSphere Content Library was first released in vSphere 5.0, content was distributed by using a pull-based replication where the subscriber vCenter Server would setup initiate the content subscription to the publisher vCenter Server and then content would then be downloaded to the subscriber vCenter Server as shown in the diagram below.


This initial architecture of vSphere Content Library made it extremely easy for any vCenter Server, regardless of their vCenter Single Sign-On domain, to create a subscription and download content (ISO, OVF/OVA and other files) from the vSphere Content Library of the publisher vCenter Server.

The creation of the vSphere Content Library subscription was managed completely by the individual subscribing vCenter Server as long as it knew the subscription URL and any credentials that may have been configured and of course connectivity to the publisher vCenter Server. While this made it easy for anyone to subscribe content from a vSphere Content Library, it also meant for larger organizations with many vCenter Server(s), an additional task was required to configure each subscribing vCenter Server.

[Read more...]