VM /ETC

Archive for the ‘esxi’ Category

This is just a quick note that the previous issue with vSphere customers using NFS storage and CBT has been resolved with a recent patch. More on the previuous problem and the new patch in this KB article:

http://kb.vmware.com/kb/1031106

The KB was updated 7.26.11

I’ve had the luxury of staying away from the math of the new vSphere 5 licensing. Honestly, I haven’t read the new guide, and I’ve only skimmed through posts that explore the pros and cons of different upgrade costs and future growth impact scenarios from virtualization admins, consultants, and architects of  various size VMware virtual infrastructures. My opinion to date – VMware’s goal is to be a total Cloud solution, and this change in licensing reflects and fosters that plan. If you are able to correctly size you infrastructure, or if you can oversubscribe it so that you can offset the costs, then the hypervisor with the most features, the best performance, and the best partner ecosystem (in terms of available third party products leveraging vSphere APIs) is still a no-brainer. That would be vSphere 5.

Storm Clouds

I’ve also read the virtualization pundits’ predictions year after year. They usually go something like “this year is the year of VDI”, “sixty something percent of all servers can still be virtualized”, and “VMware’s market share will shrink to the advances of Microsoft and Citrix”. Is the record skipping? (does anyone know what a skipping record is anymore?). Personally, I’ve always felt a balanced market of hypervisor vendors would be the most likely prophecy for the datacenter, but VMware has always managed to innovate and stay ahead of the competition. Feature-wise, they continue to do so. But, the recent announcement of licensing changes may have changed things.

Whether right, wrong, misunderstood, reluctant to change, or just emotional, many VMware shops initially viewed the new licensing announcement like dark, thunder clouds approaching. Some reactions were as hot as a flash of lightning. Virtual warning sirens sounded across the community, but after a few days and some damage control from VMware, eventually calmer heads prevailed. But, like in the aftermath of any large storm, people began to build for the future. More so than ever before, public discussion of future plans seem to include a new possibility of alternative vendor virtual datacenters.

An Opening In The Clouds

My hunch is that current VMware shops will  Read the rest of this entry »

Like everyone else, I have been reviewing the Release Notes for the latest Update 1 release of vSphere 4.1, but I decided to point out specific fixes that will make full image VM backups better for everyone. Note that I work for Veeam Software, but the fixes I am referring to are all VMware resolved issues that surface from time to no matter what backup solution you use. There are numerous other fixes and impovements in the U1 release, but, since most of my world is backup these days, these particular items “popped out” at me.

For a great overview of the entire U1 release check out Rick Vanover’s post vSphere 4.1 update 1 released from his Rickatron Blog and via his Servers and Storage Column/Blog at TechRepublic.

The rest of this post contains cut and pastes from the Release Notes and some commentary about them from me. I want to stress again that these are issues that have now been fixed!

Finally, I’ll point out the one huge VM backup issue (that I can think of right now) that still does not appear to be resolved.

Read the rest of this entry »

Managing and troubleshooting ESXi 4 can be a little alien when an administrator is used to the Service Console of ESX Classic. Specifically, troubleshooting remote connectivity to the ESX management interface after adding a second NIC involves local esxcfg-vswitch commands on ESX, but with ESXi the esxcfg commands are only available via the RCLI. Problem is you can’t use the RCLI if you lost remote management connectivity! Luckily, the local ESXi GUI lets you reconfigure your mistake and re establish remote connections.

Hit F2 on the ESXi Console and enter the System Configuration Menu

  Choose to Configure Management Network > Network Adapters

Read the rest of this entry »

ESXi doesn’t have a Service Console like ESX. Therefore, you can’t SSH to the server without entering unsupported mode. That process may be a hassle if all you need to do is modify VM configuration files. Of ourse, you could use the Datastore Browser from the VI/vSphere Client, but to make file edits you would have to download a file to your desktop, edit it, and then upload the changed version back to ESXi again. On the other hand, with Veeam’s free FastSCP editing files on ESXi datastores is easy.

To be clear, you can’t edit configuration files of the ESXi host itself with FastSCP, but there really should not be a need to do so. That’s one of the benefits of ESXi not having a Service Console!

Download FastSCP here. You will have to register with Veeam first, and the registration form will not accept a personal email. I’m guessing there is some kind of lead qualification strategy and support registration involved with this requirement for download, but I learned a work address is unavoidable. I tried to use my gmail address but received a message similar to “you must use a company email address.” The registration process ends with a confirmation email to be acknowledged before you can download, so making up a fake email is futile. Hey, it’s a small price to pay for a free, quality admin tool.

After you install FastSCP you’ll discover you have access to a trial period of Veeam Backup and Replication. I suggest exploring

Read the rest of this entry »

To entice SMB interest and acceleration in building cloud infrastructure, today VMware announced new offerings centered on the ESXi 4 hypervisor. In 2 separate press releases, VMware revealed that a new agreement was signed with Intel to effectively distribute ESXi to more SMB customers, and that these customers can now easily automate the installation and configuration of ESXi with VMware Go. This post summarizes the official announcements and then offers some opinion on other factors that continue to influence the ultimate adoption of ESXi.

VMware Signs Agreement with Intel to Expand Reach of VMware vSphere 4 to SMB Customers

“The Intel global reseller community of more than 50,000 Premier and Associate members will benefit from the new agreement by being able to resell the industry-leading virtualization platform to their SMB customers. The agreement supports Intel’s strategy to proliferate virtualization technology on the recently announced Intel Xeon Processor 5500 series into SMB markets and it provides resellers with low-cost high availability solutions, including the three new VMware vSphere 4 product editions for SMBs that enable Always On IT. The Intel ESAA program also provides resellers with pre-certified Intel server platforms for VMware vSphere 4 with the ability to have their products listed on the VMware Hardware Compatibility List (HCL) at no additional charge. This reduces deployment costs and speeds time to market for resellers to address new opportunities.”

VMware Introduces VMware Go—A New Service that Will Make Virtualization Even Easier for First Time Users

“VMware Go is a free web-based service that will enable SMB customers to fly through the ESXi setup process with just a few mouse clicks.  The award-winning VMware ESXi is the industry’s most widely deployed hypervisor, with hundreds of thousands of users worldwide.  VMware ESXi, also available for free, allows companies to reduce overhead and simplify business operations by running multiple operating systems and applications on a single server, spending less money on hardware, power and cooling, and server administration. VMware ESXi together with VMware Go is an on-ramp for companies new to virtualization, especially small businesses who may not think they have the time or budget to get started.

VMware Go was developed in partnership with Shavlik Technologies, a member of VMware’s Technology Alliance Partner Program. VMware Go will be made available as a beta offering on August 31, 2009 to customers who go to http://www.vmware.com/go/vmware-go-beta. VMware Go is expected to become generally available as a free service in 2010″

As first pointed out to me by Eric Sloof on the NTPRO.NL blog, the VMware Go Beta is available today at Read the rest of this entry »

Admins of heavily consolidated VMware VI 3 Clusters should make plans as soon as possible to download Update 5 of VMware vCenter Server to take advantage of increased performance and scalability. The latest update to vCenter 2.5 was released on July 10 and boasts improvements to support fail over management of up to 80 VMs per ESX/ESXi host in a HA (High Availability) Cluster.

The following details were taken from the VMware VirtualCenter 2.5 Update 5 Release Notes:

What’s New

Support for High Consolidation in VMware HA Clusters – VirtualCenter 2.5 Update 5 includes significant performance and scalability improvements to VMware HA. Use VirtualCenter 2.5 Update 5 for environments with more than 35 virtual machines (VMs) per host in an HA cluster.

For information on the ESX Server host settings required for this scalability improvement, see ESX Server host settings required for environments with up to 80 virtual machines per host in an HA Cluster (KB 1012002).

Upgrading or Migrating to VirtualCenter 2.5 Update 5

This release supports upgrading from VirtualCenter 1.4.1, VirtualCenter 2.0.2 (including Update 1, Update 2, Update 3, Update 4, and Update 5), VirtualCenter 2.5, VirtualCenter 2.5 Update 1, VirtualCenter 2.5 Update 2, VirtualCenter 2.5 Update 3, or VirtualCenter 2.5 Update 4, to VirtualCenter 2.5 Update 5. Review the detailed upgrade and migration instructions and guidelines that are provided in the Upgrade Guide.

Following the above link to KB 1012002 explains that upgrading vCenter 2.5 to U5 is just the start. VI 3 admins also need to make some additional configurations on ESX/ESXi hosts to achieve the 80 VMs per host improvements.

“Starting with the VirtualCenter 2.5 Update 5 release, an ESX Server host in an HA cluster can support up to 80 virtual machines. For all virtual machines to power on on other hosts in the cluster, if hosts within the failover capacity limit fail, you need to ensure that the following parameters in the ESX Server hosts are set with the following values:

Read the rest of this entry »