This is a guest post by Espen Ødegaard: As VMware has not released a fix yet (regarding issues with SD card and USB drive), I’m still experiencing issues with ESXi 7.0 U2a Potentially Killing USB and SD drives, running from USB or SD card installs. As previous workaround (copying VMware Tools to RAMDISK with option
ToolsRamdisk) only worked for 8 days (in my case), I needed something more permanent, to get the ESXi-hosts more stable (e.g. host being able to enter maintenance mode, move VMs around, snapshots/backup, doing CLI-stuff/commands, etc.).
This is a guest post by Espen Ødegaard: As searching and filtering for events in vCenter Server trough vSphere Client somewhat limited (OK, it really sucks, to be honest), it’s usually much faster using PowerCLI, to retrieve, filter & searching events.
This is a guest post by Espen Ødegaard: After upgrading my 4-node vSAN-cluster (homelab) to ESXi 7.0 build 17867351 U2a, I detected that ESXi had issues talking to the USB device, where the ESXi was installed. I found a related KB from VMware, outlining issues with the new VMFS-L, which started my baseline for troubleshooting VMFS-L Locker partition corruption on SD cards in ESXi 7.0 (83376) In short, it says that the VMFS-L partition may have become corrupt, and a re-install is needed. There is no resolution for the SD card corruption as of the time this article was published
This is a guest post by Espen Ødegaard: I recently ran into a strange issue in my home lab, running ESXi 7.0.2, build 17867351 where Veeam Backup & Replication v10 reported the following error: Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef vm-4013, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce False
I recently got an Elgato Stream Deck for the home office, and I’ve set it up mostly to control OBS Studio for a couple of projects I’m working on. Since I also have a couple of Key Light Airs, I also use it to control them.
While setting it up, I figured I needed a sleep button on it, that basically locks my Macbook and turns off the lights in one fell swoop. Conceptually this seemed like an very easy thing to set up, but it turns out there are some macOS quirks that needs to be addressed for this to work.
By default in macOS High Sierra, or newer, there is a predefined lock screen hotkey:
Command ⌘ + Control ⌃ Q which works very well. In fact, it works a little to well as it turns out.
VMware has just announced the general availability of the new vSphere 7.0 Update 2 release, which offers a bunch of new features and improvements. This includes both new load balancer options for Tanzu, as well as greatly improved security through encryption, better lifecycle management and improvements on vMotion speeds in high bandwidth networks.
On the 23rd of February 2021 VMware issued the VMSA-2021-0002 security advisory and one of the issues it addresses is VMware vCenter Server updates address remote code execution vulnerability in the vSphere Client (CVE-2021-21972). This is a critical issue, and if left unpatched could land your vSphere estate in big trouble as there is already Proof-of-Concepts available for this vulnerability. So get patching as soon as possible! Of course, this can only be exploited if you have access to the VMware vCenter Client, so if the managment plane is isolated that helps mitigate the risk.