For years, I have dismissed Virtual Machine Hardware version as unimportant. In fact, in this very blog, I may have advocated for leaving VM Hardware Version set at 8, to maintain full compatibility with both the vSphere C# Client and the vSphere Web Client.
Unfortunately, thanks to Spectre and Meltdown, things have changed. Updating your VM Hardware Version also updates the VM BIOS, and that’s an important part in the remediation of Speculative Execution Vulnerabilities, specifically: CVE-2017-5715 ‘Spectre Variant 2’. Continue reading
As we are all aware, recent updates to Shockwave Flash caused the vSphere Web Client to crash on most browser platforms. The interim solution was to install an outdated version of Shockwave Flash, just to access the Web Client. More recently, Adobe Shockwave Flash version 188.8.131.52 was pushed out in updates to Google Chrome (and other browser platforms) that fixes the problem.
- Gone is the choice between “Allow Flash” and “Ask First,”
- Now there is the choice between “Ask First” and “Block sites from running Flash.”
- What’s new is the ability to add allowed sites, including the use of wildcard characters, where Shockwave Flash will run unprompted.
Over the weekend Google pushed out an update to Flash (184.108.40.206) with an update to Chrome (61.0.3163.100) and now vSphere Web Client is broken once again! Continue reading
HPE has quietly withdrawn the HPE Custom Image for ESXi 6.5U1 July 2017 due to purple-screen issues being experienced on a number of current VMware-supported servers (http://vmware.com/go/hcl)!
The particular issue purple screen we saw when deploying this ISO against a HP BL460 G7 was:
#PF Exception 14 in world 6824:sfcb-smx IP 0x1 addr 0x1