My colleague Edwin had some spare time on his hands and decided to Thinstall the VirtualCenter client. I just tested the client and it works great. Starting the client is as fast, and maybe even faster, as a normal install. Check his article on Thinstallguru.com. Let’s hope VMware will also provide a Thinstalled version soon of the client, fully supported and compatible with Wine for the Linux users. I also heard that Thinstall is busy including Wine code into the Thinstall kernel for compatibility reasons. Hope they will fix this soon.
Introduction training Application Delivery: Installation, Isolation and Virtualization
For the readers of my blog in the Benelux area:
Nowadays Application Delivery is a hot item to talk about! On monday 28 january 2008 Ictivity Training starts with the first introduction training: “The facts about Application Delivery”.In this training different products like Microsoft Application Virtualization (SoftGrid), Citrix Application Streaming Feature and Thinstall VS will be compared to each other.
The subjects are:Overview Application Delivery:
- Application Installation
- Application Isolation
- Application Virtualization
Application Installation: The way we work now!
New technologies like Isolation/Virtualization
Demonstration of Microsoft SoftGrid and Thinstall
If you want to know more about this training you can look at the Ictivity Training website, Edwin Friesen of Thinstallguru.com is the instructor for this course.
Rescan all vmhba’s at once with the esxcfg-rescan command
Using the console it’s very easy to rescan a specific vmhba which can be useful when you are troubleshooting. For lazy people like me it’s disturbing that you have to type the command twice if you want to rescan both HBA’s. Well, as of version 3.5 VMware introduced a new setting in Advanced configuration section in the VirtualCenter Client:
Go to “Configuration” of the ESX Host
Click on “Advanced”
Click on “Scsi”
Set “Scsi.ScsiRescanAllHbas” to 1
This can also be done from the command line:
esxcfg-advcfg -s 1 /Scsi/ScsiRescanAllHbas
Now you don’t need to type “esxcfg-rescan vmhba1” and “esxcfg-rescan vmhba2” anymore, when rescanning an HBA all cards will be rescanned.
Clone and roll out template fail with “failed to connect to host”
Recently I implemented ESX 3.5 with VirtualCenter 2.5. After I installed the ESX Hosts and the VirtualCenter server the customer told me that I had to change the ip-addresses of the service console. I removed the ESX hosts from the VirtualCenter server, removed the vswif of both hosts with “esxcfg-vswif -d” and created it again with the correct ip-address and subnet. I added both hosts to the cluster again and every thing seemed to work again… until I decided to rollout a template. It took over 10 minutes before the error “failed to connect to host” appeared. [Read more…] about Clone and roll out template fail with “failed to connect to host”
CPU utilization increasing after VMotion in a DRS enabled cluster
VMwarewolf already posted this fix on his blog but had to remove it… Now VMware added it to their knowledge base. Check out the original article because it may change in time. For the lazy people I included how to diagnose the problem and more…
Diagnose the problem:
- Use the VI Client to log in to VirtualCenter as an administrator.
- Disable DRS in the cluster and wait for 1 minute.
- In the VI Client, note the virtual machine’s CPU usage from performance tab.
- In the VI Client, note the virtual machine’s memory overhead in the summary tab.
- Enable DRS in the cluster.
- Use VMotion to move the problematic virtual machine to another host.
- Note the virtual machine CPU usage and memory overhead on the new host.
- Disable DRS in the cluster and wait for 1 minute.
- Note the virtual machine CPU usage and memory overhead on the new host.
If the CPU usage of the virtual machine increases in step 7 in comparison to step 3, and decreases back to the original state (similar to the behavior in step 3) in step 9 with an observable increase in the overhead memory, this indicates the issue discussed in this article.
You do not need to disable DRS to work around this issue.
The workaround:
- Use the VI Client to log in to VirtualCenter as an administrator.
- Right-click your cluster from the inventory.
- Click Edit Settings.
- Ensure that VMware DRS is shown as enabled. If it is not enabled check the box to enable VMware DRS.
- Click OK.
- Click an ESX Server from the Inventory.
- Click the Configuration tab.
- Click Advanced Settings.
- Click the Mem option.
- Locate the Mem.VMOverheadGrowthLimit parameter.
- Change the value of this parameter to 5. (Note: By default this setting is set to -1.)
- Click OK.
To verify the setting has taken effect:
Log in to your ESX Server service console as root from either an SSH Session or directly from the console of the server.
- Type less /var/log/vmkernel.
A successfully changed setting displays a message similar to the following and no further action is required:
vmkernel: 1:16:23:57.956 cpu3:1036)Config: 414: VMOverheadGrowthLimit” = 5, Old Value: -1, (Status: 0x0)If changing the setting was unsuccessful a message similar to the following is displayed:
vmkernel: 1:08:05:22.537 cpu2:1036)Config: 414: “VMOverheadGrowthLimit” = 0, Old Value: -1, (Status: 0x0)Note: If you see a message changing the limit to 5 and then changing it back to -1, the fix is not successfully applied.
To fix multiple ESX Server hosts:
If this parameter needs to be changed on several hosts (or if the workaround fails for the individual host) use the following procedure to implement the workaround instead of changing every server individually:
- Log on to the VirtualCenter Server Console as an administrator.
- Make a backup copy of the vpxd.cfg file (typically it is located in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg).
- In the vpxd.cfg file, add the following configuration after the <vpxd> tag:
<cluster>
<VMOverheadGrowthLimit>5</VMOverheadGrowthLimit>
</cluster>
This configuration provides an initial growth margin in MB-to-virtual machine overhead memory. You can increase this amount to larger values if doing so further improves virtual machine performance.- Restart the VMware VirtualCenter Server Service.Note: When you restart the VMware VirtualCenter Server Service, the new value for the overhead limit should be pushed down to all the clusters in VirtualCenter.