I noticed at a few customer sites that the Performance tab of VirtualCenter was getting sluggish but never got the chance to really pinpoint the problem. A couple of days ago user “jterpstr” posted about this on the VMTN forum and it seems that the old rows aren’t deleted from the database for some reason. The table grows to an enormous amount of rows which causes some queries to become unresponsive or very very slow. For more info and a possible solution keep track of this topic om the forum. Thanks to the guys in this thread for pinpointing the problem and narrowing it down to a possible cause.
VirtualCenter
Installing VirtualCenter 2.0.2 on a Windows 2000 SP4 server
Today I encountered a weird problem. When I started the installation of VirtualCenter 2.0.2 on a Windows 2000 Server I received the following error notification:”Setup cannot continue. The “VMware VirtualCenter Server 2.0″ requires Update 1 Rollup for Windows 2000 SP4. Please see KB article 816542 at http://support.microsoft.com/kb/816542/.”
I checked the server but the patch was installed, so I rebooted the machine to be sure the installation of the update was completed but no luck. I reinstalled the patched and tried to install VC but again no luck. Next thing to do was check the VMTN forum and luckily someone already encountered the same weird problem and they received the following fix from VMware support:
************ Problem ***********
Update from VC 2.0.0 to VC 2.0.1 not possible.
Error message that Update Rollup 1 is not installed.************ Root Cause (if known) ***********
Wrong registry check of installer.************ Solution ***********
Replace NTDLL.DLL by KERNEL32.DLL in the registry:HKLM\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\Update Rollup 1\Filelist\0]
“FileName”=”NTDLL.DLL”
“Version”=”5.0.2195.7006”
“BuildDate”=”Thu Jan 13 10:09:36 2005”
“BuildCheckSum”=”77ecb”
“Location”=”C:
WINNT
system32”
P2V’ing a Suse Linux server
I just P2V’ed a Suse Linux Server with the cold boot iso. When booting I was confronted with a kernel panic. This is caused by the fact that the modules for the LSI Logic or Bus Logic SCSI card aren’t available, which causes the root volume to be unmountable. I tried to boot from the installation CD with the “rescue” option but this did not provide me with a fast solution for the problem. But the following was a quick fix:
- Boot from Suse CD
- Select to setup a new system
- Select to boot from the currently installed OS
- Run Yast and configure the correct SCSI controller
- Remove all the NICS and configure a new NIC
- Install VMware tools
Installing the Converter plugin crashes the VirtualCenter client – PART II
For those who did not have any luck with the deleting of the dll(ssleay32.dll) described in this blog, there’s another possibility to enable the VMware Converter plugin without crashing your VirtualCenter client:
Go to the following registry key:
[HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences\UI]
And set the following key to “Enabled”
“C:\\Program Files\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Plugins\\Converter Enterprise\\plugin.dll”
Installing the Converter plugin crashes the VirtualCenter client – Part I
Today I encountered a weird phenomenon which I did not encounter yet. I installed the VMware Converter Plugin for VirtualCenter client, so far so good. Only thing left to do was to tick the checkbox to enable the plugin. But as soon as I ticked it the VirtualCenter client crashed without any warning. I rebooted the server, and tried it again… without any luck unfortunately. I reinstalled the plugin, again no luck… I checked the wonderful VMTN forum and someone already solved this problem, it’s due to the “ssleay32.dll” in the system32 directory which is incompatible with the one VMware converter uses. Remove it, and everything will work like it should! If this doesn’t work, check out this follow-up.