Today I attended session VSP1682 ‘VMware vSphere clustering Q&A‘ hosted by Frank Denneman, Duncan Epping and Chris Colotti.

After a short introduction the Q&A started and below you will find my top 10 questions.

Q1. Are the old, vSphere 4, constraints in vSphere 5 still current?

Until vSphere 5 the best practice is a maximum of 8 hosts in a cluster, because of linked clones in VMware View and the primary/secondary ESX(i) hosts setup in an HA cluster. In vSphere 5, VMware changed this to a master/slave setup. When the master ESXi host goes offline a new master is elected within 15 sec. So, the cluster boundary limits VMware vSphere had in the past are gone. This is a huge advantage of vSphere 5.0.

(more…)

After the release on July 12th, you can now download VMware vSphere 5 and enjoy the 150 new features.

You can find the downloads here.

For more information visit:

• VMware ESXi and VMware ESX Info Center
• VMware vSphere 5 release notes.

If you want to upgrade your existing VMware vSphere installation, check out my previous article on how to upgrade to vSphere 5.

Want to know more regarding VMware’s new licensing model? Check out the latest changes here.
Hint: Read carefully and calculate the impact on your environment before forming your opinion!

Now, don’t let me keep you, GO and try out vSphere 5!

On July 12th, VMware announced the release of vSphere 5.

With the release comes the challenge to upgrade your existing installation.

However, there are a few caveats:

• vSphere 5 is the first version which comes in a ESXi version ONLY! ESXi 5 is available in an embedded or installable version. If you’re running ESX 3.x or 4.x you should do a clean installation. You can find more information here.;
• VMware changed their licensing method. Familiarize yourself with this and check if you need to upgrade/extend your licenses. You can find more information here.

Because I run a VMware vSphere 4.1 environment, this is a upgrade from vSphere 4.1 to 5.

The upgrade is a straight forward five step process.

(more…)

For putting together a business case costs and revenues are an important part of it. If you want to calculate the direct resource costs associate with hosting a server in  your data center, you want to know the direct power consumption by the server in electrical costs and the costs associated with cooling the environment where the server is situated. To do so you will need a few parameters from the device(s) used. You will need the Watts, BTU/h and the electricity costs per kWh.

Where British thermal unit (BTU)  is used as a unit for air-cooling power of an air conditioning system and refers to the amount of thermal energy removed from an area. A BTU is approximately a third of a watt-hour. 1000 BTU/h is approximately 293W.  Kilowatt hour (kWh) is most commonly known as a billing unit for energy delivered to consumers by electric utilities.

Let’s take for example a HP DL-380 Generation 6 with two Quad core CPUs, 24 GB memory, eight  network ports, two  72GB 15K SAS hard disks with two 460 Watt power supplies. This server uses about 307 Watt and generates 1047 BTU.

(more…)

Earlier this week I already told you that I’ve build a new ESXi whitebox but I had some problems installing it.

OK, first of all, what was the situation? I wanted to install VMware ESXi 4.1 Update 1 to a USB stick which is VMware certified.I plugged the USB stick into one of the USB ports on the back of my whitebox server and downloaded the ISO-image form the VMware website.

A quick installation and I’m ready to build my new lab environment. WRONG!

The installation fails with the following error:
‘Cannot install VMware ESXi 4.1 “Unable to find the system image to install’

(more…)

Last week I decided to buy a new lab server and I doubted between a HP or Dell mini server or an ESXi whitebox. Because most mini servers only have 8GB memory, I decided to collect specific parts to build my own VMware ESXi whitebox.

To find parts which are compatible with VMware ESXi 4.1, I used the following resources:

• Ultimate VMware ESX Whitebox;
• VM-help.com.

I chose a AMD Phenom II X6 processor, socket AM3 six core processor because it’s a lot cheaper than the Intel Core i-processors. As the basis I needed a AM3 socket motherboard and my selection criteria where simple, 16GB memory and onboard video.

As an ASUS fan I had to choose between the ASUS M4A88T and M4A88TD. Both can house 16GB of memory and have onboard video but the TD version has SATA 6Gbps. Because storage will most likely be the bottleneck, I decided to go for the M4A88TD-M but on the above sites there was no entry for this motherboard.

But Google is my friend so I searched for ‘M4A88TD’ in combination with ‘ESXi’. I found a few sites which mention an almost identical combination of motherboard, processor and ESXi 4.1. Eventually I took a gamble and ordered the ASUS M4A88TD-M/USB3.

The last two items where the simple ones, two sets of 8GB dual channel memory and a 6Gbps SATA disk.

(more…)

14 years ago, on May 11, 1997, IBM’s Deep Blue II chess-computer won a six-game match by two wins to one with three draws against world champion Garry Kasparov.

In June 1997, Deep Blue was the 259th most powerful supercomputer achieving 11.38 GFLOPS running 30 parallel RS/6000 SP Thin P2SC-based system nodes, with each node containing a 120 MHz P2SC microprocessor enhanced with 480 special purpose VLSI chess chips.

But how does that relate to computing power in 2011 and especially to virtual computing power running VMware vSphere 4.1?

(more…)

Yesterday Anne Jan linked me to an article on the VMware website which contained information on a free online training course. The title is Transition to ESXi Essentials. The course is dedicated to ESXi and depending on your learning style it takes about 3 hours to complete. It’s broken up in several chapters so you don’t have to do all at once.

Since VMware is moving towards ESXi, abandoning ESX with its Service Console, it’s a great time to release a course all about ESXi and how to manage it.

(more…)

I just fiddled somewhat with the ‘fling’ from the VMware site: PXE Manager. Well, if you ask me, it’s not just a ‘fling’, but it is really, really useful. It’s easy to install and easy to use.

Here’s the summary from the ‘fling’:

PXE Manager for vCenter enables ESXi host state (firmware) management and provisioning. Specifically, it allows:

• Automated provisioning of new ESXi hosts stateless and statefull (no ESX)
• ESXi host state (firmware) backup, restore, and archiving with retention
• ESXi builds repository management (stateless and statefull)

(more…)

Tonight VMware released Update 1 for vSphere 4.1 and vCenter server 4.1.

Update 1 for ESX/ESXi contains a few new/improved features:

• Enablement of Trusted Execution Technology (TXT) — ESXi 4.1 Update 1 can be configured to boot with Intel Trusted Execution Technology (TXT). This boot option can protect ESXi in some cases where system binaries are corrupted or have been tampered with. TXT is currently available on Intel Xeon processor 5600 series servers.
• Improvement in scalability — ESX 4.1 Update 1 supports up to 160 logical processors.
• Support for additional guest operating systems — Added support for RHEL 6, RHEL 5.6, SLES 11 SP1 for VMware, Ubuntu 10.10, and Solaris 10 Update 9 guest operating systems.
• Inclusion of additional drivers — ESX 4.1 Update 1 includes the 3ware SCSI 2.26.08.036vm40 and Neterion vxge 2.0.28.21239-p3.0.1.2 drivers.

Furthermore ESX/ESXi 4.1 Update 1 contains a lot of patches and fixes a list of issues.

(more…)

In May 2010 HP introduced the new HP Storageworks IO Accelerator modules for HP Blade and ProLiant servers.

So what is this IO module. It is a mezzanine card that is available for HP C-class Blades or a PCI-e I/O card for HP ProLiant servers.

It is available in three different capacities: 80GB, 160GB and 320GB. But the MOST interesting is that it can deliver 100,000 IOPS.

Because it was not certified by VMware this IO Accelerator could not be used in ESX implementations. Until now! And today HP released drivers for VMware vSphere 4.0 Update 1.

(more…)

Last week I visited a new project at which the client wants to virtualize their desktops.

During the kickoff the client mentioned that they use a variety of applications, clients and operating systems and want to deliver all these desktop flavors to their users.

Nothing new so far.

But this variety of clients and operating systems also includes Apples, MacBook (Pro)’s, etc using Mac OS X. Running a View client on a Macbook Pro with Mac OS X is no problem but provisioning Mac OS X as a virtual desktop is a whole different story.

(more…)

Last week we got a question concerning the licensing options around vSphere and how to choose the correct edition and options from all the flavors and options offered by VMware. So while answering the questions concerning the licensing I thought back to a nice overview picture we had available a few years back from VMware. So that’s why I compiled two overview pictures where there is one for the SMB market and one for the Enterprise market. In the overview the current situation and options are summarized per edition.

(more…)

Some of you might already have been there. I know I have:

You have a large organization with more than 10 remote or branch offices. You have virtualized your entire back-end but those nasty site servers still remain a physical nuisance. Some regional offices have a complete data center with more than 20 servers just to make sure everyone can work locally. You want to virtualize it but you can’t convince your management to purchase 10 or more sets of Advanced of Enterprise (plus) licenses for those sites as that is far to expensive.

Now, what do you do? What I’ve done in the past is use a ‘free’ ESXi license and manage it as a standalone server. It is a possibility, but you lack a lot of enterprise features you really want to have. And what if the site is too big for just one host. And what about fail-over? One is None, we always say. So what’s the solution? (more…)

Last month I regularly received requests from colleagues concerning VMFS block sizes. Although it’s a simple setting, it still raises a lot of questions and the introduction of vSphere 4.1 has somewhat changed the game.

The block size on a VMFS datastore defines two things:

• The maximum file size;
• The amount of space a file occupies.

First of all, the block size determines the maximum file size on the datastore. If you select a block size of 1MB on your datastore the maximum file size is limited to 256GB. So you cannot create a virtual disk beyond 256GB.

Also, the block size determines the amount of disk space a file will take up on the datastore. This is theoretical because VMFS3 uses sub-block allocation (see below).

It is not possible to change the block size after you set it without deleting the datastore and re-creating it. Therefore you should create a good design and determine the block size before creating the datastores.

(more…)

Some weeks ago I posted an article about some bad network performance when moving VMs to a new ESX host.

Last week I got an e-mail which announced some updates and among it was the one promised to us by the engineer that helped us with our problem.

Description of the patch is exactly what we where experiencing with our VMs:

“When you access remotely using Remote Desktop Protocol (RDP) from a client machine to a Microsoft Windows virtual machine with TCP segmentation offload (TSO) enabled and EnablePMTUDiscovery parameter set to 0, the network connection is slow and sometimes, the connection might not work. This issue is reported on Broadcom bnx2x NICs, such as BCM57710, BCM57711, BCM57711E, etc.” http://kb.vmware.com/kb/1026129

After installing the patch on one of the ESX hosts we tested with a test VM on a patched and an unpatched ESX host and there was a clear difference in performance. The logon on the VM was much faster on the ESX host with the patch.

For us the patch fixed the problem and we are now deploying it on all the ESX hosts.

We got a happy customer again.

With the release of vSphere 4.1 it will be the last version of ESX to be released in an ESX and an ESXi version. After this version only the ESXi flavor will be released. We at VMGuru.nl predicted that this would happen a few years back, so we advised our customers to go for the ESXi version, too make it a lot easier to migrate to a newer version in the future.

VMware recommends that customers deploy vSphere 4.1 on the ESXi hypervisor architecture as a best practice.

In the past some features from the ESX architecture weren’t supported on the ESXi platform. As of vSphere 4.0, all the functionality of VMware vSphere is supported on both architectures, including support for Jumbo Frames, Cisco Discovery Protocol (CDP), NetQueue, and NetFlow.

VMware ESXi is the latest hypervisor architecture from VMware. It has an ultra-thin architecture with no reliance on a general purpose OS, yet still offers all the same functionality and performance of VMware ESX. For a comparision between ESX and ESXi 4.1 see the following article.

(more…)

A few weeks ago I got an assignment to review a colleague’s infrastructure design based on VMware.
The design was fine (because they used my design document as template ) but one thing triggered me.

There was a special port group on one of the virtual switches names ‘MSCLUSTER’. No problem so far but I heard the client recently migrated to iSCSI storage.

The combination Microsoft Clustering Services (MSCS) combined with iSCSI triggered  my alarm bells. As I recalled Microsoft Clustering on iSCSI is not a problem but Microsoft Clustering on VMware with iSCSI is not supported (by VMware).

So, I rejected the design based on this support issue.

This message was not well received, as it turned out they had just migrated their clustered Exchange servers and had been running this way for a while now. Proposing to the client to migrate again was no option. So they tried to  question my findings. They had been running this setup without any problems and Exchange CCR clustering wasn’t real Microsoft Clustering because no disks were clustered, only the Exchange services.

(more…)

Last year we published an Enterprise Hypervisor comparison and we got very positive comments and feedback on it.

During the last few weeks I received many update requests so I decided to update the old hypervisor comparison but this time I changed the setup a bit.

Changes:

• No beta or pre-release versions are used. In the last document we also compared Hyper-V R2 beta which wasn’t officially released.
  This time all software is available and no features are subject to change due to beta-test, etc.;
• The versions used are the platinum/ultimate/fully-featured versions of the hypervisors. Product features can be limited by lower license versions;
• No free versions have been used in this comparison.

(more…)

At a client site we came upon a problem with Windows 2003 VM’s. They would get low network performance when we moved them to a newly formed ESX cluster consisting of HP 460c G6 blades. In some cases logging on to the server with a remote session took about 20 minutes.

As I mentioned this only occurred when we moved a VM to the new cluster, but also VM’s that where newly installed would get the same problem when running on the new cluster. As we are using Altiris to install and configure new VM’s a colleague decided to install a new VM by going through the steps manually which normally would be done by Altiris and found out that after the activation of a security template the performance dropped significantly.

(more…)