virtuallyGhetto

ESXi

Quick Tip – Allow unsupported CPUs when upgrading to ESXi 7.0

by 28 Comments

As outlined in the vSphere 7.0 release notes (which everyone should carefully read through before upgrading), the following CPU processors are no longer supported:

  • Intel Family 6, Model = 2C (Westmere-EP)
  • Intel Family 6, Model = 2F (Westmere-EX)

To help put things into perspective, these processors were released about 10 years ago! So this should not come as a surprise that VMware has decided remove support for these processors which probably also implies the underlying hardware platforms are probably quite dated as well. In any case, this certainly has affected some folks and from what I have seen, it has mostly been personal homelab or smaller vSphere environments.

One of my readers had reached out to me the other day to share an interesting tidbit which might help some folks prolong their aging hardware for another vSphere release. I have not personally tested this trick and I do not recommend it as you can have other issues longer term or hit a similiar or worse situation upon the next patch or upgrade.

Disclaimer: This is not officially supported by VMware and you run the risk of having more issues in the future.

Per the reader, it looks like you can append the following ESXi boot option which will allow you to bypass the unsupported CPU during the installation/upgrade. To do so, just use SHIFT+O (see VMware documentation for more details) and append the following:

allowLegacyCPU=true

There have also been other interesting and crazy workarounds that attempt to workaround this problem. Although some of these tricks may work, folks should really think long term on what other issues can face by deferring hardware upgrade. I have always looked at homelab as not only a way to learn but to grow yourself as an individual.

Note: The boot option above is only temporarily and you will need to pass in this option upon each restart. It looks like this setting is also not configurable via ESXCLI which I initially had thought, so if you are installing this on a USB device, the best option is to edit the boot.cfg and simply append the parameter to kernelopt line so it'll automatically be included for you without having to manually typing this. If this is install on disk, then you will need to edit both /bootbank/boot.cfg and /altbootbank/boot.cfg for the settings to passed in automatically.

This is ultimately an investment you are making into yourself, so do not cut yourself short and consider looking at a newer platform, especially something like an Intel NUC which is fairly affordable both in cost as well as power, cooling and form factor.

Really cool updates with OVFTool 4.4 and support for vSphere 7

by 5 Comments

vSphere 7 has officially GA'ed this morning and with folks starting to download ESXi and the vCenter Server Appliance, do not forget about all the supporting tools such as the latest PowerCLI 12.0 release which includes a number of enhancement as well as the various vSphere Management and Automation SDKs.

One of my most frequently used tools on a daily basis, some times even more than PowerCLI is OVFTool which is now at version 4.4 which officially supports vSphere 7 but it also includes a number of really awesome enhancements and bug fixes. 

While looking over the OVFTool release notes, I noticed a few interesting tidbits that I thought was worth calling out:

OVF Tool now can upload disk files to the host in parallel, and download disk files from the host in parallel. OVA is unsupported. Parallelism is limited by the number of CPUs. See the --parallelThreads=N option in the OVF Tool User's Guide for details.

This is a most welcome feature for customers with extremely large VMs where upload and/or downloads of OVAs can take a considerable amount of time as only a single CPU thread is used. With this feature, you can now enable multiple CPU threads with the --parallelThreads parameter which should really with performance! Even for smaller size VMs, you can still benefit if you have additional CPU resources to allocate and something I will be using going forward!

For multi-disk virtual machines, OVF Tool now includes the --multiDatastore flag to specify datastore per disk. See the OVF Tool User's Guide for details.

This is another welcome feature for customers where you might have an OVA that contains multiple VMDKs and want to explicitly place them on specific datastore.

The ARM64 architecture on Linux is now supported.

Finally, I thought this was very interesting to see that OVFTool has been ported over to ARM64 for Linux which means we can run now run OVFTool on a Raspberry Pi or even an Amazon A1 EC2 Instance! This might come handy in the future and I wonder if OVFTool for ESXi would be the next logical step? 🙂

I highly recommend you check out the rest of the release notes as it contains many more enhancements and fixes, many of which I have reported from the community and/or by our customers. I think this is certainly one of the tools you can upgrade immediately as it has great backwards compatibility with older vSphere releases but you can also take advantage of all the new features mentioned above immediately. If there are other OVFTool improvements or enhancements you really would like to see, feel free to leave a comment along with the use case and I will past that on to Engineering.

Sonnet Solo5G Multi-Gig (1G/2.5G/5G) USB Adapter works with ESXi

by 2 Comments

Last week I caught this tweet from Blake Garner who is an active VMware Community member that I follow and I came to learn that Sonnet just launched their first Multi-Gigabit (1GbE, 2.5GbE & 5GbE) USB Network Adapter called the Solo5G.

This of course piqued my interest for VMware Homelabs as last year we had just enabled the first Multi-Gigabit USB Network Adapter from QNAP supporting ESXi using the popular USB Native Driver Fling for ESXi. The QNAP device uses an Aquantia chipset and I had a funny suspicion that the Sonnet device might be using either the exact same or simliar chipset.

To confirm my theory, I reached out to the folks over at Sonnet and they were kind enough to send me a unit for validation which just arrived earlier this week. I had an Intel NUC 10 (Frost Canyon) already running and I just plugged it in and to my surprise it worked immediately since it already had the USB Native Driver Fling installed.


So there you have it, same chipset as the QNAP and best of all this device is only $79.99 USD which be purchased directly from Sonnet here. As of writing this blog post, the Solo5G is much cheaper than the QNAP. In fact, it seems the price of the QNAP has significantly increased since I had first blogged about it. I think multi-gig NICs both USB-based but also PCIe and respective switches is starting to become more mainstream, at least in the consumer markets and this is certainly an easy way to add additional bandwidth without breaking the bank. Big thanks to the folks at Sonnet and Blake for sharing the news!

Decoding Intel NUC “Canyon” Generation with CPU “Lake” Generation Codenames

by 9 Comments

Swift Canyon, Baby Canyon, Bean Canyon, Provo Canyon, Kaby Lake, Whiskey Lake, Coffee Lake ... these are just some of the Intel codenames that either refer to a NUC platform or CPU generation. I can understand the need for codenames, however for consumers, the various names are often confusing and being able to grok at which system is the "latest" is not always trivial. In some cases there are multiple updates to different generations of the platform all happening within a short period of time and most online sites may swap between codenames and the official "Nth" generation nomenclature.

I have been working with the Intel NUC platform from a VMware standpoint since the 6th Generation back in 2016 and even I still get confused at times on what is the latest "Canyon" NUCs and their respective "Lake" CPU generations. I can not imagine how complicated this might feel for some of our customers who are updating their VMware homelab every couple of years or someone who is just starting out for the first time. To not only help keep myself sane as I often get asked about Homelabs, literally on a weekly basis and to help educate others within out community, I have created a document which maps all Intel NUCs (full height) to their respective Nth generation along with the respective CPU architecture used in each platform.

[Read more...] about Decoding Intel NUC “Canyon” Generation with CPU “Lake” Generation Codenames

ESXi on the new 2019 Apple Mac Pro

by 11 Comments

Inquiries from customers on the support for ESXi on the latest 2019 Apple Mac Pro 7,1 has slowly been trickling in since the release of the system in late December. Officially, VMware currently does not support this platform and until we have a unit in-house to investigate further, this is the official stance.

With that said, several folks from the community have reached to me and shared some of their findings as it relates to ESXi with the new Mac Pro. A huge thanks goes out to Mike Rimmer who was able to go through the installation process and identified that the on-board NICs were not automatically detected by ESXI and the installation was unable to proceed. With the extensibility of the Mac Pro, Mike was able to add a supported Intel-based NIC to the system so that we could further understand the issue.

Upon closer investigation, it looks like the new Mac Pro uses two Aquantia based 10GbE NIC which is simliar to the 2018 Mac Mini which requires the Aquantia ESXi driver which was developed earlier last year.

AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]
Vendor ID: 0x1d6a
Device ID: 0x07b1

Although Mike did not have a chance to confirm this assumption, I did get validation from another customer who made the same observation when he attempted to install ESXi and once the Aquantia ESXi driver was incorporated into the latest ESXi 6.7 Update 3 image, both on-board NICs were automatically picked up by ESXi and installation was successful.

UPDATE (04/28/20) - ESXi 6.7 Patch 02 resolves a number of the issues mentioned below, please take a look at this blog post here for more details.

UPDATE 1 (01/16/19) - Thanks to our Graphics team who was kind enough to loan me their 2019 Mac Pro which literally came in yesterday! I had an idea which I wanted to run an experiment on which was to add a PCIe card w/M.2 NVMe SSD and see whether or not the Apple T2 Security Chip would have any affect on whether or not ESXi would be able to see the device. I was not super optimistic but I had a need for an additional M.2 device, so I went ahead and purchased a $15 PCIe adaptor. I was pleasantly surprise to see that ESXi not only detected the device but I was able to format a local VMFS volume and power up a functional VM! I guess this makes sense as only the Apple SSD's are cryptographically tied to the T2 chip and other PCIe devices would not be and this would allow customers to take advantage of this system right now for running non-MacOS guests (yes, T2 still affects the SMC).

I also ran another experiment by connecting a Thunderbolt 3 chassis which also had a supported M.2 NVMe to see if I was going to be lucky again. Although it looks like ESXi 6.7 Update 3 has resolved the PSOD'ing issue, ESXi was not able to see anything on the other end.

Note: Secure Boot must be disabled on the Mac Pro before you can install ESXi, you can find the instructions in this Apple KB.


This was certainly some good news but like the 2018 Mac Mini, the new 2019 Mac Pro also ships with the Apple T2 Security Chip which has proved challenging for ESXi as mentioned here along with some known caveats. For now, I would hold off making any purchases of the new Mac Pro if you intend to run ESXi. VMware does officially support ESXi on the last current generation of Mac Pro 6,1 along with Mac Mini 6,2 and Mac Mini 7,1 which are all on the official VMware HCL.

I will continue to update this article as new information and findings are shared with me.

Intel NUC 9 Pro & Extreme – First “Modular” NUC

by 21 Comments

The highly anticipated "modular" Next Unit of Computing (NUC) has just been announced at the Consumer Electronic Show (CES) this week, dubbed the Intel NUC 9 Pro (codename Quartz Canyon) and NUC 9 Extreme (codename Ghost Canyon). Boy am I super excited for this new platform and what it could mean for the VMware Community! 😍

Immediately off the bat, you can see that this is not your typical NUC "cube" form factor. Intel has completely redesigned the system from the inside and out, more on this in a bit. The key difference between the two NUC 9 variants (Pro and Extreme) are the CPU options, which are detailed below. For the remainder of this article, I will be focusing on the Pro version of the NUC 9 and I will call out any differences where applicable.

The use of the word "Pro" is also quite fitting as Intel is positioning this system as a high-end prosumer to Mid-Enterprise device compared to the traditional NUC. The NUC 9 Pro is targeting more demanding workloads such as Digital Content Creation, CAD/Manufacturing and Financial Service applications that either require a high-end graphics card or AI module for computing. When I first heard about this system from Intel, it conceptually reminded me of Apple's recent 2019 Mac Pro, which is also designed with modularity in mind and can cater to a variety of use cases.

Speaking of use cases, although Virtualization is not a target use case for this new platform, VMware customers have been taking advantage of the Intel NUCs for a number of years now and it is still by far the most popular platform for running a vSphere/vSAN/NSX Home Lab. However, one common complaint I often hear about the current generations of NUCs has been its CPU and I think the new NUC 9 Pro/Extreme will be a nice contender for current alternatives like the popular Supermicro E200-8D. Thanks to Intel, I was able to get my hands on a pre-production NUC 9 Pro unit for testing, so lets take a closer look at what this new platform has to offer!

[Read more...] about Intel NUC 9 Pro & Extreme – First “Modular” NUC