VMware Cloud Community
ikotb
Contributor
Contributor

Esx 3.5 to 3.5 update2 benefits?

I currently have couple of VMs on ESX 3.5 is there is any benefits of the 3.5 update 2? Thx

0 Kudos
4 Replies
ascari
Expert
Expert

bye Alberto

0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Features

Windows Server 2008 support – Windows Server 2008 (Standard, Enterprise, and Datacenter editions) is supported as a guest operating system. With VMware memory overcommit technology and the reliability of ESX Server, you can maximize virtual machine density with this new guest operating system to achieve the highest ROI. Guest operating system customizations and Microsoft Cluster Server (MSCS) are not supported with Windows Server 2008.

Enhanced VMotion Compatibility – Simplifies VMotion compatibility issues across CPU generations. Enhanced VMotion compatibility (EVC) automatically configure server CPUs with Intel FlexMigration or AMD-V Extended Migration technologies to be compatible with older servers. After EVC is enabled for a cluster in the VirtualCenter inventory, all hosts in that cluster are configured to ensure CPU compatibility for VMotion. VirtualCenter does not permit the addition of hosts that cannot be automatically configured to be compatible with those already in the EVC cluster.

Storage VMotion – Storage VMotion from an FC/iSCSI datastore to another FC/iSCSI datastore. This support is also extended on ESX Server/ESX Server 3i 3.5 Update 1.

VSS quiescing support – When creating quiesced snapshot of Windows Server 2003 guests, both filesystem and application quiescing are supported. With Windows Server 2008 guests, only filesystem quiescing is supported. For more information, see the Virtual Machine Backup Guide and the VMware Consolidated Backup 1.5 Release Notes.

Hot Virtual Extend Support – The ability to extend a virtual disk while virtual machines are running is provided. Hot extend is supported for vmfs flat virtual disks that do no have snapshots opened in persistent mode.

192 vCPUs per Host – VMware now supports increasing the maximum number of vCPUs per host to 192 given that the maximum number of Virtual Machines per host is no more than 170 and that no more than three virtual floppy devices or virtual CDROM devices are configured on the host at any given time. This support is also extended on ESX Server 3.5 Update 1.

Hardware Enablement and Management:

8Gb Fiber Channel HBAs – Support is available for 8Gb fiber channel HBAs. See the I/O Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.

SAS arrays – more configurations are supported. See the Storage/SAN Compatibility Guide for ESX Server 3.5 and ESX Server 3i for details.

10 GbE iSCSI initiator – iSCSI over a 10GbE interface is supported. This support is extended on ESX Server 3.5 Update 1, ESX Server version 3.5 Update 1 Embedded and ESX Server version 3.5 Update 1 Installable as well.

10 GbE NFS support – NFS over a 10GbE interface is supported.

IBM System x3950 M2 – x3950 M2 in a 4-chassis configuration is supported, complete with hardware management capabilities through multi-node Intelligent Platform Management Interface (IPMI) driver and provider. Systems with up to 32 cores are fully supported. Systems with more than 32 cores are supported experimentally.

IPMI OEM extension support – Execution of IPMI OEM extension commands is supported.

System health monitoring through CIM providers - More Common Information Model (CIM) providers are added for enhanced hardware monitoring, including storage management providers provided by QLogic and Emulex. LSI MegaRAID providers are also included and are supported experimentally.

CIM SMASH/Server Management API – The VMware CIM SMASH/Server Management API provides an interface for developers building CIM-compliant applications to monitor and manage the health of systems. CIM SMASH is now a fully supported interface on ESX Server 3.5 and VMware ESX Server 3i.

Display of system health information – More system health information is displayed in VI Client for both ESX Server 3.5 and VMware ESX Server 3i.

Remote CLI – Remote Command Line Interface (CLI), which was previously supported only on ESX Server 3i, is now supported on both Update 2 for ESX Server 3i version 3.5 and Update 2 for ESX Server 3 version 3.5. For more information on Remote CLI, see the Remote Command-Line Interface Installation and Reference Guide for more information.

Management Agents Support

HP Management Agents – HP Insight Management Agents provide server management capabilities for ESX Server hosts installed on supported server platforms. A new version, 8.1, is now supported.

Guest Operating System Support

Solaris10 U5 - Both the 32-bit and 64-bit versions are supported.

SUSE Linux Enterprise Server 10 SP2 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and is hence performance-optimized for VMware environments.

Ubuntu 8.04 - Both the 32-bit and 64-bit versions are supported. The 32-bit version supports the VMware Virtual Machine Interface (VMI) and is hence performance-optimized for VMware environments.

Service Console , driver and library updates

Service Console Operating System Update - The ESX Server Console operating system has been updated to RHEL 3.0 U9. See the document Updated RPMs and Security Fixes for detailed information.

Driver updates - The tg3 driver has been updated to version 3.81c. The megaraid_sas driver has been updated to version 00.00.03.19.

Library update - StoreLib has been updated to version 2.51.

VMware High Availability (HA)

VirtualCenter 2.5 update 2 adds full support for monitoring individual virtual machine failures based on VMware tools heartbeats. This release also extends support for clusters containing mixed combinations of ESX and ESX Server 3i hosts, and minimizes previous configuration dependencies on DNS.

VirtualCenter Alarms

VirtualCenter 2.5 Update 2 extends support for alarms on the overall health of the server by considering the health of each of the individual system components such as memory and power supplies. Alarms can now be configured to trigger when host health degrades.

Guided Consolidation Enhancements

Guided Consolidation now provides administrators with the ability to filter the list of discovered systems by computer name, IP address, domain name or analyzing status. Administrators can also choose to explicitly add physical hosts for analysis, without waiting for systems to be auto-discovered by the Consolidation wizard. Systems can be manually added for analysis by specifying either a hostname or IP address. Multiple hostnames or IP addresses, separated by comma or semi-colon delimiters, may also be specified for analysis. Systems can also be manually added for analysis by specifying an IP address range or by importing a file containing a list of hostnames or IP addresses that need to be analyzed for consolidation. Guided Consolidation also allows administrators to override the provided recommendations and manually invoke the conversion wizard.

Live Cloning of Virtual Machines

VirtualCenter 2.5 Update 2 provides the ability of creating a clone of a powered-on virtual machine without any downtime to the running virtual machine. Therefore, administrators are no longer required to power off a virtual machine in order to create a clone of it.

Windows Single Sign-on Support

You can now automatically authenticate to VirtualCenter using your current Windows domain login credentials on the local workstation, as long as the credentials are valid on the VirtualCenter server. This capability also supports logging in to Windows using Certificates and Smartcards. It can be used with the VI Client or the VI Remote CLI to ensure that scripts written using the VI Toolkits can take advantage of the Windows credentials of your current session to automatically connect to VirtualCenter.

rgds,

J.

0 Kudos
FredPeterson
Expert
Expert

Live cloning of VM's seems to be reason enough for me.

Of course, you don't do that kind of thing very often...but how many times have you wanted to clone a production system and had to schedule it off hours to take it down and wait for it to clone?

0 Kudos
ikotb
Contributor
Contributor

Okay...I burned the ISO image to CD to upgrade my current version "3.5" in the vm client under configuration I'm trying to backup the VMs I got to USB drive or network it goes then it times out?

0 Kudos