vSphere 4.1 released

Little_Crow

Little_Crow

Little_Crow

Associate
Joined
3 Oct 2007
Posts
795
vSphere 4.1 released, discuss.

Some of the points from the release that maybe aren't immediately apparent:

> 4.1 is the last release that will use ESX, from 4.2 onwards there will only be ESXi.

> Update manager will not include OS updates from 4.2 onwards

> VCenter, Update manager and SRM can now only be hosted on a 64bit OS.
> The Update Managers DB has some odd discrepencies on which Microsoft DB editions it can be hosted on.

So it looks like I'm going to be having fun building new 64bit VC servers to migrate to, reinstalling our ESX hosts with ESXi, and battling all new issues with vRanger, can't wait :rolleyes:
 
Only ESXi... sucks. :(. I think I may reload my ESX hosts before my support is over. Not overly nice.

Fortunately last week I put a new VC on a 64bit server.
 
Last edited:
I can't say I've used ESXi for about 3 years, and it certainly wasn't pretty.

My biggest worry is the lack of a service console. I know you can install the powercli tools, but I don't see them as any kind of substitute for a proper console.

I understand why VMWare are doing it, many of the patches are for the service console, not ESX itself, I just don't like it.
 
JonRohan said:
I would have preferred it if I'd have known about VMwares decision to drop ESX a couple of months ago. I'm sure partners and such would have known.
Click to expand...

Yep, just finished a project to DR our site using SRM, at least I only have 12 ESX hosts to rebuild, could have been worse.

Our partner has been pretty open with us, I won't go into the gory details of our HP EVA CA saga, but I'm sure had they known, they would have steered us towards ESXi and installing VC on a 64bit host.

groen said:
Why did they drop ESX ? o.O
Click to expand...
They haven't yet, but 4.2 will only have ESXi.
Not certain why, possibly that half the patches released are for the service console not ESX itself.
They probably now feel that the remote service console VM (VMA) they provide is mature enough to do everything the console can.
(Not used the latest versions, so can't comment myself)

I've always found developers for other apps very slow to make them work with ESXi, hopefully now with only ESXi they'll pull their collective finger out.
 
No one seems to know the proper reason for them dropping the service console.

Not even people I speak to at VMware!

Sometimes if you are in a pickle, the service console is the ONLY way out.
 
Just mooching through VMware's blog site whilst eating my lunch and found this from June 2009 (assuming US date format):

# The functionality and performance of VMware ESX and ESXi are the same; the difference between the two hypervisors resides in their packaging architecture and operational management. VMware ESXi is the latest hypervisor architecture from VMware. It has an ultra thin footprint with no reliance on a general-purpose OS, setting a new bar for security and reliability (learn more).
# In the future, ESXi’s superior architecture will be the exclusive focus of VMware's development efforts.
# New and existing customers are highly encouraged to deploy ESXi. Many Fortune 100 companies have already standardized on the ESXi platform.
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom