Monday, October 22, 2012

issue: a normal virtual machine with no high resource hungry application is reporting high cpu usage with alarms, performance charts of the vcenter show the same high cpu usage, the task manager of the virtual machine shows very high cpu usage too.

cause and resolutioin: This was a p2v virtual machine from a hp proliant server. When checked in the task manager under processes the high cpu using program was cqmgserv.exe which belongs to hp insight agent.

uninstall all the hp or hardware specific applications/drivers from the VM from the control manager.
Issue Resolved.

Wednesday, October 17, 2012

Issue: customer who is
trying to certify VMware ESX4.1U2 on the DL360 Gen8 and DL380 Gen8. They
seem to be using the correct driver but the service console command “lspci” is
showing the 331FLR is an unknown device. They are able to PXE boot off
the NIC and it seems to be working normally, but they wanted some investigating.

They have
tested with both VMware’s build and the HP ESX built and received same result
in both cases

Reason:

lscpi compares the pci id’s
against an internal “database” to determine the information to display.
For newer devices, the only way to get an update is for VMware to provide
updated info for the “database”. These updates are provided with ESXi
updates or new releases (e.g. 5.1 U1, 4.1 U3). There is no impact to
functionality, this is purely a reporting issue.

“esxcfg-nics –l”
should report the appropriate model.Once the hosts are updated with the new databases through vmware patching or updates it should show up properly with the lspci command too.

About Me

A passionate IT Professional with an endless fetish for innovative Science & Technology.I am a lot of things and a few among them areAn avid gamer,loves photography(not anymore),love a lot of variety of music, movies (foreign),like a lot of manga, anime series and most importantly love life.