VMware vSphere 5.0 Goes All-In with ESXi

 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
By Cameron Sturdevant  |  Posted 2011-08-26 Email Print this article Print
 
 
 
 
 
 
 

50Ia

Adding a syslog server host is done the same way in ESXi and in ESX.

VMware vSphere 5.0 does away with the ESX hypervisor. Starting now, the name of the game is ESXi. VMware has neatly outlined the differences here.

Bottom line: if your organization was using third-party tools that plugged in via the ESX Service Console, you should check to see if those tools have been approved for use in the VMkernel in ESXi.

I have to admit that until vSphere 5.0 was released, I had only passing experience with ESXi. When it was released as a free, standalone hypervisor in 2008, in my mind that meant it was inferior to the not free ESX. It turns out that was a mistaken impression. During my recent tests with vSphere 5.0, I was easily able to use my ESX-honed skills in the ESXi environment.

I'll reiterate here that I'm generally in favor of VMware taking greater control of the hypervisor environment in the form of approving third party tools for use in the VMkernel environment provided by the ESXi hypervisor. As long as technical--not competitive or marketing--hurdles must be cleared to gain acceptance, I think the change to the ESXi-only environment is a good one.

 
 
 
 
del.icio.us | digg.com
 
 
 
 
 
 

Submit a Comment

Loading Comments...

 
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel