Kasraeian

Hi,
During my testing VMware ESXi 4.1 which is the last version currently, I’ve installed it on two VM on my VMware Workstation 7.1 which supporting ESX 4.0 as guest OS.
The system I’m used on my working place have Intel E5300 CPU, 2GB DDR2 Memory and running Windows XP SP3.
continue reading…

Some days ago, I get one HP DL380 G5 server from one of my friends in project which we all working on it (he is our project manager), so I can install and test Microsoft Windows Server 2008 R2 edition as well as new feature in Hyper-V.
I had installed and worked a little with Hyper-V, it’s new and cool but lets being honest, It’s not as cool as VMware products are. continue reading…

This is the another listen learn from my project in data center as well as reminder for myself.

After few months of installation and configuring all systems and servers, the times on Microsoft windows servers changed and there’s 1-hour missed.
All system configured to get their time config from NTP server in data center, all servers and NTP server are configured in GMT 3:30+ (Iran/Tehran). continue reading…

Hi,

Just as I said before, I start posting the summary here.
So, let start it now, this post contain some info about:

• Result of wrong OS type installation in VM with different OS type
• VMware HA (Design, fail-over, …)

Result of wrong OS type installation in VM with different OS type

One configuration/step during the creation of new VM, is defining the OS type for that VM.

If any other OS except the OS type selected for VM, installed on VM, some of the following even (or all of them) may occurs:

• Some performance issues (according to different method of memory access and addressing, …)
• This would cause the incorrect VMware Tools to get installed in the VM
• If the correct MCA/MCE architecture is not presented to the guest during boot may be it wouldn’t start at all

How to fix it:

• Power off the VM.
• Modify via GUI option General of the properties of your VM.
• Power on the VM.
• Reinstall the correct VMware Tools.

VMware HA (Design, fail-over, …)

When designing or using VMware HA, it’s better to take care of some element in order to get better performance, availability and facing less problem/error.

• Setup/configure second SC/management network so you would have to path for check for host isolation.
• Don’t use default just because they are default, check the other options and compare their result for your own situation. (Number of allowed host failures …)
• For getting better result from your ha cluster, prevent using resource (cpu/memory) reservation as much as you can, as it affect directly the ha cluster performance (slot size/number of slot in cluster, …)
• When using ha on Blade servers, on more than one enclosure use more smaller (at least two) cluster instead of one big cluster.

Feel free to leave comments or any idea you have.
These information are summary (or better say notes) I took during my studies for future use.
If I miss anything; please correct me, thanks.