VMware vCenter CapacityIQ 1.0.4 Release Notes

VMware vCenter CapacityIQ Version 1.0.4| 12 August 2010 | Build 276824

Last Document Update: 18 October 2010

These release notes describe the following topics:

What's New

CapacityIQ 1.0.4 is a maintenance release that adds support for vCenter Server 4.1.

This release does not support virtual machine-based licensing for CapacityIQ. CapacityIQ will provide this type of licensing support in an upcoming release.

Top of Page

Prior Releases of VMware vCenter CapacityIQ

Features from prior releases of CapacityIQ are described in the release notes for each release. To view release notes for prior releases, click one of the following links:

Top of Page

Before You Begin

Before you install CapacityIQ, review the support and scalability information and the vCenter CapacityIQ Installation Guide.

CapacityIQ supports VirtualCenter 2.5 with Update 4 or later versions, vCenter Server 4.0.x, and vCenter Server 4.1.x, managing hosts running ESX Server 3.0.1 through ESX 4.1.x.

CapacityIQ 1.0.4 supports 200 hosts, 2000 powered on virtual machines, and a total of 3000 virtual machines. These scalability limits exist even though the limits of vCenter Server 4.1 are 1000 hosts, 10000 powered on virtual machines, and 15000 registered virtual machines. For information about cluster sizes that exceed 400 virtual machines, see the Known Issues section of the release notes. For more information about vCenter Server scalability limits, see the Performance and Scalability Enhancements section of the What's New in VMware vSphere 4.1 — VMware vCenter white paper.

In a vCenter Linked Mode environment, you must install a separate instance of CapacityIQ for each vCenter Server system. The vCenter CapacityIQ Installation Guide will include this information in the next release. For information about Linked Mode, see the VMware vSphere documentation.

Top of Page

Known Issues

The following known issues affect the 1.0.4 release.


  • If you update CapacityIQ and log in to Setup tab of the Administration Portal, the values of the registration status and vCenter Server address might fail to appear or appear as unknown.

    Workaround: Refresh the browser page to update the information.

  • If you update CapacityIQ, the Plug-in Manager in the vSphere Client does not display the latest version and build number. The Plug-in Manager continues to display the older version of CapacityIQ.

    Workaround: To display the update data, unregister CapacityIQ in the Administration Portal and reregister it to the same vCenter Server system.

  • If you apply an update using the ciq-admin command-line interface, the build number in the Administration Portal header might not match the build number on the Status tab.

    Workaround: Press F5 to refresh the Administration Portal. When the Administration Portal logs you out, you can log in to the portal.


  • The Register CapacityIQ and the Grant Access to CapacityIQ sections of the vCenter CapacityIQ Installation Guide do not provide complete information on the roles and privileges required to set up CapacityIQ.

    New: Before you register CapacityIQ during the installation process, prepare and assign the CIQ_ADMIN role to the user who registers CapacityIQ. Because this process involves assigning permissions at the root vCenter Server folder level and propagating them to child objects in the inventory tree, the user cannot have conflicting permissions that are set outside of this process that block access to any objects.

    To prepare and assign the CIQ_ADMIN role:

    1. In the vSphere Client, create a role, such as CIQ_ADMIN, and assign the Manage custom attributes, Set custom attribute, and Licenses global privileges, and the Register extension, Unregister extension, and Update extension extension privileges.
    2. Right-click the root vCenter Server folder in the inventory tree and select Add Permission.
    3. In the Assign Permissions dialog box, assign the CIQ_ADMIN role to the user who is registering CapacityIQ and propagate the privileges to child objects.

    When you register CapacityIQ and type the user name and password for the vCenter Server system, the credentials must give you the privileges associated with the CIQ_ADMIN role.

    Before you grant access to CapacityIQ, the virtual appliance generates a CapacityIQ global privilege in the vSphere Client during an earlier phase of the configuration process.

    To grant access to CapacityIQ:

    1. Restart the vSphere Client.
    2. Add the CapacityIQ privilege to an existing role that is already assigned to a user or create a new role with the privilege and assign the role to a user.
    3. Right-click the root vCenter Server folder in the inventory tree and select Add Permission.
    4. In the Assign Permissions dialog box, assign the necessary role to the user who is accessing CapacityIQ.

    The CapacityIQ documentation will include this information in the next release. For more information about creating roles and assigning users to roles, see the VMware vSphere documentation.

  • Changes to roles and permissions for a user in the vSphere Client might result in a mismatched view of objects between the vSphere Client inventory panel and the CapacityIQ inventory panel.

    Workaround: Press F5 to refresh the Capacity IQ client view.


  • If you select the CapacityIQ virtual appliance in the inventory and navigate to the Console tab to configure time zone settings, you must restart CapacityIQ at the end of the process. To restart CapacityIQ, log in to the Status tab of the Administration Portal and click Restart.

    The CapacityIQ documentation will include this information in the next release.

  • CapacityIQ takes an hour or two to display information associated with the following events in the user interface:
    • CapacityIQ might take up to two hours after a new host is added to vCenter Server for the host to account for the addition in capacity estimates.
    • After installation, it takes 40 minutes or more for inventory information to appear in the user interface.
  • If you make changes in a cluster, such as moving a host out of the cluster and moving it back, and you create a what-if scenario, it might take two or three hours for the changes to appear in the what-if scenario.
  • If a dashboard or view is open for more than an hour, the information might become outdated.

    Workaround: Click the selected object in the inventory panel to get the latest data.

  • Rendering time for certain views might be slow.

    This might happen when you select a cluster in the inventory panel, or when the selected object contains over 500 virtual machines. In these cases, the following views can take up to a minute to render in the user interface:

    • Powered-Off Virtual Machines
    • Idle Virtual Machines
    • Oversized Virtual Machines

    These views are available in report form on the Reports tab. CapacityIQ can start and process these reports in the background.

  • When the vCenter Server is down, the License or Status tabs in CapacityIQ might take some time to update information.

System Load

  • When CapacityIQ experiences a heavy system load or high network latency, inventory objects for CapacityIQ might appear multiple times in the navigation tree.

    Workaround: Right-click the page and select Refresh.

  • When CapacityIQ experiences a severe load on the system, an error message might appear about the connection with the vCenter Server system even when the connection exists.

    Workaround: Right-click the page and select Refresh. If the refresh operation does not resolve the issue, adjust the load on the system.

  • When a cluster has 400 virtual machines or more, an Internet Explorer warning might appear when you expand the cluster. The warning asks you if you want to abort the running script.

    Workaround: Click No to run the script.


  • When you select the table format for the Capacity Efficiency - Trend view, the value in the Average Powered-On Hosts column shows a powered-on host count that is based on the current snapshot rather than the correct average of powered-on hosts in a selected timeframe.

    Workaround: If the Capacity and Trend Analysis global settings page shows the Use last known capacity per interval rule in use, change the rule to Use average capacity per interval.

  • CapacityIQ metrics assume that orphaned virtual machines are powered off virtual machines.
  • The data in the pie chart on the Common Virtual Machine Configurations - Distribution view might not appear properly if you change the Capacity Calculation Rules in Capacity and Trend Analysis global settings. The default Capacity Calculation Rules setting is Use last known capacity per interval. If you change the setting to Use average capacity per interval, the pie chart might exclude some data. The information that does appear includes the counts of the unique virtual machine configurations observed within the analysis period, rather than the average or last known configurations.
  • In the Determine Virtual Machine Capacity Usage-Trend view, the CPU Limit trending line can show a greater value than the Configured CPU trending line.

    This information might seem inaccurate, but the CPU limit can be higher than the configured CPU. CapacityIQ calculates configured CPU as vCPU count x host CPU speed per core.

  • Numbers for memory consumed are slightly higher than the numbers reported by vCenter Server. On the Dashboard and on the Virtual Machine Capacity Usage - Trend view of a virtual machine page, the numbers of memory consumed are slightly higher than the numbers reported by vCenter Server. This occurs because CapacityIQ adds ESX memory overhead to the consumed memory number for the virtual machine.

    This issue affects the numbers on the following pages:

    • Dashboard
      • VM Memory Consumed - this number is slightly higher because CapacityIQ adds ESX memory overhead.
      • Total VM Memory Remaining - this number is slightly lower because CapacityIQ subtracts ESX memory overhead.
    • Virtual Machine Capacity Usage - Trend view
      • VM Memory Consumed - this number is slightly higher because CapacityIQ adds ESX memory overhead.

User Interface

  • The CapacityIQ plug-in does not load properly in the vSphere Client.

    Workaround: If you have high security settings in Internet Explorer, select Tools > Internet Options, select the Security tab, and lower the security settings for untrusted servers.

  • When you enable Fault Tolerance (FT) on a virtual machine, the primary and secondary virtual machines appear with the same name in the navigation tree.
  • When you remove a host or virtual machine, the data that CapacityIQ collects before the removal cannot be reconciled with the data that CapacityIQ collects after you add the host or virtual machine back to the datacenter.

    Workaround: Disconnect and reconnect the virtual machine or host.

  • On the Virtual Machine Capacity - Summary view, you might see values, such as Time Remaining > 1 year, even when the Total Capacity, Avg. Deployed, and Remaining values are null.

    This occurs only within the first two hours after the addition of an object.

  • Trend views might mishandle the display of information on the view page. If you use a computer with the screen resolution set smaller than 1024 x 768, the text string that appears below the Data Window bar might be truncated.

    Workaround: Change the screen resolution to a higher resolution when working with trend views.

  • What-if analysis cannot occur on a new standalone host that the vSphere Client is still adding to the inventory.

    Workaround: Links for applying what-if scenarios to the host, either in the dashboard or in views, do not appear until an hour or two after the host is added to the vSphere Client.

  • If you select Combine Scenarios or Compare Scenarios while a what-if scenario is applied, CapacityIQ does not apply the scenario to the view.

    Workaround: Wait for the scenario application to complete before you select the options.

  • If CapacityIQ performs a shutdown that is not initiated through the ciq-admin command-line interface, the Administration Portal might not indicate that the connection status is disconnected.

    Workaround: Restart CapacityIQ and check the status.

  • When you select objects in the inventory panel, the objects might inaccurately appear to have child objects.

    The following object types might display this issue:

    • Hosts and clusters with only folders
    • A datacenter with only folders
    • A cluster with only resource pools
    • A host with only resource pools
  • If you create an empty folder under All Datacenters, and attempt to expand All Datacenters in Capacity IQ, you see a Loading... indicator.

    Workaround: Press F5 to refresh CapacityIQ.

  • When you apply a what-if scenario with CPU and memory utilization values that include decimal points, CapacityIQ does not round the values to whole numbers.

    Workaround: Use whole numbers for CPU and memory utilization values.

  • On some CapacityIQ pages, the client shows an Error loading view message. CapacityIQ uses an Internet Explorer browser control for rendering its pages. This message might appear after upgrading CapacityIQ and the Internet Explorer cache is full.

    Workaround: Clear the Internet Explorer cache. See Microsoft knowledge base article 260897 for instructions. If the problem persists after clearing the cache, contact VMware technical support.

  • The wrong start time appears in the slider if you select a different time zone for the interval range start date. If the current time is Standard Time (non-Daylight Savings Time), and you select Daylight Savings Time for the interval range start date, the slider displays the wrong start time (non-Daylight Savings Time) when CapacityIQ reloads the data. The correct requested interval range appears in the view, but not in the slider. The start time appears as one interval before the actual requested start date.

    Workaround: Set the start date to the correct date before updating the interval range for the view.

Top of Page

Resolved Issues

The 1.0.4 release resolves the following upgrade and licensing issues.

  • If you upgrade vCenter Server and CapacityIQ, the CapacityIQ plug-in might disappear from the vSphere Client. The Plug-in Manager of the vSphere Client displays a connection failure with CapacityIQ.

    Workaround: From the Setup tab of the CapacityIQ Administration Portal, click Unregister, click Register, type the credentials for the vCenter Server system to which CapacityIQ connects, and click Apply.

  • When a CapacityIQ license expires, you cannot update the license because the License key text box does not appear in the Administration Portal.

    Workaround: Use an SSH client to log in to the CapacityIQ virtual appliance as the ciqadmin user, and type the ciq-admin license add --key <license_key> command.

Top of Page