WilliamLam.com

PowerCLI 13.0 on Photon OS

by // 3 Comments

I received a question from Andrea Peetz, asking whether the new Image Builder cmdlets, which is part of the new PowerCLI 13.0 release would work with Photon OS 3.0 (PH3)? After speaking with the PowerCLI team, it looks like Photon OS 3.0 is not compatible with the new cmdlets. If you attempt to use one of the Image Builder cmdlets like Get-EsxSoftwareDepot, you will get the following error:

Unable to cast object of type 'System.IO.FileStream' to type 'System.IO.Pipes.PipeStream'.


With that said, if you do not require the Image Builder cmdlets, then the rest of the PowerCLI cmdlets should work just fine.

While I have not used PH3 for quite some time now, I do use Photon OS 4.0 (PH4) on a regular basis. I was curious if I would have better luck with the new Image Builder cmdlets. Unlike PH3 which ships with Python 3.7, which is the required version for the Image Builder cmdlets, PH4 ships with a newer version of Python which is 3.10 and will not work with PowerCLI. We can still meet this requirement, but we will need to install Python via pyenv.

After a quick test, I was able to get the basic Image Builder cmdlets working and while going through a complete end-to-end workflow to make sure everything was working, I ran into a slightly different issue. When using the Export-EsxImageProfile cmdlet to export an ESXi Image Profile to an ISO file, I got the following error:

Can not instantiate 'certified' policy: VibSign module missing.

Quickly debugging the issue with the PowerCLI team, it looks like the VibSign module that has been compiled has a dependency on OpenSSL 1.1 and PH4 ships with OpenSSL 3.0 by default. Luckily, I was able to find a workaround by building the required file from the latest stable OpenSSL 1.1 release. Once the dependency was fulfilled, I was able successfully complete the Image Builder workflow!


Similiar to PH3, if you do not require the use of the Image Builder cmdlets, PowerCLI 13.0 can be installed on PH4 using the instructions below. If you do need to use the Image Builder cmdlets on PH4, you will need to run Step 2 below as that is a required step. I have also reported both of these issues with the PowerCLI team.

[Read more...]

Heads Up - ESXi 8.0 Host Client unable to attach existing virtual disk to VM

by // 11 Comments

A couple of days ago, I had received an email from a customer that after upgrading to ESXi 8.0, they were no longer able to attach an existing virtual disk (VMDK) to a VM using the ESXi Host Client, which is accessible by opening a browser to the Hostname/IP Address of your ESXi host.


After selecting the desired VMDK to attach in ESXi Host Client wizard, the customer had noticed several fields were not populated as shown in the screenshot above and the workflow would not be allowed to complete as these fields are required.

Note: This issue also affects ESXi 7.0 Update 3i and potentially other newer releases, if they also contain the 2.x version of the ESXi Host Client. One workaround, which I have personally verified with ESXi 7.0 Update 3i is to uninstall the bundled esxi-ui VIB and install the prior version by downloading the ESXi offline depot (zip) for ESXi 7.0 Update 3g. While this may not be officially supported, for those that have a standalone ESXi host or using the Free ESXi version, this may be an acceptable workaround until a fix is available in a future patch/update. For detailed instructions, see my reply on this VMTN thread.

[Read more...]

High-end Dell Precision 7770 & 7670 laptops with 128GB memory for ESXi

by // 4 Comments

I have been following the progress on the new Compression Attached Memory Module (CAMM), which was announced earlier this year and is a new laptop memory standard that has been created by Dell. Dell intends to replace the aging SODIMM memory module, which are typically found in laptops and small form factor systems like the popular Intel NUC.

Image from StorageReview

This StorageReview article by Charles Jefferies provides a nice summary of the new CAMM technology and the benefits over the 25 year old SODIMM modules. While the CAMM technology is currently proprietary, Dell has been working with Intel on this standard and have also submitted their design to the Joint Electron Device Engineering Council (JEDEC) for CAMM to become a new industry standard for laptop memory.

My biggest interests with CAMM is the capacity of their modules which can reach up to 128GB for a single CAMM module! For SODIMM, we have been limited to 32GB for a single module for a number of years and this will not be changing any time soon. Just imagine the popular 4x4 Intel NUC with 128GB memory! 🤤

Given CAMM was just announced earlier this year, I was not expecting to see any systems that a consumer could purchase for quite some time. I was actually pleasantly surprise to learn recently, that two new high-end Dell workstation laptops can now be purchased with CAMM memory and also configured with up to 128GB of memory. 😲

[Read more...]