We learned today of a particular set of circumstances which, when updating to Update 1, can lead to PSODs (purple screens). 3rd party agents are a key component of this problem.
To avoid this potentially nasty problem please read the following Knowledgebase article for details:
Upgrading ESX 4.0 to 4.0 U1 using Update Manager fails or times out and rebooting host results in a purple diagnostic screen (1016070)
Note: This KB continues to be updated. Re-visit page for latest information.
When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1, you may experience the following symptoms:
- Update manager (VUM) upgrade operation fails or times out at 33%.
- Upon reboot, the host that was being upgraded displays a purple diagnostic screen with the following error:
COS Panic: Int3 @ mp_register_ioapic
Here’s a new KB that covers a very common question, and relates to a number of different VMware products as well. The question I’m referring to is: What ports does my VMware software require for management?
TCP and UDP Ports for vCenter Server, ESX hosts, and other network components management access discusses all of the network services and the ports and protocols used by all of the these products:
||Services and agents commonly present in a vSphere environment
VMware Consolidated Backup
VMware Data Recovery
VMware View Manager
VMware Virtual Desktop Manager
VMware vCenter Lab Manager
VMware vCenter Orchestrator
VMware vCenter Server
VMware vCenter Site Recovery Manager
VMware vCenter Stage Manager
VMware vCenter Update Manager
CIM HTTP server (insecure service)
CIM HTTPS server
FTP client (insecure service)
FTP server (insecure service)
iSCSI software client
NFS client (insecure service)
NFS server (insecure service)
SMB client (insecure service)
Telnet client (insecure service)Telnet server (insecure service)
Other supported management agents that you install
The KB provides a comprehensive table of ports/protocols for products going back several versions. The table includes Product, Port, Protocol, Source, Target, and Purpose. A great one to bookmark for future reference.
In case you didn’t notice, Update 1 for VMware vCenter Server 4.0 was released last week. This is great news for all of you who wish to run the vSphere client on Windows 7 machines.
While we had a KB article (Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2 (1011329)) which went through a couple of different incarnations as new information became available, we can now put this problem behind us. No work-arounds are necessary, it just works now.
Here’s a quote from the release notes:
Windows 7 and Windows 2008 R2 support — This release adds support for 32-bit and 64-bit versions of Windows 7 as well as 64-bit Windows 2008 R2 as guest operating system platforms. In addition, the vSphere Client is now supported and can be installed on a Windows 7 platform.
We highly recommend reading the entire set of release notes, they contain valuable information.
One aspect of virtual machines that often leads to confusion is the snapshot. What is a snapshot? How do snapshots work? What products use the snapshot feature? What files are involved in snapshots?
These questions and more are all discussed in the new Knowledgebase article: Understanding virtual machine snapshots in VMware ESX. This is a fairly big topic so many links are provided to other relevant information.
Ever Since Windows 7 has come out we’ve been seeing a lot of customer interest in running the vSphere Client on it. The same goes for Windows 2008 R2. The trouble is, Microsoft changed the .Net loading mechanism in these releases, breaking our vSphere Client.
We have just posted a Knowledgebase article which outlines how to deal with this change and make the client work.
One caveat: watch for the warning that one of the workarounds is not officially supported.
Read: Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2 (1011329).