Home > Blogs > Support Insider > Monthly Archives: July 2010

Monthly Archives: July 2010

Scheduled Maintenance July 31

VMware will be performing a system upgrade to several VMware Web applications on July 31, 2010. Maintenance will begin at 12:01 PM Pacific Time and end July 31, 2010 at approximately 03:00 PM Pacific Time.

While this upgrade is in progress, you will be unable to:

  • Access or manage your VMware account
  • Submit support requests online 
  • Download, purchase or register VMware products Manage VMware product licenses.
  • Access to VMware Communities

If you need to file a support request while the upgrade is in progress, call VMware Technical Support for assistance.

We appreciate your patience during this maintenance period. These system upgrades are part of our commitment to continued service improvements and will help VMware better serve your needs.

VMware View Support with vCenter/vSphere 4.1

With the recent release of VMware vSphere 4.1 and VMware vCenter 4.1 we wanted to clarify support for these platforms with the current shipping versions of VMware View.

As hardware vendors continue to improve processor hardware, VMware is taking steps to improve the performance and utilization of this hardware. As such, we have moved to a 64-bit architecture for vSphere 4.1. View 4.5 will be the first version of View to support this new architecture, so customers should plan their upgrade paths accordingly.

Please note that View Composer is the only component of View which will not run on vSphere’s 64-bit architecture. Customers who are not using Composer should be fine to upgrade. Support for vSphere 4.1 and vCenter 4.1 are planned with upcoming version of VMware View including View 4.5.

Additional information about View compatibility with vSphere 4.1 and vCenter 4.1 can be found in the Knowledge Base Article: vSphere support for View Manager 1011292

Customers can also refer to the vSphere Compatibility Matrix: http://www.vmware.com/resources/compatibility/docs/vSphere_Comp_Matrix.pdf

View compatibility information can also be found in the View Manager Administrative Guide: http://www.vmware.com/support/pubs/view_pubs.html

VMworld is approaching quickly

If you’ve been procrastinating in getting yourself registered for VMworld this summer in San Francisco here is your friendly reminder. This year’s VMworld 2010 is being held in San Francisco August 30 through September 2. At the conference you can participate in hundreds of Breakout Sessions and cutting-edge Hands-on-Labs that don’t require pre-registration.

The ever popular Genius Bar returns this year where you can sit and have a face to face chat with various experts. From our own team, Rick Blythe and Kevin Mitts will be demonstrating our new Social Support initiatives including KBTV, the Knowledge Base, and more. Register now.

Register Now

How to upgrade to VMware vCenter Server 4.1 using the Data Migration tool

Our first video covering vSphere 4.1 is now live. The video compliments KB article 1022137 vSphere 4.1 upgrade pre-installation requirements and considerations. and describes the process for using our Data Migration tool to upgrade VMware vCenter Server 4.1

VMware vCenter 4.1 is part of the VMware vSphere 4.1 product suite and the Data Migration tool allows you to migrate your vCenter Server 4.0 configuration, since VMware has now entirely gone to a 64-bit platform. 64-bit brings significant performance benefits, but it also introduces some challenges that need to be considered before upgrading.

Sit back, grab that cup of java and take in a little KBTV.

How to upgrade to VMware vCenter Server 4.1 using the Data Migration tool

 

The Data Migration tool is provided with your vCenter Server 4.1 installation media.

New articles published for week ending 7/24/2010

VMware Consolidated Backup
Order of tasks in a VMware Consolidated Backup snapshot operation (1008163)
Date Published: 7/21/2010
vcbMounter fails with the error: Cannot create directory (1009564)
Date Published: 7/21/2010

VMware ESX
Opening virtual machine console fails with the error: The server actively refused the connection (1005534)
Date Published: 7/22/2010
ESX host’s UUID is not unique (1006250)
Date Published: 7/21/2010
Creating and removing snapshots fails with the errors: "Invalid arguments" and "File exists" (1008202)
Date Published: 7/21/2010
Applying the host profiles on an HP box with 10G NetXen fails with the error: msg = "Error during the configuration of the host: Input/output error: Input/output error" (1014373)
Date Published: 7/20/2010
Cannot add an ESX host to Cisco Nexus 1000V Distributed Virtual Switch (1018241)
Date Published: 7/19/2010
Restarting an ESX 4.0 Update 2 host causes a loss of network connectivity on a vDS switch configured with Intel 10GB uplinks (1024187)
Date Published: 7/19/2010
Cannot access a virtual machine console with vCenter Server WebAccess (1023870)
Date Published: 7/19/2010
ESX 4.1 root passwords are authenticated up to only 8 characters (1024500)
Date Published: 7/19/2010

VMware ESXi
ESXi 4.0 does not include RPM format for VMware Tools (1024047)
Date Published: 7/19/2010
Storage Virtual Appliance (SVA) hangs if it presents LUNs to the ESX host on which it is running (1022580)
Date Published: 7/20/2010
"WARNING: vmklinux26: SCSILinuxQueueCommand:" logged twice a second after upgrading from ESXi 4.0 Update 1 to ESXi 4.0 Update 2 (1024878)
Date Published: 7/23/2010
You might not be able to upgrade ESX/ESXi 4.0 hosts with installed Cisco Nexus 1000V to ESX/ESXi 4.1 (1024641)
Date Published: 7/22/2010

VMware Fusion
Checking physical memory (RAM) on a Mac for VMware Fusion (1021740)
Date Published: 7/23/2010
Cannot power on a Fusion virtual machine due to insufficient disk space (1024198)
Date Published: 7/20/2010

VMware Service Manager
Screen changes made in VMware Service Manager 8.x Screen Designer does not take effect in a Windows 2008 server (1024164)
Date Published: 7/19/2010
Using IPK Notification workflow rules on Call Suspension (1024428)
Date Published: 7/22/2010
Tabs in a collapsible section are not hidden when the section is collapsed (1024432)
Date Published: 7/22/2010
Resources that are not scanned are incorrectly deleted in VMware Service Manager 9.x (1024826)
Date Published: 7/23/2010

VMware vCenter Configuration Manager
Updating Server Advisor content for Unix manually (1024251)
Date Published: 7/19/2010
Unix Agent Upgrade via Remote Command fails with the error: ECMU Enable Remote Command Advanced Parameters does not exist (1024467)
Date Published: 7/20/2010
Incomplete jobs in Job Manager do not get cleared (1024774)
Date Published: 7/22/2010
Viewing Dashboards and SRS reports from a client computer fails with the error: Object reference not set to an instance of an object (1024799)
Date Published: 7/22/2010

VMware vCenter Server
Stateless event alarms repeatedly trigger actions that are set to run only once (1023144)
Date Published: 7/23/2010
vCenter Server 4.1 Data Migration Tool fails with the error: HResult 0x2, Level 16, State 1 (1024490)
Date Published: 7/20/2010
Upgrading to vCenter Server 4.1 fails when the installer upgrades the database (1024449)
Date Published: 7/21/2010

VMware vCenter Site Recovery Manager
Configuring the array manager in Site Recovery Manager fails (1008823)
Date Published: 7/21/2010

VMware vCenter Update Manager
Upgrade the Jetty Web server embedded in VMware vCenter Update Manager by using a security fix (1023962)
Date Published: 7/19/2010

VMware View Manager
Changing the VMware View Client connection timeout (1023347)
Date Published: 7/22/2010

VMware VirtualCenter
Using two VirtualCenter Servers with different databases on a single Oracle server fails (1024732)
Date Published: 7/23/2010

VMware Workstation
Running the vmware-config-tools.pl script on a Linux host causes a kernel error (1011984)
Date Published: 7/21/2010

Volume Purchasing Program
Volume Purchasing Program (VPP) FAQ – Affiliates (1024541)
Date Published: 7/19/2010
Volume Purchasing Program (VPP) FAQ – Online Tools and Migration (1024546)
Date Published: 7/19/2010
VMware Volume Purchasing Program (VPP) – key features and changes (1024550)
Date Published: 7/19/2010
Volume Purchasing Program (VPP) – Program Definitions and Policies (1024554)
Date Published: 7/19/2010

Questions, Questions, Questions

Mike Bean

Hello Virtual World!

I’m writing this week’s column a little early, so my fan (Hi Mom!) will have something to read next week, as I am taking a short vacation. It’s a personal tradition of mine that I never work my birthday, haven’t for many years. (I’m stubborn like that!) So the ESX systems of the world will have to keep running without my meddling for a time!

It’s one of the peculiar ironies of my life that I have a tendency to learn things too late to really make use of them. One could very easily argue that I don’t have a monopoly on that. It’s a natural by-product of aging and wisdom, and happens to everyone. More specifically, in my last job I ran a SAN reliability lab. It was my job to run 30 some odd servers engaged in more or less random read/write operations to approx 2400 hard drives. When they broke, I was expected to call the attention of the local engineering staff to the problem. Over the course of this job, I learned something. To all my friends who are engineers, I apologize, but I’m about to characterize your entire profession under a stereotype. Engineers don’t like, “it’s broke.”

Engineers like data, they like hard facts. They like information so reliable you can practically scratch a window with it. They like recorded, quantifiable statistics they can browse, copy, tweak, manipulate, reproduce and experiment with. More often than not, they like this kind of information, because it’s easy to fix, and even if they can’t fix it, it gives them something to build on. The really insidious part of all of this is the attitude is infectious. After I started this job at VMware, I realized I’d caught the virus.

It’s super common that we’ll get requests virtually every day from folks who’ve observed some sort of anomalous behavior from their servers which they must account for, and they expect our help in doing that. We do our best to provide that help when it’s asked for, and we frequently ask for diagnostic data/vm-support bundles from the affected host. In fact, I would go so far as to suggest that it’s not a bad idea to automatically include these logs with EVERY support request you send to VMware. (VMware KB 1008524) However, there seems to be a lot of common misconceptions about what it is we can actually learn from those logs, here are a few of them. (Listed in no particular order)

#1 My VM’s are behaving strangely! Check the logs please!

This is a common question, and it’s worth exploring, but it’s important to try to not put all your eggs in one basket, because ESX does not do a lot of logging at the operating system level! By and large, we concentrate on setting up the sandbox, and what the kids do within it, is their business. That’s not to say we can’t learn things about events on a VM by examining its corresponding vmware.log, but it’s important to have realistic expectations. If you find yourself in the position of having to call VMware with this question, be prepared for us to ask you some questions right back.

How precisely is it behaving strangely? How long has it been behaving strangely? What’s changed? (There is ALWAYS SOMETHING, even if we don’t yet know what). What are the characteristics of the VM? What operating system does it use? How often does it show this kind of behavior? How many VM’s are showing this behavior? (What do they have in common?)

(Wow, if any of the engineering staff from my previous job are reading this column, they’re probably laughing themselves silly right now.)

#2 There are timestamp gaps in my logs! ESX must have crashed!

This is another common one. It’s true that ESX is a prodigious logger, and under normal operating circumstances, there will never be a time when it doesn’t have something to say, but if there are gaps, you can’t necessarily assume the host was down. All that a gap proves is that the system was in a state that ESX couldn’t write to its own system files. There are multiple ways that might happen; hardware failure is the most common. I spoke with someone just this morning with substantial gaps in his logs; he’d discovered bad dimms on the host.

Gaps in the system log imply that something’s wrong with the hardware, but they don’t always PROVE it. The point is, when ESX CRASHES, you’ll know it. That’s how it was designed. You’ll get one of our famous “purple screens” (VMware KB 1006802 or KB 1009525 = examples). A purple screen is ESX’s way of saying that it’s run out of options. There are no remaining courses of action that don’t pose substantial risk of data corruption, and for obvious reasons, ESX doesn’t “roll” like that. When the system hangs, it’s reasonable to conclude that ESX can’t write to its system files. If it can’t write to system files, then it’s reasonable to assume we can’t write a crash dump either. So if you find yourself in this state, BEFORE you reboot the host (which we do understand you must do), ask yourself some fairly critical questions. After all, if you don’t ask them, we’ll probably ask you instead.

What’s the date, time, and fully qualified server name? Are there any scheduled jobs running in the environment? (such as backup jobs or batch jobs? )

  • Is the service console pingable?
  • Is VMkernel pingable?
  • Are the virtual machines pingable?
  • Can I connect to the host in a VSphere client with Virtual Center?
  • Can I connect to the host in a VSphere client without Virtual Center?
  • Can I connect to the physical console either directly, or via ILO?

If ANY of these things are true, don’t reboot right away, give us a call, we may be able to help figure out a way out!

#3 My ESXi host broke, Check the logs!

We (VMware’s technical support engineers) almost always flinch when we get these requests. I covered this in a previous blog, but it’s worth reiterating.

ESXi lives in RAMdisk!

We can certainly understand a need for urgency, and if you need to recover your systems, you may have to reboot, but you also need to understand, because ESXi does live in RAMdisk its VERY COMMON that the logs will contain NOTHING prior to the reboot. Please understand, be aware of the risk, and don’t be surprised if your technician tells you there’s nothing to retrieve. ESXi HAD to give up something to get its footprint size. Our engineers aren’t magicians; they worked hard to cram as many functions as they did into such a small memory footprint. The bottom line is some hard choices had to be made, and some of the logging and diagnostic capability didn’t make the cut. That’s why it’s that much more important to use the capabilities ESXi does have, namely, syslog and the vMA (vSphere management assistant). Trust me, if you use ESXi, put them both in your tool belt. It’ll only take ONE outage incident for an external syslog server to pay for itself. It might not happen today, or tomorrow, but someday you’ll be glad you had them.

That’s all for today, barring acts of god, the economy, VMware’s management and Prince (who apparently believes the internet is “over” http://tinyurl.com/232jyv2) I’ll see you all in a few weeks.

Live well!

New articles published for week ending 7/17/2010

VMware ESX
Downloading the license file fails (1017928)
Date Published: 7/12/2010
Cannot power on a virtual machine and you receive an Admission Check Failed error (1018180)
Date Published: 7/12/2010
Powering on virtual machines fails with the error: MAX VCPUs limit is reached (1020121)
Date Published: 7/12/2010
External I/O workload detected on shared datastore running Storage I/O (SIOC) for congestion management (1020651)
Date Published: 7/12/2010
Hot-adding memory to a Windows 7 virtual machine might causes the operating system to fail (1021319)
Date Published: 7/12/2010
VMware vSphere supports booting linux guest operating system from an paravirtual SCSI adapter (1021346)
Date Published: 7/12/2010
Configuring IPv6 with ESX and ESXi 4.1 (1021769)
Date Published: 7/12/2010
I/O Statistics in vSphere 4.1 (1021953)
Date Published: 7/12/2010
vStorage APIs for Array Integration FAQ (1021976)
Date Published: 7/12/2010
Installing ESX 4.1 and vCenter Server 4.1 best practices (1022101)
Date Published: 7/12/2010
Upgrading to ESX 4.1 and vCenter Server 4.1 best practices (1022104)
Date Published: 7/12/2010
vSphere 4.1 upgrade pre-installation requirements and considerations (1022137)
Date Published: 7/12/2010
USB support for ESX/ESXi 4.1 (1022290)
Date Published: 7/12/2010
AltGr key combinations do not work in Linux virtual machines that are remotely accessed by VMware Infrastructure Client running in a Windows RDP or VNC session (1022454)
Date Published: 7/14/2010
Using vShieldZones 1.0 with ESX 4.1 (1022536)
Date Published: 7/12/2010
Excluding a physical NIC from network resource management (1022587)
Date Published: 7/12/2010
Changes to DRS in vSphere 4.1 (1022842)
Date Published: 7/12/2010
Changes to VMware Support Options in vSphere 4.1 (1023118)
Date Published: 7/12/2010
VMware ESX and ESXi 4.1 Comparison (1023990)
Date Published: 7/12/2010
Beacon packets are sent even if the vSwitch is not configured to use Beacon Probing for Network Failover Detection (1024435)
Date Published: 7/16/2010
vSphere Client fails to differentiate between the ports of NC532m and NC532i network adapters (1018152)
Date Published: 7/13/2010
General system error occurred: Failed to create journal file providerFailed to open "/var/log/vmware/journal/1269xxxxxx.x" for write (1019598)
Date Published: 7/16/2010
VMX log file states the incorrect reason of a failure when attempts to add the same USB device to two different virtual machines fail (1021148)
Date Published: 7/12/2010
Attempts to upgrade ESX with esxupdate fail with a No Disk Space error (1021242)
Date Published: 7/12/2010
Improvements in handling thin provisioned devices (1021272)
Date Published: 7/12/2010
No ESX/ESXi support for CPU-only or memory-only NUMA nodes (1021508)
Date Published: 7/12/2010
VirtualCenter Server 2.x and vCenter Server 4.x override user-initiated changes to the resource hierarchy on hosts in a DRS cluster (1021822)
Date Published: 7/12/2010
Add CD/DVD-ROM drive operation results in a duplicate default name (1021824)
Date Published: 7/12/2010
Problem restoring free port groups on a Distributed Virtual Switch after all proxy switch ports on host are utilized (1021825)
Date Published: 7/12/2010
Error loading performance chart data when vCenter Server uses a custom SQL Server database configured with a custom JDBC port. (1021826)
Date Published: 7/12/2010
Use of large pages can cause memory to be fully allocated (1021896)
Date Published: 7/12/2010
Adding a Paravirtual SCSI adapter to a virtual machine with a SUSE Linux Enterprise Server 11 guest operating system can cause boot failure (1022738)
Date Published: 7/12/2010
Virtual Machine fails with an error: Unrecoverable Memory Allocation Failure (1023749)
Date Published: 7/15/2010
Simultaneously powering on a large number of virtual machines that use software iSCSI as the storage protocol causes some power-on failures (1024034)
Date Published: 7/12/2010
Securing Credentials in vMA 4.1 (1017669)
Date Published: 7/12/2010
ESX virtual machine monitor encounters a critical error and shuts down (1018178)
Date Published: 7/12/2010
Portgroup connectivity restored (1020374)
Date Published: 7/12/2010
dvPort connectivity restored (1020375)
Date Published: 7/12/2010
dvPort uplink redundancy restored (1020376)
Date Published: 7/12/2010
Portgroup redundancy restored (1020377)
Date Published: 7/12/2010
dvPort down with redundancy degraded (1020613)
Date Published: 7/12/2010
Duplicate IP address detected (1020647)
Date Published: 7/12/2010
Maximum supported volumes reached (1020652)
Date Published: 7/12/2010
Frequent path state changes indicate storage problem (1020692)
Date Published: 7/12/2010
Networking is turned off in a Linux virtual machine after an RPM upgrade of VMware Tools from ESX 3.5 Update 4 or earlier to ESX 4.1 (1020804)
Date Published: 7/12/2010
Change the Port Used by the vSphere Client to Connect Directly to the ESX/ESXi host (1021199)
Date Published: 7/12/2010
Supported USB device models for passthrough from an ESX or ESXi host to a virtual machine (1021345)
Date Published: 7/12/2010
A powered-off FT-enabled virtual machine is automatically powered on by VMware HA (1021589)
Date Published: 7/12/2010
Attaching a MAI KEYLOK II software protection dongle 07F2:0001 device to an external USB hub can cause devices attached to the hub to not function properly when connected to a virtual machine (1021596)
Date Published: 7/12/2010
ESX/ESXi installations on HP systems require the HP NMI driver (1021609)
Date Published: 7/12/2010
Working with firewall rules in ESX 4.x (1021779)
Date Published: 7/12/2010
Download of vSphere Client from ESX/ESXi host can fail (1021799)
Date Published: 7/12/2010
Supported encryption protocols for joining ESX/ESXi to an Active Directory server to perform user authentication (1021823)
Date Published: 7/12/2010
ESX/ESXi host using NUMA fails to start or install due to excess installed memory (1021884)
Date Published: 7/12/2010
ALUA parameters in the output of ESX/ESXi 4.1 commands (1022030)
Date Published: 7/12/2010
VMware Tools uninstall error when Linux guest operating system is removed from VMware environment (1022044)
Date Published: 7/12/2010
Troubleshooting Storage I/O Control (SIOC) (1022091)
Date Published: 7/12/2010
Number of virtual CPUs per virtual socket in ESX/ESXi 4.1 (1022289)
Date Published: 7/12/2010
Criteria for choosing a dvPort binding type (1022312)
Date Published: 7/12/2010
Name servers are removed during install when PEERDNS is set to no (1022313)
Date Published: 7/12/2010
Test (1022878)
Date Published: 7/12/2010
Accessing USB storage and other USB devices from the service console (1023976)
Date Published: 7/12/2010

VMware ESXi
Recreate vSphere 4.0 lockdown mode behavior in vSphere 4.1 (1017628)
Date Published: 7/12/2010
Configuring Round-Robin disk I/O load balancing on ESX 3.5/4.x (1017860)
Date Published: 7/12/2010
Using Tech Support Mode in ESXi 4.1 (1017910)
Date Published: 7/12/2010
Setting the congestion Threshold Value for Storage I/O Control (1019687)
Date Published: 7/12/2010
Storage device connectivity restored (1020379)
Date Published: 7/12/2010
dvPort connectivity lost due to physical link down (1020458)
Date Published: 7/12/2010
dvPort down with loss of redundancy (1020615)
Date Published: 7/12/2010
Maximum number of supported paths reached (1020654)
Date Published: 7/12/2010
Frequent PowerOn Reset Unit Attentions occur on path (1020704)
Date Published: 7/12/2010
Windows 7 or Windows 2008 guests might stop responding when FT is enabled due to E1000 driver issue (1021303)
Date Published: 7/12/2010
After vCenter Server 4.0 is upgraded to 4.0 Update 1, a managed ESXi 4.0 host becomes unmanagable due to insufficient unreserved memory on the host (1021304)
Date Published: 7/12/2010
Masking a boot device might make /bootbank unavailable on an ESXi system (1021455)
Date Published: 7/12/2010
Windows NT guest displays an incorrect amount of memory on virtual machine with hardware version 7 (1021509)
Date Published: 7/12/2010
User-configured resource settings for virtual machines might not be retained when you remove a host from a DRS cluster (1021819)
Date Published: 7/12/2010
Lockdown mode configuration after upgrading from ESXi 4.0 to 4.1 (1021935)
Date Published: 7/12/2010
PowerPath rpowermt server reports PowerPath Not Found error (1021937)
Date Published: 7/12/2010
Virtual machines backed by ephemeral/dynamic dvPort groups might lose networking when powered on as part of a host reboot (1021938)
Date Published: 7/12/2010
Overview of Active Directory integration in ESX 4.1 and ESXi 4.1 (1021970)
Date Published: 7/12/2010
Deploying ESXi 4.1 using the Scripted Install feature (1022263)
Date Published: 7/12/2010
Avocent ACS6000 Virtual Serial Port Concentrator (1022303)
Date Published: 7/12/2010
Troubleshooting ESXi 4.1 Scripted Install errors (1022308)
Date Published: 7/12/2010
Changes to vMotion in vSphere 4.1 (1022851)
Date Published: 7/12/2010
Adding a host to vDS causes a port pumber exceeded error (1022875)
Date Published: 7/12/2010
A large number of simultaneous suspend virtual machine operations cause some operations to fail (1022527)
Date Published: 7/12/2010
VMware ESXi 4.0.x Installable
VMware ESX/ESXi host logs timeout errors when trying to establish SSL connections (1020806)
Date Published: 7/12/2010
ESX/ESXi hosts that take too long to power on are marked as failing to exit standby mode by vCenter Server (1021503)
Date Published: 7/12/2010
Simultaneous access to two ESXi installations on USB flash drives causes the system to display panic messages (1021744)
Date Published: 7/12/2010
Attempting to add a host with powered-on virtual machines to an EVC-enabled cluster might fail in certain situations (1021308)
Date Published: 7/12/2010
Some vDS networking information is not available when you connect directly to a host using the vSphere Client (1021890)
Date Published: 7/12/2010
Network I/O Resource Management in vSphere 4.1 with vDS (1022585)
Date Published: 7/12/2010
Connecting a USB device through an external USB hub might occasionally generate an error (1021238)
Date Published: 7/12/2010
Enable interleaved NUMA nodes on ESX/ESXi hosts (1021454)
Date Published: 7/12/2010
Connection to the switch module is lost for all systems in a blade server configuration when one system hits a purple error screen (1021612)
Date Published: 7/12/2010
Virtual machines with more than 2TB minus 512B of RDM disk space fail to power on after you upgrade from ESX/ESXi 3.5 to ESX/ESXi 4.0 or 4.1 (1021808)
Date Published: 7/12/2010
Upgrading ESX 4.0 to ESX 4.1 (1022140)
Date Published: 7/12/2010
Load Based Teaming in vSphere 4.1 (1022590)
Date Published: 7/12/2010
Changes to HA in vSphere 4.1 (1022843)
Date Published: 7/12/2010

VMware Fusion
Downgrading from Fusion 3 to Fusion 2 (1020246)
Date Published: 7/12/2010
Windows 7 installs in a foreign language in Fusion (1023887)
Date Published: 7/12/2010

VMware Service Manager
Attaching an object to a call without reopening the call (1024000)
Date Published: 7/14/2010

VMware vCenter Converter
Assigning startup types to Windows services on the source virtual machine (1021028)
Date Published: 7/12/2010

VMware vCenter Lab Manager
VMware vCenter Lab Manager Web Console is Blank if the VMware vCenter is Installed on the Same Machine (1020474)
Date Published: 7/15/2010

VMware vCenter Server
vCenter Server 4.1 fails to install or upgrade with the error: This installation package is not supported by this processor type (1019144)
Date Published: 7/12/2010
Guided Consolidation analysis pauses and cannot be restarted (1019242)
Date Published: 7/12/2010
VMkernel fails to set MTU on vNetwork Distributed Switch (1020617)
Date Published: 7/12/2010
Maximum number of supported devices reached (1020653)
Date Published: 7/12/2010
ESX host is unable to connect to NFS server (1020705)
Date Published: 7/12/2010
vCenter Server does not start when connecting to an Oracle database (1021194)
Date Published: 7/12/2010
vCenter Server fails to populate performance charts and displays an error message when you use custom JDBC SQL port (1021202)
Date Published: 7/12/2010
vCenter Server installation with Oracle database fails after previous failure or shutdown (1021240)
Date Published: 7/12/2010
Accented and composite characters are not displayed in the index for French-language online Help (1021569)
Date Published: 7/12/2010
Some events cannot trigger alarms (1021613)
Date Published: 7/12/2010
vSphere Client displays incorrect characters when vCenter Server is not configured to support the language locale of the vSphere client (1021614)
Date Published: 7/12/2010
Migrating to the vCenter Server 4.1 database (1021635)
Date Published: 7/12/2010
vCenter Server 4.1 network port requirements (1022256)
Date Published: 7/12/2010
Error Message When Trying to Migrate Virtual Machine with USB Devices Attached (1022359)
Date Published: 7/12/2010
A missing database index slows vCenter Server (1023977)
Date Published: 7/12/2010
Virtual machine MAC address conflicts (1024025)
Date Published: 7/12/2010
Supported vCenter Server high availability options (1024051)
Date Published: 7/16/2010
Using the Data Migration Tool to upgrade from vCenter Server 4.0 to vCenter Server 4.1 fails (1024380)
Date Published: 7/16/2010
VMware vCenter Server 4.0.x
Manually enable vSphere solutions (1021265)
Date Published: 7/12/2010
iSCSI adapters cannot establish a connection to an NetApp iSCSI storage array (1021267)
Date Published: 7/12/2010
InvalidException Error Occurs When Virtual Machine and Host Do Not Belong to the Same Distributed Virtual Switch (1021318)
Date Published: 7/12/2010
Storage device path redundancy restored (1020456)
Date Published: 7/12/2010
Frequent PowerOn Reset Unit Attentions occur on device (1020702)
Date Published: 7/12/2010
Transient failure recovery due to watchdog timeout (1020706)
Date Published: 7/12/2010
Changes to Fault Tolerance in vSphere 4.1 (1022844)
Date Published: 7/12/2010
Login to vCenter Server 4.0 Update 1 using vSphere Client 4.1 fails in Linked Mode environments when vCenter Server Update 1 and vCenter Server 4.1 use a different HttpsProxyPort (1024120)
Date Published: 7/12/2010

VMware vCenter Server Heartbeat
Performing local administration of vCenter Server Heartbeart from an account that did not perform the installation (1022867)
Date Published: 7/12/2010
Joining a vCenter Server Heartbeat instance to a Linked Mode Group and Isolating a vCenter Server Instance from a Linked Mode Group when protected by vCenter Server Heartbeat (1022869)
Date Published: 7/12/2010
Downgrading vCenter Server Heartbeat to a previous version (1022874)
Date Published: 7/12/2010
Uninstalling VMware vCenter Server Heartbeat (1022877)
Date Published: 7/12/2010
TCP Offload features on all NICs must be disabled before installing vCenter Server Heartbeat (1024066)
Date Published: 7/12/2010
Creating a static route for the VMware Channel (1023026)
Date Published: 7/12/2010

VMware vCenter Site Recovery Manager
A recovery or test recovery plan fails with virtual machines that have a pre-boot message (1021827)
Date Published: 7/12/2010
Deleted networks continue to appears in the Site Recovery Manage
r Configure Test Network dialog (1021829)

Date Published: 7/12/2010
Site Recovery Manager shadow virtual machines on the recovery site lose their vDS settings after a test failover (1021919)
Date Published: 7/12/2010
Virtual machines fail to start with a timeout error when performing a test failover (1019890)
Date Published: 7/12/2010
Network configuration of a recovered virtual machine during Site Recovery Manager failover fails with the log error: Network Device Not Found (1021491)
Date Published: 7/12/2010
Site Recovery Manager registering virtual machine task fails during failover with the error: Creating VM timeout (1021920)
Date Published: 7/12/2010
SRM 4.1 Upgrade FAQ (1024175)
Date Published: 7/14/2010
Upgrading to Site Recovery Manager 4.0 Update 1 fails with the error: can’t open perl script "e:\program": no such file or directory (1019738)
Date Published: 7/12/2010
Solution Licensing (1022178)
Date Published: 7/12/2010

VMware vCenter Update Manager
Update Manager 4.1 patch repository features (1021695)
Date Published: 7/12/2010
Manually upgrade the Jetty Web server embedded in VMware vCenter Update Manager (1023594)
Date Published: 7/12/2010

entia non sunt multiplicanda praeter necessitatem

Another post from guest blogger Mike Bean. A little Latin, a little logic, and the lowly service console.

Hello virtual world!

At the risk of singing an old refrain, I was unavoidably detained from my self-imposed one blog a week schedule. Due to circumstances beyond anyone’s control, my caseload has increased by an order of magnitude. Between you and me, I think my manager’s just trying to make sure I don’t have time to write any more blogs! Jokes aside, that’s really just the nature of the business we’re in, tech support is the information technology version of firefighting. Some days you’re playing cards in the station, next thing you know you’re hip deep in multiple five-alarms all over the county.

Can we speak candidly? Make no mistake about it, tech support kinda sucks. It’s very high stress, very high turnover rate, and generally fairly unappreciated. My intent here is not to solicit sympathy, but rather to paint an accurate picture. So why does anyone take the job?

Personally I tend to think it does have some advantages. It keeps the mind nimble. I can say with complete sincerity, that VERY RARELY do I leave the apartment with any real expectation of what the day has in store for me. More than once a customer has asked me, “So, have you ever seen anything like this?” Usually this is right about the time I’m frowning at my monitor with cartoon question marks spawning from my head. You really never know how the day will end. True story, one minute, I was fairly proud of myself. I’d managed to make a fairly tricky diagnosis concerning a half dozen some odd VM’s shutting down the night before. The next minute, I was getting REALLY BASIC elementary level instruction in unix/linux compression from our escalation engineers! (ah, humility, my old friend, it’s like you never left me!)

Despite all this seemingly random chaos, every now and then, patterns tend to emerge. This week’s blog, is in fact, brought to you by last week’s pattern, which, as it turns out, was (drum roll)

BROKEN SERVICE CONSOLES

Ladies and gentlemen, I’m going to ask as nicely as I know how, PLEASE! Tread lightly on your service consoles! Obviously, I can’t know what ESX’s developers had in mind. Regardless, I’ll gladly make the argument that the service console is NOT INTENDED for day to day use. As I’ve alluded to in a previous column, they are a maintenance hatch. It’s unrealistic to expect our customers not to use them, but, please, have the clear understanding that there-is-no nested maintenance hatch, within the maintenance hatch! I met one gentleman this week whose security department had pushed out untested authentication files to his ESX service consoles, effectively breaking the root user! (I’m still a little foggy on how we fixed that one, but I think it involved several sacred rites and sacrifices to the Aztec sun gods!)

The fact is, everyday at VMware, people care A LOT about stability, and they work hard to ensure that, BUT our QA department can’t test every possible package combination for compatibility and long term stability. It’s not realistically possible. So consider please, a possible rule of thumb. If you’re thinking about adding packages to your service console that weren’t there natively, please automatically assume that you’re adding a package VMware has NOT TESTED. There may be cases where that’s not true, but I think you’ll find it’s far more accurate as a rule then an exception.

I can recall a marathon session with a customer whose hosts weren’t making it more then 3 or 4 hours without crashing. Through old fashioned, traditional logic & process of elimination we narrowed it down a third party package on his consoles. When I followed up on the case several days later, he explained the software had been pushing out some sort of faulty active directory policy that was finally isolated as the source of the crashes!

entia non sunt multiplicanda praeter necessitatem

Occam In case my readers don’t speak Latin, I won’t make you guess what that means, if you recognize it, more power to you! It’s commonly known as Occam’s razor. "Entities must not be multiplied beyond necessity", or the more common interpretation = “the simplest explanation is usually the correct one.” Occam has all sorts of applications. It’s a 14th century logic principle, that’s considered a scientific guideline by some, a mathematics principle by others, and a philosophy rule by crazy tech support engineers, (like myself). My co-workers can testify to this, I actually wrote it on the whiteboard in my cubicle, as a reminder to myself.

By and large, we’ll leave philosophy to the philosophers, but I would suggest to you now that Occam is an EXCELLENT principle to follow when it comes to modifications of the service console. If, by any circumstance, the service console is completely unrecoverable, there is NO option but reinstallation. I ALWAYS encourage caution. The less you modify your console the better, and if you MUST modify it, FOLLOW Occam and do so only with the greatest of care. The simpler you keep your configuration, the more reliable the host will be, and the better the chances it’ll be there when you need it!

Live well!

Useful vSphere 4.1 Knowledgebase Articles

We’ve noticed a few blogs (such as this one) advertising lists of our recent Knowledgebase articles pertaining to the release of vSphere 4.1

We thought a comprehensive list would be great idea.  Here is every KB article posted for the vSphere 4.1 release.

http://kb.vmware.com/kb/1023163 Installing a VMware Service Manager license
http://kb.vmware.com/kb/1017910 Using Tech Support Mode in ESXi 4.1
http://kb.vmware.com/kb/1017928 Downloading the license file fails
http://kb.vmware.com/kb/1018178 ESX virtual machine monitor encounters a critical error and shuts down
http://kb.vmware.com/kb/1018180 Cannot power on a virtual machine and you receive an Admission Check Failed error
http://kb.vmware.com/kb/1018181 Attempting to remove a host from the inventory when it is connected to vDS generates an error
http://kb.vmware.com/kb/1018183 vSphere 4 license expires and you cannot register your product
http://kb.vmware.com/kb/1019144 vCenter Server 4.1 fails to install or upgrade with the error: This installation package is not supported by this processor type
http://kb.vmware.com/kb/1019738 Upgrading to Site Recovery Manager 4.0 Update 1 fails with the error: can’t open perl script "e:\program": no such file or directory
http://kb.vmware.com/kb/1019890 Virtual machines fail to start with a timeout error when performing a test failover
http://kb.vmware.com/kb/1020121 Powering on virtual machines fails with the error: MAX VCPUs limit is reached
http://kb.vmware.com/kb/1021491 Network configuration of a recovered virtual machine during Site Recovery Manager failover fails with the log error: Network Device Not Found
http://kb.vmware.com/kb/1021635 Migrating to the vCenter Server 4.1 database
http://kb.vmware.com/kb/1021695 Update Manager 4.1 patch repository features
http://kb.vmware.com/kb/1021769 Configuring  IPv6 with ESX and ESXi 4.1
http://kb.vmware.com/kb/1021779 Working with firewall rules in ESX 4.x
http://kb.vmware.com/kb/1021801 Location of ESXi log files
http://kb.vmware.com/kb/1021806 Location of log files for VMware products
http://kb.vmware.com/kb/1021827 A recovery or test recovery plan fails with virtual machines that have a pre-boot message
http://kb.vmware.com/kb/1021829 Deleted networks continue to appears in the Site Recovery Manager Configure Test Network dialog
http://kb.vmware.com/kb/1021919 Site Recovery Manager shadow virtual machines on the recovery site lose their vDS settings after a test failover
http://kb.vmware.com/kb/1021953 I/O Statistics in vSphere 4.1
http://kb.vmware.com/kb/1021970 Overview of Active Directory integration in ESX 4.1 and ESXi 4.1
http://kb.vmware.com/kb/1021976 vStorage APIs for Array Integration FAQ
http://kb.vmware.com/kb/1022030 ALUA parameters in the output of ESX/ESXi 4.1 commands
http://kb.vmware.com/kb/1022077 Support for the scsi_device_reprobe() API in VMKLinux in ESX 4.0 and 4.1
http://kb.vmware.com/kb/1022101 Installing ESX 4.1 and vCenter Server 4.1 best practices
http://kb.vmware.com/kb/1022104 Upgrading to ESX 4.1 and vCenter Server 4.1 best practices
http://kb.vmware.com/kb/1022137 vSphere 4.1 upgrade pre-installation requirements and considerations
http://kb.vmware.com/kb/1022140 Upgrading ESX 4.0 to ESX 4.1
http://kb.vmware.com/kb/1022178 Solution Licensing
http://kb.vmware.com/kb/1022256 vCenter Server 4.1 network port requirements
http://kb.vmware.com/kb/1022263 Deploying ESXi 4.1 using the Scripted Install feature
http://kb.vmware.com/kb/1022289 Changing the number of virtual CPUs per virtual socket in ESX/ESXi 4.1
http://kb.vmware.com/kb/1022290 USB support for ESX/ESXi 4.1
http://kb.vmware.com/kb/1022303 Avocent ACS6000 Virtual Serial Port Concentrator
http://kb.vmware.com/kb/1022308 Troubleshooting ESXi 4.1 Scripted Install errors
http://kb.vmware.com/kb/1022536 Using vShieldZones 1.0 with ESX 4.1
http://kb.vmware.com/kb/1022585 Network I/O Resource Management in vSphere 4.1 with vDS
http://kb.vmware.com/kb/1022587 Excluding a physical NIC from network resource management
http://kb.vmware.com/kb/1022590 Load Based Teaming in vSphere 4.1
http://kb.vmware.com/kb/1022842 Changes to DRS in vSphere 4.1
http://kb.vmware.com/kb/1022843 Changes to VMware High Availability in vSphere 4.1
http://kb.vmware.com/kb/1022844 Changes to Fault Tolerance in vSphere 4.1
http://kb.vmware.com/kb/1022851 Changes to vMotion in vSphere 4.1
http://kb.vmware.com/kb/1022867 Performing local administration of vCenter Server Heartbeart from an account that did not perform the installation
http://kb.vmware.com/kb/1022869 Joining a vCenter Server Heartbeat instance to a Linked Mode Group and Isolating a vCenter Server Instance from a Linked Mode Group when protected by vCenter Server Heartbeat
http://kb.vmware.com/kb/1022874 Downgrading vCenter Server Heartbeat to a previous version
http://kb.vmware.com/kb/1022877 Uninstalling VMware vCenter Server Heartbeat
http://kb.vmware.com/kb/1023026 Creating a static route for the VMware Channel
http://kb.vmware.com/kb/1023118 Changes to VMware Support Options in vSphere 4.1
http://kb.vmware.com/kb/1024066 TCP Offload features on all NICs must be disabled before insta
lling vCenter Server Heartbeat
http://kb.vmware.com/kb/1021920 Site Recovery Manager registering virtual machine task fails during failover with the error: Creating VM timeout
http://kb.vmware.com/kb/1022091 Troubleshooting Storage I/O Control
http://kb.vmware.com/kb/1023990 VMware ESX and ESXi 4.1 Comparison

VMware ALERT: VMware View Composer 2.0.x is not supported in a vSphere vCenter Server 4.1

There is an issue that prevents View Composer from working with vSphere 4.1 that customers need to be aware of. View Composer will not run on a 64-bit OS, and vSphere 4.1 only supports 64-bit OS’s. The release notes don't mention this and refers users to the VMware View Support page for compatibility information.

The Knowledgebase Team has prepared KB article: vSphere support for View Manager (1011292), and an alert has been placed on the View Support page to alert customers of this issue.

This Knowledge Base article will be updated if new information becomes available. If you have been affected by this, please read the KB.

We apologize for any inconvenience this may have caused you. If you know how to spread the word to your friends and colleagues, please do so.