There are several ways to add additional drivers to ESXi. This can sometimes be necessary when implementing a new type of servers. So if you have a device that isn't supported by the default installation of ESXi a driver needs to be added after the installation.

This post will describe how to add an additional drivers to ESXi with update manager. It can also be done via the vCLI which is described by the guys at VMGuru.nl here.

The additional drivers that are available to ESXi can be downloaded from the vSphere download page under the tab Drivers & Tools. All downloads will be delivered in ISO format.

The ISO includes a zip file that contains the (offline-bundle) additional driver. The additional driver will be available in zip-file which can be imported under Configuration -> Patch Download Settings in VMware Update Manager.  There is a note (see picture in yellow) with a link to "Import Patches".

Click to enlarge picture

This will start a proces of importing the additional update into Update Manager. After this the update will be available in your repository. After which you can create a baseline and patch your ESXi hosts.

For more information on how to patch your ESXi host with baselines and remediation see the following video :

Click here to view the embedded video.

Virtualization of servers results in the fact that server are no longer depeded on the hardware on which it runs. This is one of the key selling points of virtualization, but it also results in the fact that you can't connect external hardware devices to your virtual machine directly. 

Especially for USB devices this can be a problem. There are still application vendors out there that have implemented some sort of USB dongle for licensing their software. To make it possible to connect your USB dongle to a virtual machines an implementation is needed of remote USB to connect the USB devices to your virtual machine.

The following picture gives a graphical representation of how this works.  

Click to enlarge

The concept of remote USB is based on the client-server model. All USB devices will be centralized to one USB remote server. Through a software USB device driver (=client) in the virtual machine a connection is made with this USB remote server.

Through management on the USB remote server, USB devices can be allocated to a particular virtual machine. This allows virtual machines to make use of USB devices without connecting that USB device to the hardware on which it runs. All USB data is now send over the network from the virtual machine to the remote USB server and vice versa.

There are several vendors on the market with a remote USB solution. All have the same result : giving access to USB devices over the network. Only difference is that some have software based solution while others have a hardware based solution.

When using a software based solution a server is needed that acts as the remote USB host. The server must have enough USB slots available to connect all the USB devices. The hardware based solution is a network device which act as the end point in the remote USB solution. All USB devices will be connected to this network device.

Examples :

• AnywhereUSB (hardware)
• Keyspan USB device server (hardware)
• USB over Network (software)
• USB over Ethernet (software)

Note : Remote USB isn't needed for VDI implementations. Most VDI vendors have USB redirection incorporated into their solution. In case you are using thin clients, USB redirection can also be implemented on the thin client policy server.

Click here to view the embedded video.

VMware released the long awaited vSphere 4.1. This update of the current vSphere productline has some great new feature included in this release. The notes on "What's new" can be found here.

Some new features include :

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).

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.

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).

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.

Also a nice note is included under Install and Deployment : "Future major releases of VMware vSphere will include only the VMware ESXi architecture." This means that we won't see ESX anymore in the future releases. The result will be that you eventually will need to upgrade to ESXi. Not a bad thing as I already explained in an earlier post here. For more information on how to migrate to ESXi, look at this whitepaper written by VMware.

You can download the new release here. Next thing : update to new release and play with new features

UPDATE : For more information on the vSphere 4.1 go to this link page of Eric Siebert. Excellent resource for all the vSphere 4.1 information out there.

If you want VMware SRM to work with your storage array it needs to communicate to the storage array. For this reason each storage vendor has created a Storage Replication Adapter (SRA) which plugs into SRM. You can download these SRAs  for each vendor here. (Note : Only download from the VMware website. Why?)

HDS also provides a SRA to connect to its storage arrays. But only installing the SRA won't get the storage array to be recognized by SRM. The picture below gives a graphical representation of the component needed to let SRM communicate with the HDS storage array.

Click on picture to enlarge

The HDS SRA 2.0 needs an instance of the HDS Command Control Interface (CCI) to communicate to the HDS storage array. The HDS CCI is storage box management software which is provided by HDS. This can be installed on the SRM server next to SRM and the SRA.

To create an instance of the HDS CCI a Hitachi Online Remote Copy Manager (HORCM) service is defined manually on the Windows host. The HDS CCI manages the storage array(s) through the defined control LUNs on each storage array.  The HORCM service is configured in the HORCM file. This file defines which LUNs are replicated between the protected and the recovery site. These LUNs are the LUNs that SRM can see and which it can managed for Disaster Recovery and testing purposes.

During configuration the HDS SRA is pointed to the HORCM instance which manages the storage array(s). All this provides the HDS SRA with the  information which it passes through to the SRM server.

This creates the connection between the SRM server and the storage array necessary for SRM to work. For more information look at the VMware vCenter Site Recovery Manager Deployment created by HDS. Follow its step-by-step instructions carefully while it is essential getting HDS to work with SRM.

This post is about Site Recovery Manager (SRM) in combination with the storage system of Hitachi Data Systems (HDS). I've been working with over the last couple of months. This is a braindump of my knowledge about the product.

HDS has complete portfolio of storage solutions available. Every type of VMware environment can find a HDS solution suited for their needs. I've been working with the AMS2500. This is a SAS / SATA based storage array. It is a suitable solution for midrange size companies, but can also be used by enterprise size companies as a 2nd tier SAN. Next to this storage array HDS also provides enterprise class storage array with its Universal Storage Platform.

For both types of storage HDS provides best practices for VMware which can be found here for the AMS2000 series and here for the Universal Storage Platform VM.

Like all major storage vendors HDS also is a VMware partner when it comes to SRM. They committed themselves to the support of their storage systems with SRM through their HDS SRA 2.0.

For more information how to set up VMware SRM with HDS storage arrays take a look at the deployment guide here that HDS created. It's a document that explains in detail how to setup your HDS storage array and HDS Storage Replicatoin Adapter (SRA) for the creation of your SRM environment.

For more information on HDS with VMware look at this resource page.

Last week VMware launches its new product: VMware Go. This is a product that is specifically targeted at the SMB market. A clever move by VMware to expand its market share of virtualization in the SMB segment. VMware already is the market leader in virtualization when it comes to enterprise companies. But in the SMB segment has competitors like Microsoft's Hyper-V, Citrix XenServer or RedHats KVM.

Not only cost is a factor that stops SMB companies from entering the path of virtualization. Also the lack of resources and knowledge about virtualization is something most SMB companies don't have.  With Go VMware  tries to simplify the proces of virtualization. It provides a management interface to VMware ESXi from the Go cloud.

Eric Sloof over at NTPRO.NL points to a YouTube video where Dave McCrory, founder and CTO of Hyper9, explains how VMware Go works.

The picture above shows the same explanation of VMware Go as Dave McCrory gives in his video. What shows is that management takes place, through a web interface,  from the workstation where the administrator is located. Everything will be managed from the VMware Go cloud. The ESXi hosts are connected to the Go cloud by installing a proxy admin desktop. This desktop will service the Go cloud a management interface for the ESXi host.

This is a rather new concept of managing servers. Normally a client-server management model is applied to this kind of infrastructure services. VMware vCenter, the current management tool for vSphere infrastructures, is an example of a this type of management model.

The question is : Is this the first of step into moving vSphere management into the cloud?

This may seem like a far fetched idea, but is it? We are now living in the world of cloud computing. Lets look at the same picture as above, but introduce the vCloud concept into this equation.

Here you can see the same concept as the picture above. The proxy desktop has been replaced by an VMware Go Proxy appliance which is for managing the ESXi host in you (local) private vSphere cloud. There is a connection between the Private vSphere cloud and the vCloud(s) provided the various VMware hosting partners. All this can be managed from a central point : the VMware Go cloud.

If the name will still be the same isn't important, call it vCenter Cloud Edition (CE), it doesn't matter. What does matter is the fact that you now have central point of management to control your hybrid cloud. Not only can you manage your private cloud, but from the same interface you can manage you various vCloud partners (or even non-VMware) cloud services. This makes the VMware vCenter Cloud Edition a cloud broker to manage all your IaaS cloud services. Maybe even with integration to manage PaaS or SaaS solution. One cloud to rule them all

Will this become reality? Only time will tell.

My personal opion: I like the idea of cloud brokers. I don't think that one (cloud) provider / solution can serve all the cloud services needed by a company. So in my opinion cloud brokers will become the next battleground in cloud land. That's why I like the idea of a central management cloud broker solution. That's why I like the idea of a vSphere vCenter Cloud Edition.

What do you think?

VMware today announced the vCloud Express. The new type of service allows customers to get on-demand, pay-as-you-go Infrastructure as a Service. Several leading Virtual Service Providers (VSP) like Terremark, Bluelock, Hosting.com and Melbourne IT have adopted this technology and have currently several products in beta. Look here for more information.

Introducing VMware vCloud™ Express

VMware is today introducing VMware vCloud™ Express, a new class of service that will deliver reliable, on-demand, pay-as-you go compute as a service.  Built on the industry’s leading and most complete virtualization platform, VMware vSphere™, VMware vCloud™ Express will enable customers to start with VMware vCloud™ Express and grow into full enterprise-class cloud environments with highly available and service level guarantees when they are ready to move into production.   Unlike other on-demand cloud solutions, VMware vCloud™ Express will give developers quick access to a pay-as-you-go infrastructure that is compatible with in-house VMware virtualized IT environments—making the interoperability and portability of applications from external development to internal deployment easy. With VMware vCloud™ Express, customers will have the flexibility to leverage IT resources when they need it and pay for only what they use.

VMware vCloud™ Express will be available through many leading service providers including Terremark, BlueLock, Hosting.com, Logica, and Melbourne IT.  These service providers are launching beta releases of their services today.  To try VMware vCloud™ Express, find your preferred provider by going to: www.vmware.com/vcloudexpress.

“By leveraging VMware’s best-in-breed virtualization technologies and our vast experience providing solutions to enterprise and Federal government customers, our vCloud ™Express offering will provide customers a uniquely differentiated, cost-effective platform that meets their IT infrastructure needs,” said Manuel D. Medina, chairman and chief executive officer, Terremark. “Terremark’s vCloud™ Express services will provide our customers pay-as-you-go, on-demand access to enterprise-class infrastructure that is flexible enough to offer unmatched compatibility with their own internal IT platforms.”

What this really means is that you can now connect your virtual infrastructure, running vSphere, with the VSP(s) of your choice. Expansion of your infrastructure is now available just by going to a website, registering with your credit card and selecting your type of service. No more, no less. You connect your vSphere setup with the service have expanded your virtual capacity. Easy does it!

Well not entirely true. It’s still in beta and it won’t be perfect at first. But in general I like the product. It makes Cloud Computing, especially IaaS, more understandable and will help get Cloud Computing out of the “hype cycle” and into the realistic world of IT we live in. It’s not a product supported by one vendor, but also has a broad eco-system of service providers attached to it and it propagates interoperability which, in my opinion, is one of the key factors of making Cloud Computing a success!

Matthijs Haverink and Sven Huisman over at VirtualFuture.info created a new version of their Application Virtualization Comparison Chart. It's a good comparison and overall informative document about Application Virtualization. Ideal if you need to make a choice for a product to virtualize your workloads.

Cisco and VMware are currently working on a new technology called Long Distance vMotion. This makes it possible to move application workloads between multiple datacenters without any downtime. The vMotion technology is already available within VMware vSphere. It is used to migrate one VM from one host to another or wit Storage vMotion move the VMs data from one storage location to another. This with the machine being fully operable and available to the end-user.

The changing model of data center management and provisioning allows VMware VMotion to be used for several purposes without violating the application SLAs.

● Data center maintenance without downtime: Applications on a server or data center infrastructure requiring maintenance can be migrated offsite without downtime.
● Disaster avoidance: Data centers in the path of natural calamities (such as hurricanes) can proactively migrate the mission-critical application environments to another data center.
● Data center migration or consolidation: Migrate applications from one data center to another without business downtime as part of a data center migration or consolidation effort.
● Data center expansion: Migrate virtual machines to a secondary data center as part of data center expansion to address power, cooling, and space constraints in the primary data center.
● Workload balancing across multiple sites: Migrate virtual machines between data centers to provide compute power from data centers closer to the clients (“follow the sun”) or to load-balance across multiple sites. Enterprises with multiple sites can also conserve power and reduce cooling costs by dynamically consolidating virtual machines into fewer data centers (automated by VMware Dynamic Power Management [DPM]), another feature enabling the green data center of the future.

In these cases the secondary cloud can be provided by a service provider through a “virtual private cloud” connected to your “internal cloud”. Bringing down the TCO of your server infrastructure, using capacity in the secondary datacenter only when you need it and making use of a pay-per-use model for the consumed capacity. So this technology is a real cloud enabler!

For more information about this technology can be found here. Written by Omar Sultan.

Read the paper on this subject created by Cisco and VMware here.