VMware.com Feeds

Some reasons why ESX servers may have problems accessing SAN storage when using Emulex HBAs (1004157) -

Some reasons why ESX servers may have problems accessing SAN storage when using Emulex HBAs (1004157) · The following messages appear on the ESX Server host console at boot time. The ESX Server host is booting from local storage and it is attached to

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Upgrading to ESX 4.0 and vCenter 4.0 best practices (1009039) -

Upgrading to ESX 4.0 and vCenter 4.0 best practices (1009039) This article provides steps which may be useful when upgrading to ESX 4.0 and vCenter Server 4.0. Note: This article assumes that you have read the vSphere Upgrade Guide. This upgrade

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

hostd fails with a signal 11 error then fails repeatedly (1009160) -

hostd fails with a signal 11 error then fails repeatedly (1009160) You are experiencing these issues with the hostd service: · hostd fails with a signal 11 error then fails repeatedly in a loop. · /var/core rapidly fills with hostd core files. ·

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

ESX machines hosting passive MSCS nodes report reservation conflicts during storage operations (1009287) -

ESX machines hosting passive MSCS nodes report reservation conflicts during storage operations (1009287) · Rescanning for new storage takes a very long time to complete. The VMware Infrastructure (VI) Client might report a timeout. · Using the *Add

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Corrupt heartbeat region – Problems accessing files on a VMFS datastore (1012036) -

Corrupt heartbeat region – Problems accessing files on a VMFS datastore (1012036) · You have problems accessing certain files. These files cannot be modified or erased. · The following entries appear in /var/log/vmkernel: Jun 16 13:43:21 vmhost-tp7

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Force mounting a VMFS datastore residing on a snapshot LUN results in the error: Cannot change the host configuration (1015986) -

Force mounting a VMFS datastore residing on a snapshot LUN results in the error: Cannot change the host configuration (1015986) As per the vSphere 4.0 SAN Configuration Guide, a VMFS datastore residing on a LUN that has been detected as a snapshot

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Enabling syslog on ESXi (1016621) -

Enabling syslog on ESXi (1016621) All ESX and ESXi hosts run a syslog service (syslogd) which logs messages from the VMkernel and other system components to a file. On ESXi hosts, you can use the vSphere Client or the vSphere CLI command

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Forward vpxa logs to syslog (1017658) -

Forward vpxa logs to syslog (1017658) In ESXi vpxa logs are not sent to syslog by default. If you want to send the logs to a remote syslog server, there is no way to have the vpxa logs follow hostd and vmkernel logs as they are sent to syslog

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Error message: Cannot open root device. Please append a correct "root=" boot option (10196) -

Error message: Cannot open root device. Please append a correct "root=" boot option (10196) · You see an error message similar to the following: VFS: Cannot open root device "UUID:048b19c0-9850-4676-8b00-f42a6854427e" or 00:00 Please append a

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

VMware vCenter Lab Manager 4.0.2 Web Console is Blank if the VMware vCenter is Installed on the Same Machine (1020474) -

VMware vCenter Lab Manager 4.0.2 Web Console is Blank if the VMware vCenter is Installed on the Same Machine (1020474) vCenter Lab Manager installs an ActiveX plugin to display the Web console in Microsoft Internet Explorer. If vCenter 4.x Client is

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

test for manishp Hz 531852 (1020807) -

test for manishp Hz 531852 (1020807) test test

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

NIC teaming using EtherChannel leads to intermittent network connectivity in ESXi (1022751) -

NIC teaming using EtherChannel leads to intermittent network connectivity in ESXi (1022751) When trying to team NICs using EtherChannel, the network connectivity is disrupted on an ESXi host. This issue occurs because NIC teaming properties do not

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Finding all enabled guest accounts (1023267) -

Finding all enabled guest accounts (1023267) You may want to get a list of enabled guest accounts in your environment to disable the accounts for improved security. This article provides the steps to find the enabled guest accounts in your

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Loading a custom fingerprint in VMware vCenter Application Discovery Manager (1023307) -

Loading a custom fingerprint in VMware vCenter Application Discovery Manager (1023307) This article provides steps for loading a custom Detail Discovery fingerprint in VMware vCenter Application Discovery Manager (ADM). The Detail Discovery

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Inserting data into the database fails with the error: An error has occurred while inserting detail discovery results (1023373) -

Inserting data into the database fails with the error: An error has occurred while inserting detail discovery results (1023373) · Inserting data into the database fails · Cannot insert data into the database · You see this error in the GUI: An error

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

vCenter Configuration Manager services do not start after modifying the service account (1023391) -

vCenter Configuration Manager services do not start after modifying the service account (1023391) vCenter Configuration Manager (VCM) services, such as the Collector and Server Advisor services, do not start after services accounts are modified. This

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Setting up MAPI for incoming emails in VMware Service Manager (1023557) -

Setting up MAPI for incoming emails in VMware Service Manager (1023557) This article provides the steps to configure MAPI for incoming emails in VMware Service Manager. VMware Service Manager supports MAPI for incoming emails on systems with Rolling

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Calls logged through VMware Service Manager incoming email end up in the wrong partition (1023677) -

Calls logged through VMware Service Manager incoming email end up in the wrong partition (1023677) Calls logged through VMware Service Manager incoming email end up in the wrong partition This article provides you the information to set the calls

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Upgrade the Jetty Web server embedded in VMware vCenter Update Manager by using a security fix (1023962) -

Upgrade the Jetty Web server embedded in VMware vCenter Update Manager by using a security fix (1023962) The following VMware vCenter Update Manager versions embed the Jetty Web server version 6.1.6: · Update Manager 1.0 Update 2 and later · Update

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

CMDB Link Type functionality in Service Manager 9.x (1025210) -

CMDB Link Type functionality in Service Manager 9.x (1025210) · When trying to link two CMDB items, you are prompted with the CMDB link type dialog box, but your Container-Component link type is not displayed. CMDB Link Type functionality has been

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Timekeeping best practices for Windows (1318) -

Timekeeping best practices for Windows (1318) This article presents best practices for achieving accurate timekeeping in Windows Guest operating systems. These recommendations include a suggested configuration for time synchronization in the guest

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Creation of New RDM for MSCS Cluster Node when Cluster Service Is Active on Another Node (1862) -

Creation of New RDM for MSCS Cluster Node when Cluster Service Is Active on Another Node (1862) I am using a Cluster-Across-Boxes or N + 1 configuration for Microsoft Cluster Services. I am attempting to add a raw device map (RDM) for the shared

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Microsoft Office SharePoint Server 2007 Performance on VMware vSphere 4.1 -

Microsoft Office SharePoint Server 2007 Performance on VMware vSphere 4.1 VMware recently released a whitepaper showing the performance scalability of SharePoint Server 2007 on VMware vSphere 4.1. This paper demonstrates that vSphere 4.1 exhibits high performance and includes advanced features that can improve the overall user experience in multi-tier applications such as SharePoint. Results of the experiments, in which up to 171,600 heavy SharePoint users were supported on a single physical server, highlight the benefits gained by the ability to easily deploy additional SharePoint virtual machines as needed to satisfy changing demands This paper also discusses some of the advanced features of VMware vSphere 4.1—such as memory compression, NUMA-aware resource management, and inter-VM communication—that allow vSphere to efficiently virtualize resource-intensive and latency-sensitive applications. The paper concludes with a set of recommended best-practices for achieving optimal SharePoint performance on VMware vSphere 4.1. For more information on this research, read the full paper: Microsoft Office SharePoint Server 2007 Performance on VMware vSphere 4.1.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Understanding Memory Resource Management in VMware ESX Server 4.1 -

Understanding Memory Resource Management in VMware ESX Server 4.1 We have published a whitepaper about how ESX server 4.1 manages the host memory resource. This paper not only presents the basic memory resource management concepts but also shows experiment results explaining the performance impact for four different memory reclamation techniques: Page sharing, ballooning, memory compression and host swapping used in ESX server 4.1. The experiment results show that: 1) Page sharing introduces negligible performance overhead; 2) Compared to host swapping, ballooning will cause much smaller performance degradation when reclaiming memory. In some cases, ballooning even brings zero performance overhead. 3) Memory compression can significantly reduce the amount of the swapped out pages and hence greatly improve the overall performance in high memory overcommitment scenario. The following is the brief summary of the paper. In this paper, we start from introducing the basic memory virtualization concepts. Then, we discuss the reason why supporting memory overcommitment is necessary in ESX server. Four memory reclamation techniques are currently used in ESX server: Transparent Page Sharing (TPS), Ballooning, Memory Compression and Host Swapping. We illustrate the mechanism of these techniques and analysis the Pros and Cons of each technique from performance perspective. In addition, we present how ESX memory scheduler uses a share-based allocation algorithm to allocate memory for multiple Virtual machines when host memory is overcommitted. Beyond the technique discussion, we conduct experiments to help user understand how individual memory reclamation techniques impact the performance of various applications. In these experiments, we choose to use SPECjbb, Kernel Compile, Swingbench, SharePoint and Exchange benchmarks to evaluate different techniques. Finally, based on the memory management concepts and performance evaluation results, we present some best practices for host and guest memory usage. The paper can be found in http://www.vmware.com/files/pdf/techpaper/vsp_41_perf_memory_mgmt.pdf Note that this paper is written based on ESX4.0 memory management paper. Besides the new content introduced in ESX4.1, e.g., memory compression, quite a few places have been updated to represent the state of the art of ESX memory management.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Enhanced VMware ESX 4.1 CPU Scheduler -

Enhanced VMware ESX 4.1 CPU Scheduler Check out our technical paper on ESX CPU scheduler in vSphere 4.1. This is revised from the previous version to reflect a new feature, wide VM NUMA support. This paper attempts to answer the following questions: How is CPU time allocated between virtual machines? How well does it work? What is the difference between “strict” and “relaxed” co-scheduling? What is the performance impact of recent co-scheduling improvements? What is the “CPU scheduler cell”? What happened to the scheduler cell in ESX4? How does ESX scheduler exploit the underlying CPU architecture features like multi-core, hyper-threading, and NUMA? The following provides a brief summary of the paper: ESX 4.1 introduces wide-VM NUMA support, which improves memory locality for memory-intensive workloads. Based on testing with micro benchmarks, the performance benefit can be up to 11–17 percent. In ESX 4, many improvements have been introduced in the CPU scheduler. This includes further relaxed co-scheduling, lower lock contention, and multicore-aware load balancing. Co-scheduling overhead has been further reduced by the accurate measurement of the co-scheduling skew and by allowing more scheduling choices. Lower lock contention is achieved by replacing the scheduler cell lock with finer-grained locks. By eliminating the scheduler cell, a virtual machine can get higher aggregated cache capacity and memory bandwidth. Lastly, multicore-aware load balancing achieves high CPU utilization while minimizing the cost of migrations. Experimental results show that the ESX 4 CPU scheduler faithfully allocates CPU resources as specified by users. While maintaining the benefit of a proportional-share algorithm, the improvements in co-scheduling and load-balancing algorithms are shown to benefit performance. Compared to ESX 3.5, ESX 4 significantly improves performance in both lightly-loaded and heavily-loaded systems. The paper can be downloaded from http://www.vmware.com/resources/techresources/10131.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Open Standards for Interoperability, Portability, and Security -

Open Standards for Interoperability, Portability, and Security Posted by Winston Bumpus Director of Standards Architecture, VMware I’m Winston Bumpus, director of standards architecture at VMware and president of the Distributed Management Task Force Inc. (DMTF). I want to share some thoughts on the ever-evolving cloud computing environment, specifically around open standards and open source software. You might have seen an announcement this week on OpenStack, and I wanted to take this opportunity to shed light on VMware’s opinion on the value of open source and the need to view it differently from interoperability. OpenStack, an initiative between NASA and Rackspace, a VMware service provider partner, seeks to accomplish some interesting standards work similar to other open source cloud projects like Nebula, offering customers another choice in cloud platforms. We love providing customers choice of hardware, operating systems, management platforms and cloud computing platforms. We expect to see all sorts of cloud computing implementations that will provide customers a range of price points, features, benefits and specs based on their requirements. But what’s most important to us as it relates to these various implementations – those that currently exist and those that are still to come – is that the interfaces work together so that true choice is possible. When we look at cloud computing, we approach it from a customer-centric point-of-view. We’re in a new era of computing and we see three key issues with Infrastructure as a Service (IaaS) cloud computing that currently concern customers: Interoperability (common APIs) Portability (standard packaging and deployment formats) Security (standards-based security infrastructure) We’re working on all three of these issues through: Our support of the Open Virtualization Format, which is currently the key cloud standard for interoperability Our participation in cloud standards development within the DMTF and working with other industry leaders including AMD, CA, Cisco, Citrix, EMC, Fujitsu, HP, Hitachi, IBM, Intel, Microsoft, Oracle, Novell, Rackspace, RedHat, Savvis, and SunGard. Our work with the Cloud Security Alliance to develop cloud security best practices based on existing standards and technology. Additionally, we don’t confuse open standards with open source. Open source is a collaborative development process for creating an implementation of a product or service while open standards are developed by a collaborative process to ensure interoperability among various competing product offerings. We’re huge supporters of open source software efforts, having placed major bets on Spring and RabbitMQ, among others. And while open source makes sense for some product offerings, open standards provide interoperability between open sourced, shared sourced, and private sourced implementations. We believe that customers should be able to choose the best products at the best prices and have the flexibility to migrate to a better solution if and when it becomes available. That’s why open standards are critical for both open sourced and other sourced implementations. We partner with numerous companies, some of which are developing open source cloud computing environments, and we expect those partnerships to continue to grow. But when it comes to interoperability, we encourage customers to judge technologies on performance, not how they were developed.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Latest Updates -

Latest Updates These are the changes or updates made to VMware Compatibility Guide since it was last published: Added support for FreeBSD 8.0 on ESX 4.1 Added support for Debian 4 r9 on ESX 4.1 Added support for Debian 5.0.5 on ESX 4.1 Check the VMware Compatibility Guide here: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

vCO Team Blog -

vCO Team Blog Two of my colleagues recently launched a new website. It is probably one of the few vCenter Orchestrator Blogs out there and definitely worth following for anyone who is into orchestration and automation. Besides of course covering the vCenter Orchestrator 4.1 release extensively they wrote multiple very useful and detailed articles on vCenter Orchestrator. One of the first articles explains how to create a self provisioning portal with vCO in a detailed stepwise approach. They have just published a follow called "part 2". The article cover the following steps which result in a self provisioning portal: How to create a simple Workflow How to map inputs, outputs, and attributes How to launch a Workflow from a webview, using the vCenter Orchestrator Weboperator How to launch a Workflow from the vCenter Orchestrator Client How to create a Workflow using subworkflows How to map inputs, outputs, and attributes How to use user interactions How to do basic presentations How to use validation presentation properties How to handle exception and write to the event log How to use vCO Server and System objects in scriptable boxes How to use the API search How to launch a Workflow from the vCenter Orchestrator Client How to launch a Workflow from a webview, using the vCenter Orchestrator Weboperator How to set rights on workflows How to set up the vCO mail plug-in

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

vSphere 4.1 and more -

vSphere 4.1 and more We've very pleased to announce the availability of VMware vSphere 4.1 and several other products today. Here's an initial overview of what's new and what's changed. (Updated 7/13 with press releases, blog posts) The Press Releases At VMware, our press releases are very readable and actually worth checking out. Here are the highlights for the two releases that came out July 13: VMware Advances Foundation for Cloud Computing With VMware vSphere 4.1 and Expanded Virtualization Management Portfolio Introduces the concept that vSphere 4.1 is a platform to build cloud infrastructures Goes over the big new features -- see also Steve's blog post (below) Talks about new cloud-based (per-VM) licensing models that we're introducing for several of our vCenter management products Talks about bringing over the Ionix acquisitions to new branding and support from VMware Teases the new Essentials pricing (see the next release) VMware Introduces Enhanced Virtualization Offerings for Small and Midsize Businesses Some background on SMB use of virtualization - contrary to what you might think, small businesses actually often make use of our "enterprise-grade" virtualization feature vMotion in Essentials and Standard Essentials is now list priced at $495/6 processes ESXi (free version) now called "VMware vSphere Hypervisor". We'll now use ESX & ESXi just to refer to the two different architectures. Blog Posts Here are some important blog posts we published. VMware vSphere 4.1: Advancing the Platform for Cloud Computing from VMware CTO Steve Herrod: "And I thought I’d close with a bit tech-y, but great quotation about this release from one of our more than 800 beta-testing customers... "This release has the stability of a ‘dot-1’ release with the advancements of a ‘dot-0’ release". Indeed!" vSphere and vCenter: The Foundation of VMware's Cloud Strategy from VMware Marketing VP Bogomil Balkansky: "VMware is bringing the benefits of cloud computing to internal datacenters by helping customers more efficiently and effectively manage existing applications while building the path to the private and public cloud. This is what virtualization is all about. By enabling an evolutionary approach to cloud, VMware vSphere and VMware vCenter are the foundation for our cloud strategy" Steve also contributed this short video introduction to vSphere 4.1: VMware vSphere 4.1 VMware vSphere 4.1 product overview "Begin the Journey to a Private Cloud with Datacenter Virtualization" What's New in vSphere 4.1 VMware vSphere 4.1 Release Notes - ESXi Edition VMware vSphere 4.1 Release Notes - ESX Edition VMware vSphere 4.1 product support & downloads VMware Scripting - SDK Developer Support available for vSphere SDK 4.1 (Developer Center Blog) Performance Implications of Storage I/O Control in vSphere Environments with Shared Storage (VROOM!) vSphere 4.1 is Here! Tell Me Something About the Release I May Not Know (vSphere Blog) vSphere 4.1 has shipped! (VIX API Blog) Got Network I/O Control? (VMware Networking Blog) PowerCLI 4.1 is out (PowerCLI Blog) VDR and vSphere 4.1 Compatibility (Uptime Blog) EMC Ionix Customers Transitioning to VMware Support July 1st (Support Insider Blog) VMware ESXi VMware ESXi and ESX Info Center "Planning your upgrade to VMware ESXi, the next-generation hypervisor architecture." t’s here! The latest version of ESXi (ESXi Chronicles) VMware vSphere Hypervisor The product formerly known as "free ESXi" VMware vSphere Hypervisor product overview VMware vSphere Hypervisor community with an explanation of the change Introducing VMware vSphere Hypervisor 4.1 - the free edition of VMware vSphere 4.1 (vSphere Blog) VMware vCenter Server Heartbeat 6.3 VMware vCenter Server Heartbeat product overview VMware vCenter Server Heartbeat 6.3 Release Notes VMware vCenter Site Recovery Manager 4.1 VMware vCenter Site Recovery Manager product overview VMware vCenter SRM 4.1 Release Notes Upgrading to SRM 4.1 - including upgrading to vSphere VirtualCenter 4.1 (Uptime Blog) VMware Studio 2.1 VMware Studio product overview VMware Studio 2.1 release notes VMware Studio 2.1 now available for download (blog post) For more information For the full picture -- and it's a big picture, because vSphere 4.1 is a big release, I recommend: Planet V12n the aggregation of dozens of blogs from the community of VMware users Eric Siebert's comprehensive vSphere 4.1 - The Links

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Performance Implications of Storage I/O Control in vSphere Environments with Shared Storage -

Performance Implications of Storage I/O Control in vSphere Environments with Shared Storage vSphere based virtualized datacenters often employ a shared storage infrastructure to support clusters of vSphere hosts. Applications running in virtual machines (VM) on vSphere hosts share the storage resources for their I/O needs. Performance of applications can be impacted when VMs contend for storage resources that are shared. Without proper access control for sharing the resources, the performance of all applications tend to get affected in a non-trivial way. Storage I/O Control (SIOC), a new feature offered in VMware vSphere 4.1, provides a dynamic control mechanism for proportional allocation of shared storage resources to VMs running on multiple hosts. The experiments conducted in VMware performance labs show that: SIOC prioritizes VMs’ access to shared I/O resources based on disk shares assigned to them. If the VMs do not fully utilize their portion of the allocated I/O resources on a shared datastore, SIOC redistributes the unutilized resources to those VMs that need them in proportion to the VMs’ disk shares. SIOC minimizes the fluctuations in performance of a critical workload during periods of I/O congestion. For the test case executed at VMware labs, limiting the fluctuations to a small range resulted in as much as a 26% performance benefit compared to that with the default configuration (figure 1). Figure 1. Application throughput with and without SIOC enabled For further details, read the white paper titled “Managing Performance Variance of Applications Using Storage I/O Control” at http://www.vmware.com/resources/techresources/10120

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

VMware vSphere 4.1: Advancing the Platform for Cloud Computing -

VMware vSphere 4.1: Advancing the Platform for Cloud Computing Posted by Steve Herrod Chief Technology Officer A number of our recent VMware blog posts have focused on the newer VMware technology areas... SpringSource, RabbitMQ, Gemstone, and the partnerships we're forming to deliver cloud-portable applications. With this blog post, I get to highlight vSphere and vCenter, VMware's largest engineering investment areas and the very foundation of our broader cloud computing story. Today we are announcing general availability of VMware vSphere 4.1, and I'd like to share a bit more about it from both a technology and an engineering process perspective. First, the technology… when we launched vSphere 4.0 in May of last year, we highlighted three main themes that are core enablers of cloud computing: Efficiency, Control, and Choice. These are themes that you’ll see us focus on for many years to come, and we’ve made major progress on each of them with vSphere 4.1. Efficiency: The goal here is to squeeze the most out of your hardware investment and to make management of large, virtualized datacenters simple and scalable. We’ve made major progress on this theme with 4.1. Two areas I particularly like are: Memory compression Simultaneous vMotions I’m also excited in how we’ve dramatically increased the scalability of almost every component of our product suite. In vSphere 4.0, the engineering team made several major architectural changes designed to help the software scale better. We took some advantage of these in 4.0, but with 4.1, we’ve had a chance to really exploit the new software base. Here’s just a selection of the key scalability improvements: Those are some pretty big increases to a product that is already fairly scalable! Control: The focus of this theme is helping IT have complete control over the performance and availability of their applications, something particularly challenging in today’s public clouds. The biggest breakthrough we’re delivering in this area focuses on storage and the ability to guarantee certain levels of bandwidth to a VM, even in a heavily consolidated and multitenant environment. There were some early videos showing off earlier versions of this new Storage IO Control capability. You can read more about it and just try to request guarantees on performance from today’s clouds! Choice: The last theme is around enabling customer choice… choice as to what applications you run, what hardware you run them on, and, as we move forward, which cloud you run them in. With vSphere 4.1, we continue to increase VM performance, making virtualization a no brainer for even the highest end applications]. We’ve also continued to grow our hardware compatibility list substantially, ensuring that you can leverage your existing investments while having broad choice as to your future hardware purchases. As of this writing, vSphere 4.1 is fully supported with more than 2000 server models and more than 2200 storage array targets. And stay tuned for more news as to how vSphere 4.1 forms the foundation of cloud portability… This is just a short take on the technology advances. There’s lots more data available here and I’ve also recorded a short video to give more context to the above advances. As for the engineering process angle, I’m extremely proud of how the team delivered this release. After the launch of vSphere 4.0, we have moved to a “train model” of vSphere and vCenter product releases, targeting more regular (and predictable) releases of the software. This is critical to customers and partners, who are basing a lot of their own products and plans on new vSphere and vCenter offerings. And we plan to keep the trains running on time, so we’re already hard at work on the next two vSphere and vCenter releases where we’ll continue to push forward on efficiency, control, and choice. And I thought I’d close with a bit tech-y, but great quotation about this release from one of our more than 800 beta-testing customers... "This release has the stability of a ‘dot-1’ release with the advancements of a ‘dot-0’ release". Indeed! Happy virtualizing, all!

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Read The Effin Blog!

… technical docs and manuals just never quite cut it.

VMware.com Feeds

The Press Releases

Blog Posts

VMware vSphere 4.1

VMware ESXi

VMware vSphere Hypervisor

VMware vCenter Server Heartbeat 6.3

VMware vCenter Site Recovery Manager 4.1

VMware Studio 2.1

For more information

Leave a Response

What I'm Doing via Twitter...

Recent Posts

Recent Comments

Categories

Blogroll

Archives

Tags

Meta

Top 5 Planet V12n blog posts week 26 Been really busy today with the kids but did manage to get the top 5 ready for you guys.... Read it! Thomas Mackay - Understanding ESX/ESXi Equivalency…Are we there yet? It is public knowledge that ESX is evolving to a pure ESXi model in the future release cycles of the product, though exact timelines are still under NDA. Convergence to a “console-less” ESX provides a number of benefits to our customers, with which many of you are, by now, well acquainted . It reduces the overall footprint that requires patching (see below) as well as removes the dependency on the vestigial RHEL-based Console Operating System, and sets the stage for future enhancements and technologies yet to be introduced. (Those who are under NDA might know to what I am referring! Thakala(vReality) - VMware Data Recovery 1.2 Linux file level restore client I have successfully tested it on 64-bit CentOS 5.5, and because so many versions of Ubuntu are listed I’d guess that FLR client works on any recent Debian releases also, just make sure it has support for FUSE 2.5 or later. If you have custom kernel make sure you have all FUSE dependencies compiled in. Note that even though your Linux distribution may be 64-bit version, 32-bit version of FUSE is required. Note the absence of any SuSE or Novell SLES distrubtions from tested and supported list, not that FLR client won’t work on them though, I am sure it will. Jon Owings - All out of HA Slots As you can see here the slot size is rather giant. We have the largest CPU and Memory reservation plus some overhead (for simplicity) and that blows the size of the slot way up. I didn’t set the reservation, but surely they were there. 8GB of reserved memory. 4000MHz of CPU. Ouch. Where did that come from? It followed the VM from the old host to the new one. One of the reasons I was there was to setup a new cluster since the older ones were performing so slow on the local storage. It seems like someone tried to help some critical VM’s along the way by adding the reservations. I removed the reservations and had plenty of slots as you see below. Massimo Re Ferrre - Cloud and the New IT Pillars In my previous IT life I was in the business of trying to homogenize heterogeneous virtualization platforms under a single management umbrella so I have to (strongly) agree with my colleague’s statement. In fact, these pillars are very different in the way you manage them. This is true not only from a technology perspective but also, and even more so, from a process perspective. For example, the process to request a partition on a legacy Unix system may be totally different than the process required to instantiate a new physical server, which in turn is totally different than the process to request a new vSphere virtual machine. To complicate things more, the Cloud pillar, by very definition, doesn’t require any process whatsoever to instantiate a new workload from the self-service portal. Duncan Epping - vSphere 4 U2 and recovering from HA Split Brain I had never noticed this until I was having a discussion around this feature with one of my colleagues. I asked our HA Product Manager and one of our developers and it appears that this mysteriously has slipped. As I personally believe that this is a very important feature of HA I wanted to rehash some of the info stated in that article. I did rewrite it slightly though...

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Top 5 Planet V12n blog posts week 25 The World Cup tournament just entered the knockout stage. Today England plays against Germany and I guess it is needless to say that I will be supporting England, or should I say "Engerland"? (Hey, no one loves their neighbours.) All of this has of course nothing to do with the reason I am writing this article. This article is about the top 5 Planet V12n articles of week 25. This week we've got a "newcomer", I guess this is my way of saying welcome William. Here we go: Kendrick Coleman - Why vSphere Needs NFSv4 If you are familiar with my blog, you'll know that I'm a huge advocate of the NFS protocol with VMware. I firmly believe that over the next few years, ethernet storage will be the front-runner of VMware deployments. Most of the people that I talk to that have a Fiber-Channel (FC) based environment are in large enterprises that made the switch to VMware but used their existing FC environment. Which is great, but now is the time everyone is starting to virtualize their whole environment and money talks when it comes to scalability. I won't go into Ethernet vs FC because there is boat loads of information already out there, but let's talk about NFS. NFS is that guy sitting in the corner that doesn't get much attention, but NFS is making headway into the marketplace. Vaughn Stewart - Data Compression, Deduplication, & Single Instance Storage Storage savings technologies are all the rage of the storage and backup industries. While every vendor has their own set of capabilities, it is in the best interest for any architect, administrator, or manager of data center operations to have a clear understanding of which technology will provide benefits to which data sets before enabling these technologies. Saving storage while impeding the performance of a production environment is a sure-fire means to updating one's resume. Daniel Eason - VMware DPM usage – My view DPM technology is excellent and to be honest plain common sense, it has moved from being experimental into full blown production supportable within the later versions of ESX and now as a de facto proven product within vSphere. Core Main benefit of DPM is simple, it will dynamically turn off virtual hosts that are not needed at non peak times which is great, it avoids the cost that would have been occurred by running even vSphere hosts in an under utilised state. So I’ll get to the point do I think DPM is capability that can be used it to obtain the saving to anyone? well not really to be honest, I am in the non enthusiastic camp when it comes to DPM and the reasons I think this are as follows... William Lam - ESXi syslog caveat Append the above entries between the ... tags. Once you have updated the vpxa.cfg file, you will want to run the follow command on the Busybox console to ensure the changes are saved and backed up to the local bootbank for ESXi. There is an automated cron job that runs every hour which calls /sbin/auto-backup.sh Scott Drummonds - Private Clouds, People Consolidation, and Chargeback The beauty of virtualization is that not only can the physical resources be shared, as any VMware demonstration will prove, but the people that support the infrastructure can be shared, too. This concept is already understood by VMware’s more mature customers, who have been telling VMware for years that virtualization can save more money in operational expenses than capital expenses. These savings are coming after thinning the ranks of dedicated infrastructure specialists and refocusing them on higher value opportunities.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Top 5 Planet V12n blog posts week 24 As it was fathers day yesterday and I also had to fly out to London I totally forgot to hit the "publish" button. I did however create a Top 5: David Davis - VIDEO: Mike DePetrillo speaking on VMware vCloud One of the most controversial parts of Mike’s presentation is when he says that vCloud is really sold to the CIO and the message to the IT group is that you will have to change in order to keep your job. In other words, “the cloud” will assimilate the infrastructure as we know it and IT people will have to adapt to that, improving their skill set, in order to move to different roles in the IT organization where they can accomplish the more important IT projects with real ROI (not just maintaining the SAN LUNs, or whatever they do). Watch the video to hear the vCloud message for yourself… Note: Mike doesn’t show a “Project Redwood” demo – sorry. Eric Sloof - StarWind iSCSI multi pathing with Round Robin and esxcli After you have created a StarWind iSCSI target, it’s ready to service connections. You can established a connection to an iSCSI target and it appears as a new datastore on your ESX server. I’ll show the operations you need to complete to create and format the datastore in the way your ESX server can create virtual machines on it. I’m also going to show how the esxcli command can be used for PSA (pluggable storage architecture) management and explain how to use the vSphere Client to manage the PSA, the associated native multipathing plug‐in (NMP). Tod Muirhead - Scale-Out Performance of Exchange 2010 Mailbox Server VMs on vSphere 4 The performance in the 4000 user tests shows a rise of only 30ms in the 95th percentile SendMail response time between a single 4-vCPU VM and four 1-vCPU VMs. The 8000 user tests show an increase of approximately 140ms in the same metric when comparing the single 8-vCPU VM with four 2-vCPU VMs. Even though this is a significant percent increase, the absolute increase is still relatively small in comparison to the 1 second threshold which is where users will begin to perceive a difference in performance. Martin Klaus - Operations Management in the Virtualized Environment – What’s different? As the foundation for the Private Cloud, virtualization enables server, storage and networking resources to be shared very efficiently across applications. Virtualization also allows you to standardize your service offerings. Templates for your corporate Windows or Linux images can be provisioned as virtual machines in minutes. Even higher-level server configurations with complete web, application and database server stacks can become building blocks for your Enterprise Java environments or Sharepoint instances, further simplifying the provisioning process and lessening the need for one-off admin tasks. Automated backup, patch and update processes are additional benefits that are easy to realize with virtualized infrastructure. Scott Lowe - The vMotion Reality In his article, Benik states that the ability to dynamically move workloads around inside a single data center or between two data centers is, in his words, “far from an operational reality today”. While I’ll grant you that inter-data center vMotion isn’t the norm, vMotion within a data center is very much an operational reality of today. I believe that Benik’s article is based on some incorrect information and incomplete viewpoints, and I’d like to clear things up a bit.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Scale-Out Performance of Exchange 2010 Mailbox Server VMs on vSphere 4 This is the third part in a series of blog posts on Exchange 2010 performance on vSphere 4. In the first post, tests were done to show the scale-up performance of a single Mailbox Server VM hosting up to 8000 users. The second post was about how increasing the amount of RAM would reduce the number of IOPS, resulting in better performance. This article is about scale-out performance with multiple Exchange 2010 Mailbox Server VMs. For a variety of reasons, it often makes sense to have more than one Mailbox Server in an Exchange environment. Testing was conducted in VMware labs to determine the performance impact of spreading the same number of users across multiple VMs as opposed to running them in a single VM. The results showed that great performance was maintained with only a slight increase in latency when scaling out with either of the 4000 or 8000 user scenarios. Configuration The same configuration was used as in the previous two blogs. A Dell PowerEdge R710 with dual quad-core Xeon X5570 processors and 96GB of RAM was installed with a development version of vSphere 4 (build 235768). In the previous tests, there were three Exchange VMs running on the vSphere server: Mailbox, CAS, and Hub. For these scale-out tests, the number of Mailbox Server VMs was increased to 4 and the CAS and Hub Server VMs were moved to another vSphere server. This resulted in only four Mailbox Server VMs running on the vSphere server being tested. Storage for the VMs was increased to provide additional space for the new Mailbox Server VMs. The number of data LUNs was doubled, resulting in four 9-disk RAID 5 LUNs with each VM having virtual disks on all of the LUNs. Microsoft Exchange Load Generator 2010 Beta was used to simulate the users for the scale-out tests. The Online Outlook 2007 Very Heavy profile with 100 MB mailboxes was used. The option to have all LoadGen Users pre-logon was set, and the rest of the settings for LoadGen 2010 beta were left at default values. Testing In order to test the scale-out performance of Exchange 2010 on vSphere, the same number of users were run on a single Mailbox Server VM, two Mailbox Server VMs, and four Mailbox Server VMs. The total amount of memory and vCPUs was kept constant and the users were evenly divided across the VMs. The charts below show the results for 4000 and 8000 user tests across one, two, and four VMs. The performance in the 4000 user tests shows a rise of only 30ms in the 95th percentile SendMail response time between a single 4-vCPU VM and four 1-vCPU VMs. The 8000 user tests show an increase of approximately 140ms in the same metric when comparing the single 8-vCPU VM with four 2-vCPU VMs. Even though this is a significant percent increase, the absolute increase is still relatively small in comparison to the 1 second threshold which is where users will begin to perceive a difference in performance. The reason for the increase in response time is due to an increase in IOPS, which puts additional load on the storage array and disk latency increases slightly. IOPS increases as VMs are added, even though the number of users stays the same, because using four smaller caches is less efficient than one large cache. This shows that Exchange 2010 does a good job of managing large caches when the RAM is available. Another way to look at the data is to compare the same size VMs being used to support an increasing number of users. A single 4-vCPU VM supporting 4000 users had a 95th percentile SendMail latency of 234ms and two 4-vCPU VMs supporting 8000 users had 314ms. Doubling the workload on the server with an additional Mailbox Server VM resulted in an increase of only 80ms. Conclusion Performance of Exchange 2010 in the scale-out tests on vSphere was great with response times well below 1 second. vSphere allows Exchange 2010 architects to have the flexibility to use multiple mailbox server VMs to create and manage their Exchange 2010 environment as their needs dictate and get great performance. At the same time testing indicated there is the opportunity to reduce IOPS by using fewer mailbox server VMs with larger RAM sizes instead of using a greater number of mailbox server VMs with less RAM. This aspect of Exchange 2010 performance is due to Exchange 2010’s ability to efficiently manage the larger memory size.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Top 5 Planet V12n blog posts week 23 As I was watching one of the World Cup games yesterday evening I totally forgot to click "publish". Thanks Jason for pointing this out. Here's this weeks top 5: Aaron Delp - Comparing Vblocks I believe one of the most interesting concepts to come along in our industry recently has been Cisco/EMC/VMware's Vblock. My best definition for Vblock is a reference architecture that you can purchase. Think about that for a second. Many vendors publish reference architectures that are guidelines for you to build to their specifications. Vblock is different because it is a reference architecture you can purchase. This concept is a fundamental shift in our market to simplify the complexity of solutions as we consolidate Data Center technologies. We are no longer purchasing pieces and parts, we are purchasing solutions. Scott Drummonds - VMDirectPath The only reason why anyone is considering VMDirectPath for production deployments is the possibility of increased performance. But the only workload for which VMware has ever claimed substantial gains from this feature is the SPECweb work I quoted above. That workload sustained 30 Gb/s of network traffic. I doubt any of VMware’s customers are using even a fraction of this network throughput on a single server in their production environments. Jason Boche - NFS and Name Resolution A few weeks ago I had decided to recarve the EMC Celerra fibre channel SAN storage. The VMs which were running on the EMC fibre channel block storage were all moved to NFS on the NetApp filer. Then last week, the Gb switch which supports all the infrastructure died. Yes it was a single point of failure – it’s a lab. The timing for that to happen couldn’t have been worse since all lab workloads were running on NFS storage. All VMs had lost their virtual storage and the NFS connections on the ESX(i) hosts eventually timed out. Frank Denneman - Memory Reclaimation, When and How? Back to the VMkernel, in the High and Soft state, ballooning if favored over swapping. If it ESX server cannot reclaim memory by ballooning in time before it reaches the Hard state, the ESX turns to swapping. Swapping has proven to be a sure thing within a limited amount of time. Opposite of the balloon driver, which tries to understand the needs of the virtual machine let the guest decides whether and what to swap, the swap mechanism just brutally picks pages at random from the virtual machine, this impacts the performance of the virtual machine but will help the VMkernel to survive. Duncan Epping - Is this VM actively swapping? At one point the host has most likely been overcommitted. However currently there is no memory pressure (state = high (>6% free memory)) as there is 1393MB of memory available. The metric “swcur” seems to indicate that swapping has occurred” however currently the host is not actively reading from swap or actively writing to swap (0.00 r/s and 0.00 w/s).

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

VMware vExpert 2010 [Updated Monday 7 June] The invitations to the VMware vExpert 2010 program have been sent out. Emails were sent out Friday and Monday; the timing had no bearing on the merit of your application! (If you were expecting an invitation, please check your junk mail filters. Although I tried not to use any words like Congratulations! or You Win a Million Dollars! or Free Herbal Prescriptions! I've gotten reports that spam filters did catch a few of the outbound emails.) We had a great selection of candidates this year, and I'm looking forward to working with all of you. All of the judges were very impressed with the applicants, and we made some very hard decisions about who to accept in the program. If you applied but did not get selected, I would be happy to work with you on planning for 2011 and how you might work toward a vExpert designation. The vExpert award looks backward on what you did the year before, and in the seven short months until Jan 2011 you could make quite an impact. Things move very quickly in the social media world, and people who rock it hard can get noticed quickly. There were a number of common cases in applications that weren't accepted: You didn't demonstrate enough activity. If your claim to vExpert fame is a blog, then you should blog like you mean it. If you are active on the community, then you should be very active. Although we tried to evaluate quality over quantity, blogging or answering questions on the community is an endurance sport, and the way to grow in knowledge and grow an audience is to be consistent over time. Take the time to blog (or speak, or whatever you do) every day. This is hard work. Work hard, but you just have to do one step at a time. After a year, you'll be shocked at how much you accomplished. (Now life may have intervened -- babies, work, health, and happiness are all part of living and should take precedence over virtualization evangelism. We'll catch you next year when you come up for air. No worries.) You participated but did not create. You came to events, podcasts, and more. You supported and commented and tweeted. You probably learned a lot, and you now know more people, but you didn't do a lot of sharing of your expertise. Creating is hard work, and we looked for people who sat their butts in their chairs and typed or powerpointed or otherwise instantiated their knowledge so that others could benefit. You have something to say to the world. Say it. What problem did you solve at work today? What are you passionate about? Give back to the world. Your didn't differentiate yourself. There are two related parts to this problem: one you can't do much about, but one that's the key to success. If you are in the English-speaking virtualization world, the bar for evangelism is very high. We're a bunch of smart people, and you're competing for people's attention against both geniuses and overachievers. (Oh, yes, I'm talking about the Dutch.) You can't do much about where you live, but you can figure out how to make yourself stand out. Don't just blog product and press releases. Go beyond. Blog your passion and tell people about what's important to you. Make a picture or a comic or a presentation or a video. *Become "that guy that does that amazing thing." Dare to be memorable.* You didn't demonstrate enough "above and beyond" activity outside your normal job. If your day job is to sell virtualization products, you had to pass a high bar to receive a vExpert award. The judges have a soft spot in our hearts for people who could be lounging on the couch at home or even at a hotel, but instead push it harder. Invest a slice of your time in yourself. Having fun doing something cool is the best way to stand out in your career. It's much better than not having fun and not standing out. You need to go deeper. Virtualization is a deep topic. vSphere is a deep product that cuts across all IT disciplines. We all start somewhere in our journey and from the perspective of where we've been. Be humble enough to realize that you might not understand the whole landscape yet. Do your homework. *Listen, learn, break out of your silo.* You didn't demonstrate enough reach outside your company. The vExpert award is at some level about evangelism. Sharing your expertise internal to your own company is wonderful, but the judges were also looking for people who had created a platform where they could influence beyond the boundaries of a single company -- thus the emphasis on a blog or speaking engagements. Go out and conquer! If you're introverted, write. If you're extroverted, speak. If you're brilliant, teach. If you're not brilliant, hook up with people that are and help organize! Make waves. Your application note wasn't detailed enough. Often, the judges couldn't determine exactly what impact you had in your activities, or exactly what you did. If someone else nominated you, they may not have adequately described exactly how awesome you were in 2009. I think we're moving to an application model (vs a nomination model) for next year. *Get ready to apply for 2011 - now is not the time to be modest.* Allow yourself to excel and then just let us know what you've been up to. Your activity was mostly in 2010. The award was given out for things you did in 2009. The next vExpert selection will be in seven short months, so if you just got going in 2010, you have a great runway to join the program next year. Keep it up! I hope something in that advice resonates with you. I'd love to work with you throughout this year and next - give me a buzz. For those that did get selected as vExperts, I've got more to say about why and what's coming up, but that came come later. I hope you're as excited as I am. Doors will be opening to our vExpert community site tomorrow! Cheers, John Troyer jtroyer@vmware.com

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.

Top 5 Planet V12n blog posts week 22 Week 22 already. Almost half way down 2010. Next week the Fifa World Cup starts. For those of you, probably Americans, who don't have a clue what it is about: World Cup Soccer. And yes this is the most widely viewed sports event there is and the cool thing about it is that you get to watch sports for 45 minutes in a row before you have a commercial break! Anyway, there's one thing left to say before I will list this weeks Top 5: GO HOLLAND! Cody Bunch - The Math Behind the DRS Stars In our particular case, not much to look at, as well, she is seemingly a well balanced cluster. However let’s work through the formula with the assumption that we have a 2 node cluster and a standard deviation of 0.282 (the “target” from above): 6 – ceil(0.282 / 0.1 * sqrt(2)). Eric Sloof - Caveat when using - Percentage of cluster resources reserved as failover spare capacity I think everyone knows the three admissions control policies which can be enforced on a VMware HA Cluster. If you are using the default “Host Failures Allowed” policy, you must keep in mind that the largest virtual machine reservation will decide how big your cluster slot size is going to be. In most cases when you are using reservations that differ, I would prefer to use the “Percentage of cluster resources reserved as failover spare capacity”. But be careful, I’ve pulled two quotes which warn us for scattered resources and the need to set restart priority on large virtual machines. Simon Long - VMware ESXi 4 Log Files This is the ESXi Host Agent log. It contains information on the agent that manages the ESXi Host and it's VM's. I don't tend to use this log as much as I used to with ESX, purely because it has been amalgamated in the message log. If you are troubleshooting a Host issue and don't want vmkernel logs getting in the way, this is the log for you. The log entries are time stamped (using UTC timezone) which is pretty handy when looking back to see what happened when an error occurred or something failed. Arnim van Lieshout - PowerCLI: Reset CPU and Memory Limits Today I noticed a memory limit on a vm. After investigating my environment using the vEcoShell and the Community PowerPack, I found more vms with memory limits set. It turned out that there was a template which had the limit set. I could easily reset all limits using the GUI, but I thought I rather do it with PowerCLI. Alan Renouf did a post already on a oneliner to reset all cpu and memory limits back in july 2009. After trying that code I found it rather slow. If you want to speed up things in PowerCLI you need to use the Get-View cmdlet. After some digging in the vSphere API Reference, I came up with a different peace of code that is much faster. Duncan Epping - esxtop -l As most of you know esxtop takes snapshots from VSI nodes (similar to proc nodes) to capture the running entities and their states. The rate in which these snapshots are taken can be changed with the “s”. The default setting is 5 seconds and the minimum, which most people probably use, is 2 seconds. This means that every entity (worlds, for instance a virtual machine) and the associated info is queried again every two seconds. As many of the metrics shown in esxtop are calculated based on the difference of two successive snapshots, e.g. %USED (CPU), esxtop just rereads all the info(all entities and all values) and calculates the values of the metrics.

Download VMware Products \| Privacy \| Update Feed Preferences Copyright © 2010 VMware, Inc. All rights reserved.