With the Big news that broke late last night and early this morning that vSphere 4.1 was released and available for down. Many of my fellow bloggers have written articles about the great new features that are included with this release. I am going to just offer a summary of some of the high points of the release that I find as the biggest impact. I was not part of the Beta testing for this release so I am just not getting to play with this version. The group of Beta testers have been enjoying and playing with the latest features for sometime now and thats why there has been a sudden explosion of articles that people have been holding until the official realease of the product.
Scripted Install for ESXi. Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network by using PXE booting. You cannot use scripted installation to install ESXi to a USB device.
vSphere Client Removal from ESX/ESXi Builds. For ESX and ESXi, the vSphere Client is available for download from the VMware Web site. It is no longer packaged with builds of ESX and ESXi. After installing ESX and ESXi, users are directed to the download page on the VMware Web site to get the compatible vSphere Client for that release. The vSphere Client is still packaged with builds of vCenter Server.
Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot.
Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth.
Storage Performance Statistics. vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New VMDK and datastore statistics are included. All statistics are available through the vSphere SDK.
Storage I/O Control. This feature provides quality-of-service capabilities for storage I/O in the form of I/O shares and limits that are enforced across all virtual machines accessing a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion.
Network I/O Control. Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic (vNetwork Distributed Switch only).
Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted.
Improved Support for Handling Recalled Patches in vCenter Update Manager. Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed.
ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles.
Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk.
You can see the full feature list on the VMware page, the list is pretty long.
With more talk about Storage IO Control (SIOC) each month, VMware is starting to leak more details about the feature. The best write up on the feature was by Scott Drummonds last month that you can read here. With SIOC you will be able to have almost a quality of service for VM’s in regards to storage IO control. With a very simple setup showcased in the video below you can level the playing field so that something happening in one virtual machine does not monopolize all of the storage bandwidth and starve other machines.
A few things to keep in mind for now. That SIOC is enabled per datastore, does not have a reservation limit at this time, only enforces limits when a threshold is reached and can enforce limits for IOPS when specified at the VM level. Thanks to Duncan for these details.
In the images below you can get an idea of how Storage IO Control is working along with Shares applied to Virtual Machines to stop any VM from hogging all of the IO.
In working with a client recently I noticed that they are cloning virtual machines and it’s causing issues with their tool set. This really came to light when working with their XenApp servers. The Citrix team was building servers loaded with apps to create a template that could be cloned to create the other servers in a application pool. The issue with this is that the team was using existing servers already in production that already had the tools installed on them. The problem came to light with issues from the tools used to protect and monitor the virtual machines. This would not be an issue with standard OS templates already created that would have the tools added after the cloning process.
When cloning the virtual machine there are still a lot of registry entries left over with the old server name for tools like Opsware, McAfee and an asset mgmt application. These old registry entries would cause the new VM to knock the old VM out of the tools console and cause issues with reporting and management of the source server. For example Opsware would start talking to the newly cloned server thinking it was the source server and this would leave the source machine not in the patching scheduled.
To clean this up it was necessary to uninstall these tools from the new virtual machine then go back through the registry and clean up any entries that referenced the old server name. Then reboot the server and reinstall the tools. This will clean up the issues and allow everything to work without conflicting with the source server.
So for future requests of this type they have agreed to either use a base OS build and load applications on by hand or create their Citrix template with applications and clone prior to installing any monitoring applications. This will eliminate the issues that they had been experiencing.
Hot off the presses! The latest update for VMware vSphere is now available for download. Both Update 2 for ESX 4.0, ESXi 4.0 and vCenter 4.0 are all available now. Run don’t walk to your nearest PC with a fast connection and start downloading. Ok don’t run you might crash into something. Have fun playing with the latest update in your labs. You can download the latest version here.
Here are some of the release notes for ESX 4.0 U2, see full list here.
Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
Enhancement of the esxtop/resxtop utility— vSphere 4.0 Update 2 includes an enhancement of the performance monitoring utilities, esxtop and resxtop. The esxtop/resxtop utilities now provide visibility into the performance of NFS datastores in that they display the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s(guest latency).
Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04.
Here are some of the release notes for ESX 4.0 U2, see full list here.
Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
Enhancement of the resxtop utility— vSphere 4.0 U2 includes an enhancement of the performance monitoring utility, resxtop. The resxtop utility now provides visibility into the performance of NFS datastores in that it displays the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s (guest latency).
Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04.
Here are some of the release notes for vCenter 4.0 U2, see full list here.
Guest Operating System Customization Improvements: vCenter Server now supports customization of the following guest operating systems:
Windows XP Professional SP2 (x64) serviced by Windows Server 2003 SP2
While I was upgrading my vCenter server to Server 2008 I came across the following issue. I was trying to install VMware License Server on a Window Server 2008 32bit server and the install would fail saying it cannot start system services. After checking to make sure that I had not made some dumb mistake with my account I hit the intertubes and found that others had the same issue.
I was able to get pass this issue by downloading the latest copy of Virtual Center server 2.5 update 6 and then extracting the License server install file from the VPX folder. Seems that the copy from the install .iso file is newer than the file available for direct downloading. Maybe VMware can fix this soon. I did not try it but according to some other posts the version in VC 2.5 U5 might also work. Once I installed this version it worked the first time.
Error 1920.Service VMware License Server failed to start. Verify that you have sufficient privileges to start system services.
Recently while setting up a new cluster on vSphere I had an issue with adding one of the hosts to the cluster. It would fail the HA configuration piece each time I would try. The host would join the cluster but HA would have a Red alarm for its failure. Nothing seemed to be wrong with the host, hardware or configuration. I would get the error listed below on each attempt.
cmd addnode failed for primary node: Internal AAM Error agent could not start
I found the following VMware KB article to help troubleshoot these types of errors. My issue ended up being an issue with the cluster that was created. I created a new cluster and moved my ESX Hosts and Virtual Machines over to it and the issue was gone. Before trying this route I had examined several of the options listed in the KB article.
If you are interested in Guest Blogging for us, all you have to do is reach out to us. We welcome people willing to create content that will benefit the Virtualization community. It does not matter if you are a seasoned blogger or a first timer.
