Virtualization Team

I know many Virtualization Consultants who all are still wondering where is the Intel Nehalem processor in the VMware Capacity Planner. The Nehalem processor has already hit the market more than 6 months back, VMware still has not update their Capacity Planner to include it. We all know that the Nehalem processor is providing a great performance & efficiency enhancement comparing to the prior Intel processors & this change should be taken into the consideration When doing Capacity Planning.

This article title say “Sony VAIO laptops disabled Intel VT“, but what should that mean to you. It should mean the world to a lot of us. It should mean think twice trice before you buy a Sony VAIO laptop, due to the amount of limitation that come with disabling Intel VT. Ok, let’s see some of the most obvious limitation:

1- Sony VAIO Laptops will not support Windows 7 XP mode, which require enabling hardware Virtualization:

Windows 7 will be offering a great feature which is called XP mode, which will allow you to run most of XP applications on Windows 7 without having to worry about application compatibility with Windows 7. As Windows 7 XP mode requires Hardware Virtualization which Sony has decided to disable on their laptops. This means if you are upgrading to windows 7 then Sony VAIO laptop might not be for you.

I want all of you to look at this logo & try to guess which company logo is this .

Ah if you rather watch this post as a video instead of reading it check the video below else keep reading.

I am sure this logo is familiar to most of us. At least I am sure 75% of you had already guessed whose logo is this . Do you think you really know whose logo is this? Well then scroll down to see the answer. If you missed it or got it right the first time then please leave me a commend & a feed back of this small puzzle .

.

vSphere Virtual Center Linked Mode Prerequisites:

Well, yes this article has two headers or titles. Guess what they are almost identical.

I have seen “Error 28039. Setup cannot join vCenter Server to the linked mode group” all over the net & without any one posting resolution for it. hmmmm, how did I find out about this error and what made me looking for resolutions, well I had faced this same ugly error in my own lab. The resolution for it was nothing more than following the pre-requisite to vSphere Virtual Center Linked Mode which most people ignore. Below is the pre-requisite that you must follow for a successful installation of vCenter Linked mode & I will highligh the mostly missed one.
All the requirements for standalone vCenter Server systems apply to Linked Mode systems. In addition, to the following requirements:

Many of you have already heard about the new VMware vNetwork Distributed switch. It has been a really great innovation by VMware. I believe most of us has already learned something about its benefit like:

1- Simplify Virtual Machine Networking: As you get to create one switch per cluster & create the policy across all your ESX hosts at once instead of repeating the process endlessly.

2- Enhance Virtual Machine Networking:

• VMware vNetwork Distributed Switch maintains network runtime state for VMs as they move across multiple hosts, enabling inline monitoring and centralized firewall services.
• It provides a  framework for monitoring and maintaining the security of virtual machines as they move from physical server to physical server