Posted by Brian on Jun 10, 2010 in VMware, vCenter Server, vSphere | View Comments
Hot off the presses! The latest update for VMware vSphere is now available for download. Both Update 2 for ESX 4.0, ESXi 4.0 and vCenter 4.0 are all available now. Run don’t walk to your nearest PC with a fast connection and start downloading. Ok don’t run you might crash into something. Have fun playing with the latest update in your labs. You can download the latest version here.
Here are some of the release notes for ESX 4.0 U2, see full list here.
- Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
- Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
- Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
- Enhancement of the esxtop/resxtop utility— vSphere 4.0 Update 2 includes an enhancement of the performance monitoring utilities, esxtop and resxtop. The esxtop/resxtop utilities now provide visibility into the performance of NFS datastores in that they display the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s(guest latency).
- Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04.
Here are some of the release notes for ESX 4.0 U2, see full list here.
- Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
- Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
- Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
- Enhancement of the resxtop utility— vSphere 4.0 U2 includes an enhancement of the performance monitoring utility, resxtop. The resxtop utility now provides visibility into the performance of NFS datastores in that it displays the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s (guest latency).
- Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04.
Here are some of the release notes for vCenter 4.0 U2, see full list here.
- Guest Operating System Customization Improvements: vCenter Server now supports customization of the following guest operating systems:
- Windows XP Professional SP2 (x64) serviced by Windows Server 2003 SP2
- SLES 11 (x32 and x64)
- SLES 10 SP3 (x32 and x64)
- RHEL 5.5 Server Platform (x32 and x64)
- RHEL 5.4 Server Platform (x32 and x64)
- RHEL 4.8 Server Platform (x32 and 64)
- Debian 5.0 (x32 and x64)
- Debian 5.0 R1 (x32 and x64)
- Debian 5.0 R2 (x32 and x64)
read more
Posted by Brian on Jun 10, 2010 in VMware | View Comments
Well I knew this day would come eventually, we had run out of space on this HP MSA. I knew going into this small project but this is the direction that the team took. So we purchased another 2 TB of space and I needed to add it to the configuration. We ended up buying 6 450 GB SATA disks to use in the MSA 2312sa unit. The drives were used to create one vDisk with just over 2 TB of usable space that was split up into 2 Datastores in VMware.
The configuration was a breeze just like the initial setup. The disks were placed evenly across the disk shelves and appeared into the console as expected. A couple of clicks later I had a vDisk setup and then created to volumes and assigned them to my hosts once I had created the Datastores from the first Host.
If you need to know more about how to setup these you can read my initial post on how to setup a HP MSA 2300 series array here.
read more
Posted by Brian on Jun 9, 2010 in VMware, vSphere | View Comments
Just announced today VMware and Novell are partnering up on SUSE adoption and support. By having a valid support agreement with VMware and a qualifying purchase you can gain access to use SUSE Linux in your data center. This really cuts out the licensing worries that larger accounts may have had around using SUSE.
The other important part of the partnership is that VMware will now start using SUSE for their appliance machines that are released. In the past they have mostly used CentOS.
You can read a public copy of the news release here.
You can see the official VMware announcement here. Also have a look at the qualified sku’s here.
Personally this is funny timing since we just got a large client to create their first couple of Linux virtual machines. They just happened to also be SUSE machines.
read more
Posted by Brian on Jun 3, 2010 in Troubleshooting, VMware, vCenter Server | View Comments
While I was upgrading my vCenter server to Server 2008 I came across the following issue. I was trying to install VMware License Server on a Window Server 2008 32bit server and the install would fail saying it cannot start system services. After checking to make sure that I had not made some dumb mistake with my account I hit the intertubes and found that others had the same issue.
I was able to get pass this issue by downloading the latest copy of Virtual Center server 2.5 update 6 and then extracting the License server install file from the VPX folder. Seems that the copy from the install .iso file is newer than the file available for direct downloading. Maybe VMware can fix this soon. I did not try it but according to some other posts the version in VC 2.5 U5 might also work. Once I installed this version it worked the first time.
Error 1920.Service VMware License Server failed to start. Verify that you have sufficient privileges to start system services.
read more
Posted by Brian on Jun 2, 2010 in Labs, Tools, VMware | View Comments
The VGC is probably my personal favorite from VMware Labs so far. It is a simple but powerful utility with some cool features you don’t get with the standard vSphere client. I wrote about VMware guest console in the past covering its basic features that you can read here. Listed below are the latest features to be added or updated to this little Gem. You can have a look at VMware labs and download VGC for yourself here.
- Performance & Scalability -
- VM retrieval is enhanced to discover VMs in much lesser time.
- VGC can manage up to 315 Powered On VMs on all connected servers. Number of VMs retrieved from a server will be limited once this limit is reached.
- Support for 64 bit Windows has been added.
- Remote Console feature has been extended to work with VMs hosted on vCenter.
- Workspace files created with this version of VGC will be encrypted. However, workspace files created using earlier versions are not compatible with this release.
- VM Templates are differentiated from regular VMs.
- Workspace files can now be loaded in VGC by double clicking the .vgc files.
read more
Posted by Brian on Jun 2, 2010 in Troubleshooting, VMware | View Comments
Whether your tracking down an issue on your own or collection data to submit a support request to VMware your gonna need to round up the necessary log files. I have collected and listed some of the main log locations from VMware and also linked to KB articles covering a full list of log file locations.
VMware ESX log files
- From the Service Console
- From the vSphere Client connected directly to the ESX host (click Home > Administration > System Logs)
- From the VMware Infrastructure Client connected directly to the ESX host (click Administration > System Logs)
The vmkernel logs (which log everything related to the kernel/core of the ESX) are located at /var/log/vmkernel.
The vmkwarning logs (which log warnings from the vmkernel) are located at /var/log/vmkwarning.
The vmksummary logs (which provide a summary of system activities such as uptime, downtime, reasons for downtime) are located at /var/log/vmksummary.
The hostd log (which is the log of the ESX management service of the ESX) are located at /var/log/vmware/hostd.log.
The messages log (which log activity on the Service Console operating system) is located at /var/log/messages.
The VirtualCenter Agent log is located at /var/log/vmware/vmware/vpx/vpxa.log.
The Automatic Availability Manager (AAM) logs are located at /var/log/vmware/aam/vmware_<hostname>-xxx.log.
The SW iSCSI logs are located at /var/log/vmkiscsid.log.
The System boot log is located at /var/log/boot-logs/sysboot.log.
The vmkernel, vmkwarning, and hostd logs are located at /var/log/messages.
The Host Management service (hostd = Host daemon) log is located at /var/log/vmware/hostd.log\.
The VirtualCenter Agent log is located at /var/log/vmware/vmware/vpx/vpxa.log.
The System boot log is located at /var/log/sysboot.log.
The Automatic Availability Manager (AAM) logs are located at /var/log/vmware/aam/vmware_<hostname>-xxx.log.
vCenter log files – (KB Article)
The SRM configuration files are located at:
- C:\Program Files\VMware\VMware Site Recovery Manager\config\extension.xml
- C:\Program Files\VMware\VMware Site Recovery Manager\config\vmware-dr.xmlOr
- C:\Program Files\VMware\VMware vCenter Site Recovery Manager\config\extension.xml
- C:\Program Files\VMware\VMware vCenter Site Recovery Manager\config\vmware-dr.xml
The SRM Logs (on vCenter Server for connection with SRM and on SRM for SRM workflow) are located at:
- %ALLUSERSPROFILE%\VMware\VMware Site Recovery Manager\Logs, which translates by default to C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\LogsOr
- %ALLUSERSPROFILE%\VMware\VMware vCenter Site Recovery Manager\Logs, which translates by default to C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Site Recovery Manager\Logs
The SRM Installation Logs (on the SRM Server, which may not be the vCenter Server) are located at C:\Documents and Settings\Administrator\Local Settings\Temp\1.
The location of the SRA Logs (on the SRM server) depends on the SRA type and vendor. They may be located in:
- C:\Program Files\VMware\VMware vCenter Site Recovery Manager\scripts\SAN\*\logOr
- C:\Program Files\<SRA Vendor or Name>\
read more
Posted by Brian on May 28, 2010 in Troubleshooting, VMware | View Comments
I found a recent VMware KB article about FT and some common reasons that it might fail to start. The article goes on to explain some reasons why FT options might be greyed out, disabled or you cannot turn on Fault Tolerance. It also talks about requirements that must be met to enable FT. See the full article here.
VMware article that explains Fault Tolerance and what it can do. VMware KB
read more
