Ran into common problem that other administrators have probably come across the other day when I was migrating some old ESX 3.5 hosts to a new vCenter where I get the following error: The license
While troubleshoot the issues I had with a VMware ESXi cluster: https://blog.terenceluk.com/vmware-esxi-40-update-2-slow-boot-up/ https://blog.terenceluk.com/vmware-esxi-41-slow-boot-up-seemingly/ https://blog.terenceluk.com/slow-boot-up-times-on-esxi-41-do-you/ https://blog.terenceluk.com/problem-when-upgrading-from-esx-35-to/ I’ve noticed that the VMware KB article wasn’t clear on what variables existed in which ESXi version so I took
For those who have come across one of my earlier posts a few months back: Experiencing slow boot up times during an update from ESX 3.5 to ESX/ESXi 4.0 or 4.1? Check your RDMs https://blog.terenceluk.com/slow-boot-up-times-on-esxi-41-do-you/
I figure that I’ll most likely forget this some time in the future which is why I wanted to write a blog post about how you can obtain the boot up logs of an ESXi
During the first few Cisco UCS B Series deployments I was a part of, there was always this problem that I would run into that I knew what I needed to do to get around
While this error message may be obvious to the seasoned VMware ESX/ESXi administrator, I’ve found that it’s a common question some newer administrators who are just getting into VMware’s virtualization technology tend to ask which
As with my previous post about VMware VMFS block size considerations, the topic VMDK partition alignment has probably been beaten to death in the VMware virtualization. A quick search on the internet will yield plenty
I’m sure the topic of VMFS block size considerations has been discussed plenty of times and a quick search on the internet will yield plenty of blogs and articles about it but I’ve noticed that
One of the reasons why I like what I do an my position at the company is that whenever there’s any problems with a Cisco UCS B or C series servers, I’m one of the
Throughout the years that I’ve been involved with virtualizing environments, I’ve realized that there are actually many pre and post tasks that should be completed when virtualizing a physical host. While I always had scattered
