PSOD on HP Proliant G7 with AMD 6100 Series

Posted on March 1st, 2011 in Server, Tips, Virtualization, vSphere | 2 Comments »

There is known issues been faced by small group of user who had deployed their VMware ESX host on the latest platform with G7. You can refer to the official link from HP here and additional KB from VMWare referring to the same issues. If you are facing this, you may be the unlucky 1, but nothing much you could do as the PSOD message will refer to the CPU error, compatible issues and etc.

The only thing you could do is to wait until both HP and VMware to come out a final fix in this case. Quick solution, is change hardware vendor or different platform. I had experienced 3 times about it, in the past 2 months and this is the latest finding we had received from both VMware and HP regards the latest PSOD we had. HP had recommended to upgrade the BIOS, Firmware and driver for multiple times, but this doesn’t fix the issue we are facing. Lately there had release another new update bios and hope this problem will be gone after this.

Feel free to share any work around solution beside the official link provided by tech support.

Read more »

Network Card Driver failed ESX host with DL 585 G7

Posted on January 18th, 2011 in Server, Tips | No Comments »

Recently there are couple of issues I had faced on the latest DL 585 G7 server which installed with ESX 4.0 Update 2. The common problem reported by couple of users are same which could potentially caused all the network traffic dead off for the entire ESX host. The even worst case could be happen and cause Purple screen to the ESX host. The current solution is to either update the NICs driver with the latest version, but I will suggest to disable all on board NIC and replace with either Broadcom and Intel Gigabits adaptor. This will isolate unnecessary issues which I had not seen in others servers brand.

Please refer to the VMware Forum Here for the confirmation on bugs with multiple users who experience the same issues as I did.

Read more »

Maximize CPU utilization on ESX host with Cisco UCS B250M2

Posted on October 16th, 2010 in Server, Tips, vCenter, Virtualization, vSphere | 4 Comments »

We were doing some stress test with more than 15 VMs on a single B250M2 Cisco UCS blade machine with 2 x Intel 6 Cores 2.93Ghz, and 192GB memory. While are stress test are pretty simple, each VM been provisioned with 2 vCpu and 4GB of physical memory. We maximize the CPU load of all the virtual machine and end up I was able to capture the print screen as attach here.

Read more »

Great Post about NUMA Hyperthreading in ESX 4.1

Posted on October 8th, 2010 in Tips, Virtualization, vSphere | No Comments »

As you may aware, significant improvement had been done on the latest hypervisor from VMware vSphere 4.1.
1 of the key changes are the vCPU for each virtual machine with latest NUMA hyperthreading architecture.

I found a very details and great post talk about this topic, please read the full post from here.

This will significant improve the Consolidation ratio and performance over the virtual machine VS the previous version ESX 4.0.

Read more »

How to make APC PCNS 2.2.4 work with ESXi 4.1

Posted on October 7th, 2010 in ESXi, Tips | 2 Comments »

For the past 1 week, I have been busy with the APC PCNS and ESXi 4.1 and I would like to share my experience “How to make APC PCNS 2.2.4 work with ESXi 4.1″ here.

Basically I will not discuss How To Install PowerChute Network Shutdown on VMware ESX /ESXi again and you may refer to APC official link here.

If you’re try to install APC PCNS 2.2.4 on vSphere Management Assistant (vMA) 4.1 and I’m sure you will get the similar error like “This version of PowerChute Network Shutdown only support VMware ESXi” which I think APC teams should it much more clear. The error message caused by APC PCNS (ver 2.2.4) setup file – “install.sh” which check on “/etc/vima-release” file. In the vMA 4.1 released, you’re can only found “/etc/vma-release” file which changed recently. Create a symbolic link or edit the installation script can temporary ignore these error message. See this link.
Read more »