A few days ago VMware released vCenter 2.5 U4, the latest installment of their vCenter Server. I have yet to upgrade my environment(s), but I will be planning to do so very soon. There are two new enhancements to vCenter with this release, and a handful of updates.
- **Guest Operating System Customization Improvements
** VirtualCenter now supports customization of Windows Server 2008 guest operating systems.
- **Performance Overview Charts
** VirtualCenter 2.5 Update 4 introduces the Performance Overview plug-in, which provides a single view of key performance metrics for CPU, memory, disk, and network without having to navigate through multiple charts. The aggregated charts show high-level summaries of resource distribution. To install the Performance Overview plug-in, see Installing the Performance Overview Plug-In in VirtualCenter 2.5 Update 4 (KB 1008296)
One of the biggest updates that effects me personally is the update to Storage VMotion;
- **Storage VMotion Creates Temporary delta.vmdk Files Only for the Virtual Disks That Are Migrated
** In previous releases, if a virtual machine has more than one virtual disk and you want to move only some of the virtual disks to another datastore by using Storage VMotion, temporary delta.vmdk files are created for all virtual disks attached to the virtual machine. Starting with VirtualCenter 2.5 Update 4, during Storage VMotion, temporary delta.vmdk files are created only for the virtual disks that are migrated to another datastore.
This is a pretty big enhancement. With the current version, say you wanted to move a large backup VMDK to another datastore and you knew it would take a while to copy. SVMotion would actually snapshot all of the VMDK files for the Virtual Machine, migrate only the VMDK you chose to move then commit the snapshot. This means your delta VMDK files would typically be pretty large for your active VMDK disks, taking unnecessary disk space and time to commit.
I’m curious if they’ve resolved the issue of not migrating the VM config (vmx). Currently if you SVMotion’d a VM and kept the destination the same as its source for the vmx file, it would error saying that it is not supported.
For the full listing of changes, read the vCenter 2.5 U4 release notes.