No more space for the redo log error when attempting to start a virtual machine (1002103)
When starting a virtual machine, a dialog appears stating there is no more space for the redo log, and prompts you to retry or abort. The datastore in which the…
Update Manager fails when performing a scan (1006544)
· Unable to scan any ESX hosts using Update Manager · VMware Infrastructure Client produces the following error: Update Manager Had a Failure · The failure occurs with any baseline attached to…
VMware SQL Server Plug-in Automatic Filter Discovery (1009519)
This article provides information about how VMware SQL Server Plug-in for Microsoft SQL Server discovers new information during normal operation. Database structure in Microsoft SQL…
VMware VirtualCenter Server service does not start (1008114)
· VMware VirtualCenter Server service starts, then fails immediately. · The vpxd logs contain the following error message: [2009-01-05 19:36:37.130 'App' 12216 verbose]…
The VMware Cost-Per-Application Calculator compares the cost of virtualizing applications on VMware Infrastructure 3 versus other commodity virtualization offerings, like Microsoft Windows Server 2008 (Hyper-V). The calculator provides an accurate and simple methodology to determine and compare the deployment costs of virtualization solutions by 1) including both software and hardware infrastructure costs and 2) accounting for number of applications that a virtualization platform can run on each sever.
By leveraging the VMware Cost-Per-Application Calculator, you will see how VMware’s superior virtualization technology enables greater cost savings while at the same time greatly improves reliability and availability across your IT infrastructure.
Pools or virtual machines remain listed in VirtualCenter after being deleted in View Manager KB Article 1007510 Updated Mar. 24, 2009
Products: VMware Virtual Desktop Manager
Product Versions: VMware View Manager 3.x
Symptoms:
A pool is deleted from disk in View Manager from View Administrator > Desktops and Pools
Some virtual machines from the deleted pool remain in VirtualCenter
In View Administrator > Desktop Sources, the virtual machine show a status of Deleting, however the objects never get deleted
Resolution:
The virtual machine may not be deleted when View Manager is unable to process the shut down command. To workaround the issue:
Manually shutdown the virtual machine and wait a few minutes. VirtualCenter automatically continues with the cleanup process and deletes the virtual machine.
If the virtual machine is deleted from VirtualCenter or you have manually deleted the virtual machine but it still appears up in Desktop Sources, the virtual machine entry must be removed from ADAM.
Warning: Editing or deleting items within ADAM may destroy existing pools in View Manager. Backup the configuration data before making any changes. For backup instructions, see http://www.vmware.com/pdf/vdm_config_data_export_import.pdf.
1. Open the ADAM editor, click Start > Programs > ADAM > ADAM ADSI Edit.
2. Right-click ADAM ADSI Edit and select Connect to.
3. Choose Distinguished name (DN) or naming context and type:
dc=vdi,dc=vmware,dc=int
4. Under OU=Servers, double-click each entry and search in Attribute > pae-DisplayName for the corresponding virtual machine name.
5. Delete the appropriate entry that contains the virtual machine name.
6. Refresh the Desktop Sources view. The virtual machine is no longer listed.
A guest post from Srinivas Krishnamurti, Director of Product Management and Market Development:
I’m very excited to share information about a new and exciting project that a few of our wonderful engineering folks have been working on – VMware vCenter Mobile Access. (Thanks BenK, Cabir, Harish!)
Did you ever get paged when you are in a meeting about some virtual machine that needed to be restarted? Or, did you ever get an alert when you are at your kid’s soccer game or at the movies that a particular server is overloaded? Actually, imagine any scenario where you need to actively manage your datacenter but you are nowhere close to a PC. Wouldn’t it be nice to act on the notification from your mobile phone? After all, we are now a generation that doesn’t leave home without a mobile phone…
Introducing VMware vCenter Mobile Access (vCMA). vCMA allows you to monitor and manage VMware Infrastructure from your mobile phone with an interface that is optimized for such devices. Specifically, it allows you to:
Search for virtual machines in your data center
Migrate virtual machines from one host to another using vMotion
Execute recovery plans using VMware Site Recovery Manager
Access Scheduled Tasks, Alarms and Events
And much more…
Instead of explaining all the capabilities, we figured it would be easier to show them in a video – you can view a demo here.
Learn to configure and deploy the Exchange 2007 Mailbox, Hub Transport, and Client Access server roles onto individual VMware virtual machines using VMware ESX 3.5 and HP ProLiant c-Class blade servers.
Introduction
The following table of VirtualCenter (VC) performance counters lists the counters with a description of their purpose. We’re still building out this page so if you want to see detail on a particular counter just post a message at the bottom of this article. I’ll update the article, as needed.
Remember, with the exception of ready time, statistic levels one and two are the only ones needed for 99% of the performance monitoring and analysis out there. Don’t spend many of your own cycles worrying about levels three and four!
Before you continue, you should know that all total count metrics reported by VC are reported over the sample window. When you’re looking at live stats, this sample window is 20 seconds. When you’re looking at archive stats, it will depend on the interval duration. That duration could be five minutes, 30 minutes, two hours, or one day.
This causes a lot of confusion when comparing esxtop results to live VC results to archived VC results. As an example, ready time might be reported as 10% in esxtop. In live VC results this amount of ready time would be reported as 2000 ms (10% of the 20s window.) In one day archive results, the same number would be reported as 30,000 ms (10% of the five minute interval duration.) All of these numbes reflect the same amount of ready time.
More information about CPU, Memory, Disk, Network and Other Statistics you can find here: http://tiny.cc/8IQFP
I recently wrapped up some testing in my lab around VMware HA; specifically, around VMware HA isolation response. My tests involved various network configurations and attempted to clearly document the behavior of VMware HA isolation response under different circumstances. I thought I’d share some of my findings here in the hopes that others would find this information useful as well. (Keep in mind that some of the stuff listed below is just common sense, but I’m including it here anyway just for completeness.)
Ensure that the vSwitch hosting the Service Console has at least two uplinks. Keep in mind that instead of leaving that second uplink primarily unused, you can place other traffic on the same vSwitch and use the “Override vSwitch failover order” option to direct traffic preferentially onto certain uplinks. (I’ll most likely post a separate blog entry about that so that I can explain that in more detail.)
Ensure that DNS is working correctly on all ESX hosts in the HA-enabled cluster. You should verify host name resolution for both short names as well as fully-qualified domain names (FQDNs). Although I’ve seen numerous recommendations to hard-code entries into /etc/hosts, this approach is difficult to manage and does not scale well. Just fix DNS instead.
Ensure that the Service Console’s default gateway responds to ping. If it does not, you’ll need to use the das.usedefaultgateway and das.isolationaddress parameters to change where VMware HA should check to see if it is isolated. Chad Sakac recently discussed these items as well, so check that entry for additional information.
CPU Scheduling Affinity options not available (1005918)
· The virtual machine is part of DRS cluster · CPU Scheduling Affinity options not available under Virtual Machine Properties > Resources > Advanced CPU According to the Basic System…