Top vBlog 2015 voting is open now!


Finally ... Eric Siebert over at vSphere-Land.com has kicked off this year's Top vBlog voting - this time sponsored by Infinio!

The yearly vBlog voting is a great opportunity to show your support for your favorite virtualization blogs. Keep in mind that this is not a popularity contest - do not just vote for the blogs that everyone votes for every year, but pick those that had the best value for yourself!

You will find this blog in the overall favorites list and in the category "Best Independent Blogger".

Head over to the Top vBlog 2015 site to cast your vote - Thanks!!

New service: The VMware ESXi Patch Tracker


A while back I was looking for an easy way to stay up to date with VMware ESXi patches. VMware provides a lot of RSS feeds that keep you updated on new blog posts, new KB articles, security advisories etc., but ... I could not find anything that would just ping me whenever an ESXi patch was released.  The closest thing that I found was a link named "Get New Patch Alert" on the My VMware Patch Download Portal. That will refer you to the profile settings of your MyVMware account where you can manage various subscriptions including something that should keep you updated on new releases and patches of all sorts of VMware products. However, this just never worked for me, I never got a single e-mail out of this (anyone?), so I must assume that this service is not functional.

I finally decided to develop something on my own and provide that as a service to the community. So here is what I call the ...

VMware launches vSphere 6 - What's in ESXi 6.0 for free license and white box users?


The cat is out of the bag and it wears the number 6. VMware has announced its much anticipated new major version of their flagship product vSphere, and right now the virtualization blogosphere is humming with the news about vSphere 6.0.

Since this is an enterprise product most of the exciting new features are interesting for large installations using paid licenses and vCenter managed hosts: The long awaited ability ro use the Fault Tolerance (FT) feature with VMs that have more than one vCPU (SMP FT) is something that you can try out in your home lab if you have multiple hosts and use vCenter with an evaluation license, but the new support for virtual storage volumes (vVol) requires a modern SAN array with proper hardware support - nothing that you will find in the average home lab (at least not today). The ever increasing VM scalability now allows you to run VMs with 128 vCPUs and 4 TB RAM on physical hosts that can have up to 480 pCPUs and 12 TB RAM. Even in enterprise production environments it will be difficult to find setups that come even close to these numbers...

But what's in vSphere 6 that is useful for users of the free ESXi license and home labs?

pfSense 2.2 was released - How to install VMware Tools (sort of)


I'm a big fan of pfSense, an Open Source firewall and router appliance, that I use in my hosted lab. Recently version 2.2 of pfSense was released with a lot of bugfixes and new features. Please review the announcement blog post to find out what's new.

In my lab I upgraded one of the "not so important" pfSense VMs to version 2.2 and then tried to get VMware Tools installed and running again following my own guide that I wrote a while back for pfSense 2.0 and 2.1. But, well, things have changed a lot with pfSense 2.2, because it is now based on the latest FreeBSD version 10.1. Here is what I found out and what I ended up with.

What's new in the V-Front Online Depot


Since I launched the V-Front Online Depot about a year ago it has developed into a place where you do not only find the ESXi software packages that I created on my own, but also quite a few applications and drivers that others have contributed.

In 2014 Raphaƫl Schitz (he runs the excellent french hypervisor.fr blog) e.g. created and contributed the Intel Infiniband Subnet Manager (ib-opensm) package and the iperf v2 tool for ESXi, but this time I want to highlight two community developed driver packages that will help people running ESXi on white boxes with unsupported NICs.

2014: Year-end review


2014 - the fourth year of V-Front - is coming to an end. Like in the last years I have a list of highlights that I want to share - in case you missed any of them ...

How to make your unsupported NIC work with ESXi 5.x


When you try to install VMware ESXi on some whitebox hardware that is not officially supported by VMware then your attempt might come to an unpleasant end after the installer presented the error message shown above. ESXi has in-box support for a limited number of network interface cards (NICs), and sadly a lot of consumer grade devices are not on the list.

Is this the end of the world? No. If you are a regular reader of my blog then you probably already know that help (and in some cases even rescue) is available. However, I keep getting e-mails from people asking how to get their NIC xyz to work with ESXi ... So I finally took the time to write down all the steps that you need to take and the options you have - just to point them here instead of giving the same answers per e-mail again and again.

A very similar post of mine is How to make your unsupported SATA AHCI controller work with ESXi 5.5 - it is about a year old now and with 80k pageviews my most successful blog post ever. So far. Let's see how this one goes ...

How to avoid browser warnings when using the vCenter Web Client with a self-signed certificate


If you have a recent VMware vSphere installation with a vCenter server in production or in a lab then you will be aware of that the Web Client is the recommended choice for managing the environment and that the well known C# based vSphere Client is considered deprecated or legacy (since version 5.1 already).

However, when you connect to the Web Client of your freshly installed vCenter server for the first time using your favorite Internet browser you will be greeted by a more or less alarming warning. Chrome even warns you that VMware might steal your credit card information ;-) (well, they probably already have that) ... You should really be worried whenever you see this warning on a random Internet site, but you don't need to if it's your company internal vCenter server that you try to access.

So, why do you get this message, and how can you get rid of it?