WilliamLam.com

AlmaLinux OS 8.4 on ESXi-Arm

by // 2 Comments

I came across this Reddit thread yesterday, announcing the release of AlmaLinux OS 8.4 for Arm and I knew I had to give it a go on ESXi-Arm!

After downloading the ISO, simply create a new Other 4.x Linux VM (1  vCPU/4GB memory) and then boot the ISO to begin the installation. One thing that threw me off the first time I performed the installation was that I forgot to setup networking. It turns out the network interface is actually disabled by default and users must manually toggle the enable button, which I find quite annoying from user experience standpoint. After enabling the networking interface, the rest of the installation went smooth without any issues.


Complete the installation by rebooting and you will now have AlmaLinux OS 8.4 for Arm running on ESXi-Arm 😀


For those interested in setting up Gnome desktop for AlmaLinux, you can follow this tutorial which I used myself.

Note: Thanks to Cyprien, VMware Tools can be installed it looks like an additional repo must be configured by running the following:

dnf config-manager --set-enabled powertools
dnf -y update
dnf install -y git make rpm-build autoconf automake libtool gcc-c++ doxygen fuse-devel gdk-pixbuf2-xlib-devel glib2-devel gtkmm30-devel gtk3-devel libdnet-devel libicu-devel libmspack-devel libtirpc-devel libtool-ltdl-devel libX11-devel libXext-devel libXi-devel libXinerama-devel libXrandr-devel libXrender-devel libXtst-devel openssl-devel pam-devel rpcgen xmlsec1-devel xmlsec1-openssl-devel valgrind-devel libdrm-devel systemd-devel
git clone https://github.com/vmware/open-vm-tools.git
cd open-vm-tools/open-vm-tools/
autoreconf -i
./configure
make
make install

Next, we need to create a new systemd unit file so that we can manage the VMware Tools service, do to so, run the following command:

cat > /etc/systemd/system/vmtoolsd.service << EOF
[Unit]
Description=
Description=Open VM Tools
After=
After=network-online.target

[Service]
ExecStart=
ExecStart=/usr/local/bin/vmtoolsd
Restart=always
RestartSec=1sec

[Install]
WantedBy=multi-user.target
EOF

Finally enable and start the VMware Tools service by running the following command:

systemctl enable vmtoolsd.service
systemctl start vmtoolsd.service

ESXi on SimplyNUC Ruby and Topaz

by // 5 Comments


Ruby and Topaz is the latest in SimplyNUC's custom lineup of NUC-like systems which they started to build and sell a couple of years ago. The Ruby platform is based on the AMD Ryzen 4000 Series and the Topaz platform is based on Intel 11th Gen Tiger Lake Series.

Given the current global chip shortage that may last a couple more years, it may take some time before everyone can get their hands on either of these platforms, but I have slowly been seeing new inquiries about these platforms as folks are starting to receive their units. Of course, the most popular inquiry that I have received is whether these systems can be used with ESXi? 😀

Topaz

Since Topaz uses the same Intel 11th Gen Tiger Lake CPU, it works exactly the same as the Intel NUC 11 Performance (Panther Canyon) and Intel NUC 11 Pro (Tiger Canyon), which requires the Community Networking Driver for ESXi to enable both the 2.5GbE and 1GbE onboard network adapters when installing ESXi on Topaz. One really nice feature of Topaz is that all three models (i7, i5 and i3) include dual onboard network adapters, where as this option is only available on Intel NUC 11 Pro as an add-on card that must be purchased separately.

Here is screenshot of the latest ESXi 7.0 Update 2 release running on Topaz

Ruby

Although there was quite a bit of community interests in running ESXi on the Ruby platform, I was not particularly optimistic mainly because both the onboard network adapters are from Realtek. Since there are no ESXi networking drivers from Realtek, ESXi would not be able to detect either of the network adapters which is the same behavior that I have seen for other AMD-NUC like kits such as the ASRock Gen 1 and Gen 2 systems.

Unfortunately, there has been no progress with Realtek joining VMware's I/O Vendor Partner (IOVP), which would enable the development of an official network driver for ESXi. Although folks can add networking to these platforms leveraging the USB Network Native Driver for ESXi, it is less than ideal. At this point in time, I can not recommend Ruby or other AMD-based NUCs that uses Realtek-based network adapters.

Here is screenshot of ESXi 7.0 with USB network adapter running on Ruby

IT Admins can be a key enabler to an organizations App Modernization efforts

by // Leave a Comment

Whether you call it Digital Transformation, Digital First, Application Modernization (App Modernization) or some other fancy name, the fact of the matter is, almost every single business is going through some form of transformation to become more competitive in this new digital era. According to a recent survey by VMware, 91% of executives agree their major app initiative in 2021 is to migrate and modernize legacy apps. While this transformation has been going on for some time, the COVID-19 global pandemic has certainly super charged its acceleration and is now a critical imperative for many organizations to be able to create and deliver new digital experiences for their end users.

As part of my role within the VMware Cloud team, I have been taking a closer look at how some of our customers are thinking about their App Modernization strategy and to better understand their overall plan and thought process. With some of the recent customer conversations that I have had, many organizations are just starting their App Modernization journey and one of the challenges that I have observed is simply where and how to get started. There are certainly many different factors that can affect or even slow down these initiatives including organizational structure, tension between lines of businesses, development, operations and IT teams. However, before an organization can decide what application/services they are interested in modernizing, they need to first have a complete understanding of their current application estate.

This understanding is critical before an organization can determine the appropriate modernization strategy (Retain, Rehost, Replatform, Refactor or Retire) for a given application.


[Read more...]