Oct 272011

Last year I joined a Movember team and while I though I would look like a ‘bit of a spoon’ with a moustache I actually quite got into the whole thing.

So this year I though why not use the power of the virtualisation community try and raise some money for charity just by letting your top lip grow some fuzz Smile


I have created a team called vTache and I would like as many of you to take part as possible. So please join my team and as of the 1st of November you will be raising money for some really good causes.

Post to Twitter

Aug 012011

The hottest topic after the launch of vSphere 5.0 has unfortunately not been about the awesome technology features announced like Auto Deploy, Storage DRS, Fault Domain Manager etc etc.

I was around in Cannes VMworld 09 when vSphere 4.0 was released and all the talk seemed to be about licensing then also, so this controversy does not come as a huge surprise to me.

I am a little disappointed however that some people I know to be extremely clever are failing to see the bigger picture. I’m not going to go into all that now as I think it has been blogged to death. Some good articles are by Rynard Spies who speak about the downside of new licencing compared to vSphere 4.0 and Aaron Delps, speaking about the bigger picture of TCO and how the VMwares new licencing model fits.

Personally the new licencing model does not seem all that bad to me. Those who know me will know that I love a good analogy, so here I go….

I believe comparing the old vSphere 4.x licencing model to 5.0 is seriously floored. Lets use a car as an example:

A Ford Focus Hatchback (05-11 model) cost between £11,695 – £20,845 brand new. a Ford Focus Hatchback (‘11 onwards) costs (£16,000 – £24,000). Now we all know why we are paying more, it’s a better looking car, it has better safety features, it has more toys, it is more efficient on MPG but most critically the development of the car. Even though it is at a high-level it is more or less the same car, no-one complains that the price has gone up considerably.

When VMware went from VI3.x to vSphere 4.0 they didn’t actually put the price up to reflect all the new toys and development costs.

So why have they increased the costs now? Lets look at the industry, even though there are the ‘Scale Out’ gang who blindly believe that it is the best model, the hardware vendors are producing the most powerful servers that we have seen and are managing to pack them into more and more reduced CAB space. Added that CPUs will soon be going in to the high teens and 20’s means that VMware old licencing model would be totally financially unfeasible. If everyone went for 4.x Ent Plus then with all the factors I mentioned above VMware would be selling less and less licences and make less money!!

So, do I think there could be improvements with the licencing model VMware have produced for vSphere 5.0? Yes, I would like to see the vRam limit up to 96GB for Ent Plus (rumours say this might happen). But do I think switching to vRAM was the correct decision? Yes, it makes total sense to me when looking at VMwares long term goal to remain the market leader.

Lets stop moaning about the licencing model and start talking about the product its self.

Post to Twitter

Jul 122011

Bye Bye ESX and the Service Console!! The long time talked about removal of the service console from the vSphere product set means vSphere 5.0 is now a converged platform offering (ESXi).

So what platform enhancements are in the vSphere 5.0 release?

Image Profiles – An image profile allows for the create of bespoke ESXi images. Common issues in previous version of ESX meant that existing ESXi images could have missing drivers and no plugins like nk1v. It describes all the components in an ESXi instillation image, but not configuration. The Image Builder is a set of command line utilities (powercli version). Image Profiles are kept in a depot, a repository (library of images and VIBs)

What is Auto-Deploy?

ESXi is downloaded and ran from memory. VMware vSphere Auto Deploy virtual appliance loads the hypervisor software onto host as it is booting. It uses the image profiles obtaining from the depot and boot it via PXE. Combining the features of host profiles, Image Builder, and PXE, VMware vSphere Auto Deploy simplifies the task of managing ESXi installation and upgrade for hundreds of machines. New hosts are automatically provisioned based on rules defined by the user. Rebuilding a server to a clean slate is as simple as a reboot and the physical memory is cleared. To move between ESXi versions, you update a rule using the Auto Deploy PowerCLI and perform a test compliance and repair operation.

Auto-Deploy allows for rapid provisioning and re-provisioning of new hosts and enables simplified updates.image

The big bonus for Auto-Deploy is no local storage for host hypervisors. The same goes for Boot from SAN.


Recipe for Auto-Deploy:

Custom ESXi image + network boot machine + auto deploy virtual appliance + configuration + host profiles + runtime state information + vCenter server + recording of events + syslog netdump servers


Used to be IPtables – not anymore. Service aware but not state of host. 3rd party components.

Can add rules thorough GUI or xml format.

New Virtual Machine Capabilities

VM scaling:

Hardware version 8. 32 virtual cpu per VM, 1tb ram per VM.

    Support for up to 512 virtual machines. vSphere 5.0 supports up to 512 virtual machines totalling a maximum of 2048 virtual CPUs per host.

    Support for larger systems. vSphere 5.0 supports systems with up to 160 logical CPUs and up to 2TB RAM.

    other new features – UI for multi-core virtual CPUs, extended VMware tools compatibility, support for mac os server.

    • New Virtual machine capabilities. ESXi 5.0 introduces a new generation of virtual hardware with virtual machine hardware version 8, which includes the following new features:
      • 32-way virtual SMP. ESXi 5.0 supports virtual machines with up to 32 virtual CPUs, which lets you run larger CPU-intensive workloads on the VMware ESXi platform.
      • 1TB virtual machine RAM. You can assign up to 1TB of RAM to ESXi 5.0 virtual machines.
      • Nonhardware accelerated 3D graphics for Windows Aero support. ESXi 5.0 supports 3D graphics to run Windows Aero and Basic 3D applications in virtual machines.
      • USB 3.0 device support. ESXi 5.0 features support for USB 3.0 devices in virtual machines with Linux guest operating systems. USB 3.0 devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it. USB 3.0 devices connected to the ESXi host are not supported at this time.
      • UEFI virtual BIOS. Virtual machines running on ESXi 5.0 can boot from and use the Unified Extended Firmware Interface (UEFI).

    Other new features – UI for multi-core virtual CPUs, extended VMware tools compatibility, support for mac OS server.


    Storage DRS (SDRS):

    • Initial virtual disk placement (Pod – pool of data stores)
    • Out of space avoidance,
    • I/O load balancing,
    • Virtual disk affinity anti-affinity
    • New man agent object,
    • Storage equivalent of SRS clusters,
    • Consists of similar data stores,
    • storage load balancing domain.
    • Storage Policy based management (SPBM),
    • 2TB+ LUN support. vSphere 5.0 provides support for 2TB+ VMFS data stores.

    VMFS-5 – Scalability and performance improvements, increase limits of the file-system (limits a FS size that increases when the FS extends/grows), Reduce SCSI reservation with VAAI primitives. Plumbing of UNMAPs (Space reclamation on TP LUNs). Set the stage for future proofing, more efficient snapshot facility within VMFS, support for 2 TB plus files.

    vStorage API for storage awareness (VASA) – to allow array vendors to provide more info about the storage array, (drives, RAID level etc).

    VAAI – now doing NAS and Thin Provisioning (pass info down to array to clear up the space). Ability to warn when the array runs out of space.

    Storage vMotion Enhancement – speeded up, now snapshot VMs can be storage vMotioned.

    Storage vMotion snapshot support – Allows Storage vMotion of a virtual machine in snapshot mode with associated snapshots. You can better manage storage capacity and performance by leveraging flexibility of migrating a virtual machine along with its snapshots to a different data store.


    LLDP – Link Layer Discovery Protocol) – bit like CDP

    Netflow – inter-vm traffic, vm-physical infrastructure traffic – (vDS sends records to 3rd party collectors such as NetQoS and NetScout)

    DVMirror – can monitor traffic inter-vm or intra-vm.

    NIOC (network IO control)– network prioritisation (I/O shares) at VM level – QOS extended to network infrastructure – workload isolation between tenants. – done through vDS resource pools and shares within them.



    vMotion – support for up to four 10GBPS or sixteen 1gbps nics –single vMotion can now scale over multiple nics (load balance). It can now slowdown during page send (SDPS)(slows down the VM slightly to ensure the copy can complete) feature throttles busy VMs to reduce timeouts and improve success. vMotion can now ensure less that 1 second switchover time in almost all cases. It can support higher latency networks (up to 10MS), improved error reporting, resource pool integration by vMotion now puts VMs in the proper resource pool.

    DRS – integration with vShield, support for vShield agents (zones, edge, app, endpoint), a DRS/DPM cluster hosting vShield agent VMs, resource pool management consistent for clusters and non clusters being managed by VC. Resource pool settings stored in VC for non-clustered hosts (same as clustered hosts), enables support for stateless ESXi hosts running in standalone/non-clustered mode, prevents direct host access to resource pool settings managed by VC, improved behaviour when host disconnected from VC, if host loses access to VC users can connect directly to the host and override VC to take control, no longer requires restarting the VPXA.

    Cloud Level Scalability:

    • 1000’s of VDC’s
    • 50,000+ VMs
    • 2000 hosts
    • 150,000 Objects
    • 200+ concurrent administrators

    Can now run on Linux and also comes with a downloadable appliance.

    FDM (fault domain manager) – Replacement for VMware HA. no more AAM

    • More reliable
      • Deploys and reconfigures within seconds, regardless of cluster size.
      • Uses multiple channels for agent-to-agent communication: both network and storage
      • Removes dependencies on commonly misconfigured services (e.g., DNS)
    • New and Improved features
      • Management network partition support (new)
      • Single HA log file per host and syslog integration (new)
      • Host isolation response (improved)
      • Admission control (improved)
      • Agent error reporting (improved)

    Flex Based Client:

    • Empowering the Administrator
      • Centralize all VMware Administrative User Interfaces
      • Seamless integrate with all VMware solutions
      • Create a common user experience
      • Common “Look and Feel”
      • Single Sign On (SSO)
      • Scale to the Cloud
      • Support multiple platforms
      • Provide for ease of extensibility

    Its worth noting this is better than the web clients prior to vSphere 5.0 but still has a little way to go to match the vSphere Client.

    Update Manger – can now do delayed and staggered upgrades – can upgrade a Virtual Appliances.

    And for VDI:

    Accelerator. An accelerator has been delivered for specific use with View (VDI) workloads. With this option configured in ESXi, a read cache is constructed in memory that is optimised for recognising, handling, and de-duplicating VDI client images. The cache is managed from within the View Composer and delivers a significant reduction, as high as 90% by early estimates, in IOPS from each ESXi host to the storage platform holding client images. This reduction in IOPS enables large scaling of the number of clients in case multiple I/O storms, typical in large VDI deployments, occur.



    (I’ll keep updating as I find them):

    Post to Twitter

    Jun 242011

    First off credit for this post has to go to Brian Lyttle for his 4.1 USB blog post.

    Not to much has changed from the 4.1 methods of booting the install for vSphere 4.1.

    The method I used to follow was Ivo Beerans manual syslinux method. This works ok if you manage to follow every instruction perfectly. But in a attempt to make my life easier I found this method is much more straight forward and is easily repeatable.

    By using UNbootin to create the USB file, life become much simpler. It still creates a syslinux.cfg file but it does all the hard work for you.

    I’m a Windows desktop guy so UNbootin is great for my Windows 7 desktop but its also available for Linux and MAC OS.

    Here’s the auto configured syslinux file contents:

    default menu.c32
    prompt 0
    menu title UNetbootin
    timeout 100

    label unetbootindefault
    menu label Default
    kernel /ubnkern
    append initrd=/ubninit -c boot.cfg

    label ubnentry0
    menu label ESXi-5.0.0-381646-standard ^Installer
    kernel /MBOOT.C32
    append initrd=/ubninit -c boot.cfg

    label ubnentry1
    menu label ^Boot from local disk
    kernel /ubnkern
    append initrd=/ubninit

    Create the bootable USB Flash installation drive.

    Download UNbootin from sourceforge.

    Once you have stated UNbooin.exe select Ubuntu from the distribution dropdown menu (I left the version at the default).


    Select the ISO file you want to be able to boot to.

    If an overwrite messages appear just accept them.

    Dont click ‘reboot now’

    THATS IT… you now have a bootable USB Flash Drive with vSphere Hypervisor 5.0 instiller package.

    Ivo’s Kickstart files can be used to automate the instillation of the hypervisor should you wish to do so.


    To complete the instillation and configuration follow……………

    Post to Twitter

    Jan 102011

    I stumbled across an annoying issue with the VI client and backward compatibility. I kept receiving the error “The server closed the connection. The underlying connection was closed: the connection was closed unexpectedly.”

    It was also raised in this VMware community article:


    I was using the 4.1 client to connect to the ESXi 4.0 server and assumed that this would be acceptable as it should be backwardly compatible. Unfortunately this is not the case. While it is not a huge issue for me to have the 2 versions installed I can imagine a larger estate with both ESXi 4.0 and ESXi 4.1 to be a little more irritating.

    This is not a show stopper at all but backward compatibility is something every company should get correct.

    In addition if you have already had the 4.0 VI client installed this is not an issue as it simply loads previous version without prompting.

    Post to Twitter

    Oct 162010

    So another VMworld Europe is over and the majority of attendees will be left with a sense of satisfaction and a slightly painful hangover. Also some with iPads, net-books and countless T-shirts, USB keys, pens and even sponsored energy drinks.

    This years show was widely criticized when it was announced for being so close to the main event in San Fran and it was anticipated that the number of attendees and vendors would have been effected. This was true to a certain extent but other factors compensated.

    The good:

    Tech Preview

    The technology presented by VMware at this show was not the staggering list of features and new products we had in Cannes however it was more than enough to get our teeth into. The focus was mainly around vCD and its peripherals (vSheild, Chargeback, Networking etc etc). We also saw plenty on View 4.5 and its evolution. I also particularly liked the look of project ‘Horizon’ which will be VMware SaaS solution arriving some time next year.

    The vendors had plenty of tech to keep us all interested between Breakout Sessions and it was interesting to see how the landscape is changing from a vendor perspective. Some very interesting solutions to the old VDI I/O bottle neck issue seemed to grab my attention and the guys at Atlantis Computing were on the full marketing warpath. I also liked what HP/3par are trying to do and the direction that venture takes will be hugely interesting and could make a huge mark in the VDI space. Perhaps is the tide is theoretical tide is swinging back towards SAN than local disk?? I think I’m edging into dangerous territory and getting away from the point….

    I’m a big fan of UCS and that and he vBlock were really interesting to get a good look at in the flesh. While im not as much of an ITIL guru as Steve Chambers (anyone following Steve will know this) I am still very much of that way of thinking so Service Manager really captured my attention and vCloud request manager also looked to fit the cloud model very well.

    Attendee figures

    Paul Maritz announced that this has topped 6000, a record for the Europe event.

    Vendor attendance

    Compared to the Cannes show last year (seems allot longer) I did not notice a great deal of vendors (that I cared about anyway) being missing from the event.


    Copenhagen is an inspiring an beautiful city with excellent transport and plenty of accommodation. Its night life left there to be plenty to do outside the event.

    2010-10-14 09:41:58 +0200

    Solutions Exchange

    Overall the Bella Centre was more that adequate for the event. As it was scaled down somewhat this year there was more than enough room to host such an event.


    This year seemed to have more vendor parties than ever. I was pressed frequently by attractive young girls trying to get me to go their party. It was plainly obvious that those girls wouldn’t actual be there though.  I hit the VMUG party on the Monday evening and the Veeam party Wednesday and despite the tiredness had a great time at both.

    2010-10-14 09:41:31 +0200


    This year year in San Fran we saw the Labs being delivered by a cloud service provider for the very first time. This theme was continued in Copenhagen and I was very pleased to see that the Lab team reached there goals on VMs created and destroyed and people attending.

    I found the labs them selves to work very well and they were responsive and I had not issue. One person next to me had all sorts of issues however and had to keep getting an engineer over to help, I initially though bad things about the lab he was doing but when he asked what ‘putty’ was and what ‘ssh’ was to the response to his first question I realised it was more likely user error.

    2010-10-15 23:32:50 +0100

    Breakout Sessions

    I really liked the format of a few of the breakouts where it was basically an intimate 15 or 20:1 ratio to the tech lead. This was far for more informative and I felt I got an honest and frank answer to most of the questions I asked. I also like the ‘Who want to be a millionaire style surveys at the beginning.

    Social Media and Bloggers Lounge

    I was blown away by this as I did not expect there to be level of attention around this. I always knew that this area was popular and the amount of people trying to get into the social scene (me included) has exploded in the last 18 months (I think I may have said that in my interview a few times haha). You only have to look at the VMUGs and there popularity along with the vbeers events to see how much people enjoy spending time in the company of like minded people.

    I was very pleased to have been involved with this and meet some really cool (geek cool that is) people that I will defiantly keep in contact with.

    2010-10-15 23:34:21 +0100

    The bad:

    Tech Preview

    While there was plenty to consider with the announcements (specifically Horizon, View 4.5 and vCD) there was no getting away from the fact these technologies had been announced and being used for a fair number of weeks. This gave enough time for everyone to find the failures and missing features that most VMworld’s would not experience. I know I may be a minority on this looking at the % of attendees but the advanced guys were all feeling a little deflated. As a result the Breakout Session often felt like pure marketing and not technical. Perhaps I’m being a little over critical here but I can not honestly say I went away thinking I have learned anything new that I didn’t already know from reading the announcements or playing with the products prier to the show.

    Breakout Sessions

    As a result of the lack of technology announcements the Breakout Session often felt like pure marketing and not technical. Perhaps I’m being a over critical here but I can not honestly say I went away thinking I have learned anything new that I didn’t already know from reading the announcements, documentation or playing with the products prier to the show.


    While on the whole i liked the labs and there structure I thought that the queues were allot worse than Cannes. This is in part to the ‘cloud’ way it was done, Cannes had separate banks of desks for each lab. This meant that if you arrived at a lab that had a huge queue you could do your second or 3rd choice. I found the queuing in Copenhagen frustrating and as a result I didn’t get as many labs done as Id have liked. Many be if id been more dedicated then id have arrived at 8 every day.


    While I dont think the venue was bad I though the food was a far cry to that in Cannes. Im not a fussy eater however the lack of variety and the peculiar food combinations meant that I was left with bagels most days. When I did try the hot food (lamb curry I think) it was warm at best.


    The main party lacked something this year while basically a similar setup to the Cannes (games machines etc) it lacked a certain intimacy you got at last years venue and felt a little like we were all cattle in a barn being made to force drink and much larger as possible. Not to say i didn’t at least try and drink as much as i could ;-). Id say the place was only half full by 10:30 as most vendors had dragged people off to bars. Also the pre main event entertainment was a little boring and the 60’s theme was very odd. On the bright side I was with great company and any party is only as good as what you make it.

    Solution Exchange

    Much smaller exchange from Cannes. While I don’t think there was a radically reduced vendor attendance the size of the booths were much reduced. As was the free gifts. The iPad giveaways from the bigger vendors draw crowds but the usual gift were reduced to pens and hats.

    The not so great:

    Simons pink, flowery shirt.

    Celebrity spotting (Simon Long)

    and my interview.

    David Owen (@vMackem) on VMwareTV

    Suggestions For 2011

    All in all I enjoyed this years VMworld immensely and most of the bad points I highlighted are not issues I would think would put me off. If I had to say which was the best out of Cannes and Copenhagen I would probably have to give it to Copenhagen. The whole social networking scene has made it impossible (if you wanted to that is) not so have access to even the most famous faces in the industry.

    I’m fairly confident that Copenhagen has been booked in for next year so I’m not going to suggest changing that however I feel the following would make the experience better:

    • At least having one big announcement at the Europe event. This wont leave us feeling like the poorer cousins over the pond.
    • Placing twitter names and blog addresses clearly on the badges. While not everyone have these it would be great for those that do to identify people from there virtual persona.
    • Have the labs accessible through wireless and allow people to use their laptops throughout the venue. Thee wireless was pretty good (apart form the odd drop outs) so I think this would be achievable with some reconfiguration on the lab side.
    • Split the party into multiple rooms like Cannes.

    Post to Twitter

    Aug 192010

    NOTE: this is currently speculation and not yet confirmed by VMWARE.

    It looks like vmware are about to pull the plug on the VCDX 3 program as of the 30th of August 2010 (thats the romour anyway). All Exams and Design Submissions must be passed and submitted by this date.

    This leaves me, along with quite a few other people, with very little notice to get the exams and designs finalised and submitted.

    My personal position is that I have passed the Enterprise exam but not the Design exam (failed it once). As a result I have spend hundreds of pounds on something that looks like its going to be worthless.

    I have 2 main issues:

    1. Why have there not been any anouncments from vmware certification? I know people have recently taken the enterprise exam and were not informed of the pending withdrawal of VCDX3 thus anyone that thought they could take their time for the rest of the process have been caught out.
    2. Why is there no meaningful qualification at each stage of the VCDX3 process like there is with the VCDX4. I don’t really understand why there has not been an equivalent of the VCAP for stages in the VCDX3. I would not have as much of an issue with this if my VCDX3 Enterprise exam actually counted for something.

    The VCDX3 process was a little painful and drawn out, but to make matters worse vmware now seem to have left a significant number of people in limbo as there is so much confusion due to no official announcement. Vmware have always been good at connumication and it puzzles me why we have ended up in this situaltion.

    As the upgrade path allows anyone that has passed the design exam in VCDX3 to take the design exam in VCDX4 and skip the Administration exam.

    However when I went to book my exam on the Pearson Vue website the entire exam has been removed from site. Hence I can not book the exam.

    This leaves me (and others) with the very real possibility of wasting allot of time and money on a qualification that means next to nothing in the industry (re the Enterprise Exam only).

    Please could you do the poll bellow so I can get an idea how many of you are effect by this:

    Sorry, there are no polls available at the moment.

    Post to Twitter

    Jul 092010

    I had a client recently that had brought a small company in to P2V a small set of infrastructure. I was brought in to “fix” the issues that they left.

    They made a small mistake that made me have to do some reading.

    They were using Cisco EtherChannel to aggregate 4 GBE ports. This is fine and is an accepted way of increasing your bandwidth however they were not seeing the performance benefits that it should have brought. After some investigation I noticed that only one of the NIC on the ESX server was actually being used with any great demand.

    Reading the below article led me to the load balancing option in the vswitch.

    They had it set to “Route based on the originating virtual port ID”. The load balancing needs to be “Route Based on IP HASH”.

    Also do not use beacon probing with IP HASH load balancing and do not configure standby up-links with IP HASH load balancing.

    Once this change was made it load balanced as you would have expected (once the ESX network services had been restarted).


    Post to Twitter

    Jun 172010

    Someone asked me recently what are the differences between Distributed Virtual Switch and the Cisco Nexus 1000v?

    As I have only used the 1000v in lab environments my highlevel knowledge was a little rusty.

    This is what I found as being available in the 1000v and not the VDS:

    • With the Nexus 1000v you get a IOS interface that will allow network managers to manage the virtual network infrastructure with the same  features as they already use to manage the physical network.
    • Port profile – As that VM moves from server to server with VMotion, the port profile follows it. All security and network configurations, stay with the VM as it travels from server to server. Enabling security policies you would traditionally find in the physical servers to be applied to VMs
    • QOS (Quality Of Service)
    • Switched Port Analyser
    • Authentication.
    • And many more…

    Much more on the features of the 1000v can be found http://www.cisco.com/en/US/products/ps9902/index.html

    The VDS is a big step forward from the single vSwitch model with features like:

    • Central Management
    • Network Aware Vmotion
    • Private VLANS

    More info on VDS: http://www.vmware.com/products/vnetwork-distributed-switch/

    Post to Twitter

    Jun 112010

    vSphere was updated on June 10th 2010 to Update 2.



    New Features:

    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
    • SLES 11 (x32 and x64)
    • SLES 10 SP3 (x32 and x64)
    • RHEL 5.5 Server Platform (x32 and x64)
    • RHEL 5.4 Server Platform (x32 and x64)
    • RHEL 4.8 Server Platform (x32 and 64)
    • Debian 5.0 (x32 and x64)
    • Debian 5.0 R1 (x32 and x64)
    • Debian 5.0 R2 (x32 and x64)



    New features and enhancements:

    • 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. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.

    Post to Twitter

    Twitter links powered by Tweet This v1.8.3, a WordPress plugin for Twitter.