La version 4.1 de VMware vSphere est disponible au téléchargement
vSphere 4.1 comme SRM 4.1 sont disponible en téléchargement sur le site de VMware,
La liste complète des nouvelles fonctionnalités est disponible ici
La Release Note est disponible ici
A noter que la version 4.1 de SRM est aussi disponible
Indiscrétion ou volonté de VMware de publier non officiellement des informations sur la prochaine version de vSphere ?
Le site virtualization.info a publié récemment une liste de fonctionnalités disponibles sous la prochaine release de vSphere : vSphere 4.1.
- Storage I/O can be shaped by I/O shares and limits through the new Storage I/O Control quality of service (QoS) feature
- Network I/O can be partitioned through a new QoS engine that distinguish between virtual machines, vMotion, Fault Tolerance (FT) and IP storage traffic.
- Memory compression will allow to compress RAM pages instead of swapping on disk, improving virtual machines performance.
- Distribute Resource Scheduling (DRS) now can follow affinity rules defining a subset of hosts where a virtual machine can be placed
- Virtual sockets can now have multiple virtual CPUs. Each virtual CPU will appear as a single core in the guest operating system.
- A team physical network interface cards in a vNetwork Distributed Switch can now dynamically load balance traffic.
- Health check status and operational dashboard are available for HA configurations.
- vSphere Client is no more part of the ESX and ESXi installation packages. At the end of the installation process administrators are redirected online to download the client.
- ESXi installation can be scripted. The script can start from a CD or over a PXE boot source, and can install the hypervisor on local or remote disks.
- ESX can boot from iSCSI targets (support for iBFT)
- NFS performance stats are included in esxtop and vCenter Server, as well as through the vSphere SDK.
- Virtual machines serial ports redirection over the network
- Support for up to 4 vMotion concurrent live migrations in 1GbE networks and up to 8 concurrent live migrations in 10GbE networks
- Support for USB pass-through (virtual machines can use ESX/ESXi local USB devices)
- Support for administrator password change in Host Profiles
- Support for FT in DRS clusters with with Enhanced vMotion Compatibility (EVC)
- Support for iSCSI TCP/IP Offload Engine (TOE) network interface cards (both 10GB an 1GB)
- Support for 8GB Fibre Chanell HBAs
- Support for IPsec on IPv6 network configurations
- Support for multiple Data Recovery virtual appliances
- Support for Microsoft Volume Shadow Service (VSS) in Windows Server 2008 and 2008 R2 guest operating systems for vStorage APIs for Data Protection (VADP)
- Update Manager (VUM) can now patch additional 3rd party modules for ESX (like EMC PowerPath)
- Virtual to Virtual (V2) migration for offline Hyper-V virtual machines in vCenter Converter
- ESX and ESXi direct support for Microsoft Active Directory through Likewise technology integration
- Support for Intel Xeon 7500 / 5600 / 3600 CPU series (this includes EVC support)
- Support for AMD Opteron 4000 / 6000 CPU series (this includes EVC support)
Etant beta testeur officiel donc sous NDA je ne pouvais communiquer ces informations avant qu’un tiers de les publient.
Après la nécessité de mettre la main au porte-monnaie lors de la migration de Virtual Infrastructure 3.5 (version Entreprise) vers vSphere 4 Entreprise Plus, on apprend au détour de la release notes de l’update 1 de vSphere que la future version de vCenter (4.1 ???) nécessitera d’être installée sur un OS 64 bit :
“Future releases of VMware vCenter Server might not support installation on 32-bit Windows operating systems. VMware recommends installing vCenter Server on a 64-bit Windows operating system. If you have VirtualCenter 2.x installed, see the vSphere Upgrade Guide for instructions on installing vCenter Server on a 64-bit operating system and preserving your VirtualCenter database.”
Il va falloir à nouveau sortir quelques euros (de manière détournée) pour migrer ces licences Windows 2003 ou 2008 32 bit en 64 bit pour pouvoir préparer l’arrivée de la future version.
Ce cout caché peux d’autant faire monter la facture que le SGBD est installé sur la même machine.
Comique de la situation si vous souhaitez profiter de la migration vers vCenter 4.0 Update 1 pour migrer sur un OS 64 bit sachez que le vCenter nécessite un DSN 32bit
Astuce :
lancer le ODBC DNS Tools version 32 bits à partir de la commande suivante :
[WindowsDir]\SysWOW64\odbcad32.exe