Pages

2009-09-23

One of the most ridiculous things that Microsoft are saying as of late is that the feature in vSphere that allows you to over commit memory, is not such a big thing and that most people do not use it anyway - herehere and here.

If you saw my previous post you will see that I managed to double the amount of virtual machines running on the same host (from 8 to 16 VM's running Windows 2003 Server 1GB RAM) without changing the 8GB RAM configuration on the host.

Would I be able to do this with Hyper-V? Hell No!

So I will say this again to Microsoft. Customers use Memory over-commit, they use it daily, and use it all the time. As long as you do not have this feature - this will be a strong point against using your product.

A client came to me a few months ago requesting help with a problem they had.

They have a system that does some (I guess you can call it) grid computing. They were using 20 desktops with XP to compute perform some calculations, and the the process was taking 10 hours , utilizing ~100% CPU on each machine throughout the process.

Because of a change that was made in the algorithm, the process would now take 22 hours to complete, for the same amount of calculations and that was not an acceptable result.

We wanted to test, would it be possible to cram a large amount of Virtual machines to do the work and we came up with the following solution:

3 IBM x3550 Dual E5430 Processors

8 GB RAM

ESX3i on each of them

8 Windows Server 2003 VM's on each server (total of 24 VM's)

We saw that when the Virtual machines were busy doing the calculation process, they were utilizing 100% of the vCPU, bringing the host to very close to 100% utilization during the calculations. This was the hard limit of 8 VM's on each host.

The amazing thing was that the same run that would have taken 22 hours on physical Desktops now took on these three servers 8 hours (a 275% increase in performance). The client was thrilled!

We tested different configurations of more VM's with lower CPU limits, but since the utilization was 100% regardless of the speed of the vCPU, the results stayed that the optimized configuration was 8 VM's per host.

The cost for the whole design (including a test Server and a Management sever) was

Fast forward 6 months. Budget issues, etc. etc.

Client comes to say that they are ready to go forward with the project. But there was one slight problem. During that period IBM announced that they were going over to a new series of Servers (x3550M2) and that the old ones were no longer available for purchase.

And also during that period ESX4 was released.

New servers were tested with the same data as before, this time on a x3550M2 with Dual E5530 Processors.

We fired up the tests with the same 8 VM's as before. the results were pretty much the same. Except for one small thing. We were seeing that the the CPU was only 50% utilized (or more correctly only 50% of the cores were being used) Huh??

With Hyper threading enabled - the machine recognized 16 cores. So we deployed another 8 VM's (16 in total on one host). And of course there was no problem of RAM, because since all the machines are exactly the same,

I am not saying that in all use cases this will work, but this one did. We ran the tests, and instead of the results we had with the previous hardware of 8 hours, the job was now complete in 5 (a 60% increase in performance). With this metric, we now could reduce the number of physical Hosts from 3 down to 2. Also the pricing for VMware Software that was on the original configuration (Foundation Accelerator Kit) was now replaced with the VMware Essentials at a lower price (40%). In the same configuration we now configured the system with 2 ESX hosts and 32 VM's.

the new price for the project.

So yes, the Nehalem Processors, are a good thing, and in this specific case - it managed to lower the costs and boost the performance.

When VMware released the free product VMware Server 2.0.0 version, they decided to get rid of the Console client application.

Was this a good thing? Some say no, some say that it was, personally - I think it was a mistake to ditch the Console.

A bit of background.

When you install Server 2.0.x, bundled with it you get an Apache/Tomcat installation on your host.

Now this is something that I find personally annoying. Take for example a Windows Host. Windows has IIS built in. So why do I need to add another Web server to the machine. Same goes for Linux by the way, this will install its own Web Server, regardless if you are already using Apache on you Linux host

And it uses resources..

This is the management console that you receive.

There are certain use cases for running Server instead of ESXi, to name a few - non compatible hardware, access to USB devices, sound etc. that you cannot get with using ESXi

But never fear, and this is not a very well documented feature, but it is available. Some of you might have heard about a management tool that can help. It is free, it is a VMware product and most of you are already using it.

If you have not already guessed, I am talking about the vSphere Infrastructure Client.

So how would you go about doing this? Well it is pretty simple. When managing your host through the Web interface you went to the following ling (my host IP = 10.0.0.5) https://10.0.0.5:8333/ui/#

So what you should do is open the VIC and in the host field connect to the host but on port 8333 like this:

Login with your credentials and then you get a familiar screen

Note the subtle differences though

And last but not least a remote console to a working VM

This is fully functional. You can create VM's, change resources, Snapshots, the works!

And of course I do not need apache running and using resources.

Why did I find it important to bring this to your attention? With this method it allows you use a single tool and application to manage all your virtual hosts, be they:

2009-09-17

From this this post on Technet - we can finally say that if you have a Windows 2000 Server in your enviroment - GET RID OF IT!!!!!! (or at least before July 13, 2010)

Another small thing to note - Service Pack 2 for Windows 2003 - was the last, there will be no no SP3.

Here is the short version.

Windows 2000 Server

Extended Support for Windows 2000 Server will end on July 13, 2010. At this time, Windows 2000 Server will no longer be publicly supported. You will be able to continue using "Self-Help Online Support"*

Windows Server 2003 and Windows Server 2003 R2

Also on July 13, 2010, Windows Server 2003 and Windows Server 2003 R2 (at a supported service pack level) will move from the Mainstream Support phase to the Extended Support phase. During the Extended Support phase:

Customers will continue to have access to all security updates and Self-Help Online Support options (Example: Knowledge Base articles, online product information etc.)

Non-security hotfixes developed during the Extended Support phase will be provided ONLY to customers who enroll in Extended Hotfix Support (EHS).

Please note: If you'd like to enroll in EHS, customers must already have a Premier Support contract. In addition, customers must enroll in EHS within the first 90 days of the Extended Support phase. Program and per fix fees may also apply. Customers with Software Assurance can enroll in EHS at any time.

Service Pack 3 for Windows Server 2003

We have received inquiries from our customers and partners on whether or not there will be a need for a Service Pack 3 for Windows Server 2003. Microsoft will not have a SP3 release for Windows Server 2003.

To Summarize...

Self-Help Online Support* will be available for Windows 2000 Server after Extended Support before it ends on July 13, 2010.

Windows Server 2003 and Windows Server 2003 R2 will begin an extended support phase on July 13, 2010

it is a 51 page document, with step-by-step walkthroughs of how to troubleshoot performance problems on an ESX host regarding all aspects - Network, Storage, CPU, RAM, Guest, and Host.

The troubleshooting process starts with the top-level troubleshooting flow in Top-Level Troubleshooting Flow. However, the introductory material includes background information that is important for the successful completion of a performance troubleshooting effort. Identifying Performance Problems discusses what we mean by a performance problem, and how to tell when observed behavior is and is not a problem. Performance Troubleshooting Methodology gives an overview of the troubleshooting methodology used in this document. Using This Guide discusses how to use this guide. The guided approach makes using this document different than reading a typical manual. Performance Tools Overview gives an overview of the performance monitoring tools used in the troubleshooting process. Starting with Top-Level Troubleshooting Flow, the remainder of the document covers the process of using the performance monitoring tools to identify observable performance problems, find the root-cause of those problems, and then fix the causes.

Of course activating the shell console on ESXi is not supported - I do not need to remind you about that. But, if you already have done it and would like to transfer files in and out of your ESXi host with FTP, here is how.

2009-09-10

Last week I prepared a short explanation of what changes there are in vSphere Licensing in anticipation of the upcoming date of December 15, 2009 whereas we will no longer be able to purchase vSphere ESX Enterprise.

Think this is a good summation of what your options are, and thought that I would share it with the community.

It is always good idea to be pro-active, instead of re-active.

With the release of vSphere at the end of May 2009, the licensing Structure for vSphere has changed from the previous structure that we are accustomed to in VMware Virtual Infrastructure 3.5 (VI3)

1. There is no change in vCenter Server Licensing.

2. vSphere is now sold per physical CPU. The VI3 license was always for 2 CPU's. As of the change to vSphere it is priced per CPU, so please take care when placing your orders.

3. The editions in which ESX are now offered have changed from what was available in VI3

Editions Available in ESX 3.x were:

Foundation

Standard

Enterprise

Editions available in ESX 4.x are:

- Essentials / Essentials Plus (Bundle)

- Standard

- Advanced

- Enterprise (*This is a special case that will explained later in detail)

- Enterprise plus

Below is a schematic as to how the different editions map between the versions (all Prices in the document are VMware List Price)

Here is the feature breakdown for the new versions

Most of the Servers deployed today in our company are using the ESX Enterprise version, and using the Enterprise features of: VMotion, Storage VMotion, and DRS.

In order to accommodate customers VMware decided to continue the Enterprise License - but only until the End of the year (December 15, 2009). Thereafter, this edition will not be available for purchase. This has been confirmed with VMware support and licensing departments and on numerous locations in the Virtual community.

What does this mean for customers and for company in particular?

1. Starting December 16, 2009 - Enterprise will no longer be an option for purchase.

2. The Enterprise version will continue to be supported after the deadline mentioned above.

3. We will have to choose which version we will purchase instead - Enterprise Plus or Advanced.

Advanced

We will be able to continue to use most of the features we have been using until now - besides two important features

- Storage VMotion (migration of VM's from one storage device to another in real-time)

- DRS (Dynamic Resource Scheduling of optimal placement of Virtual machines - based on their utilization)

Enterprise Plus

This will include all previously used features plus the new features of Host Profiles, Distributed vSwitch and 8-way vSMP.

Important issues to note if upgrading to Enterprise Plus

If you currently use the features of SVMotion and DRS and plan to do so in the future then you will have to purchase the Enterprise Plus license.

The new features that come with Enterprise plus will only work if all of the hosts in that cluster are at the same level.

2009-09-02

vControl Multi-Hypervisor Management provides multi-VM control and task-based automation to reduce VM administration and improve consistency. Furthermore, vControl Multi-Hypervisor Management allows organizations to automate manual and repetitive tasks while enabling a cost-effective solution for high availability in the data center.

Working across multiple platforms, including VMware ESX/ESXi, Microsoft Hyper-V, Citrix XenServer, and Sun Solaris Zones, vControl gives administrators the power to manage single or multiple VMs one-by-one or simultaneously. Finally, vControl Multi-Hypervisor Management provides pre-configured workflows to manage daily tasks, as well as a workflow builder for customization.

vControl Multi-Hypervisor Management helps organizations:

Reduce virtual machine (VM) administration time and errors without sacrificing control of the virtual environment

Perform various actions on a single VM or for multiple VMs to reduce time and effort

Automate manual and repetitive tasks while freeing up time to perform more valuable tasks

vConverter SC freeware from Vizioncore is enterprise-class software that significantly reduces the time, cost, and effort required to convert physical and virtual machines to VMware®, Microsoft®, or XenServer™. vConverter SC is suitable for all types and sizes of server consolidation initiatives where several or even thousands of physical servers need to be virtualized.

vConverter SC enables fast, easy and reliable conversions without disrupting the source physical system during the conversion process. There is no need to reboot, no need to visit machines being converted and no software to install on the source, which means virtually no downtime, thus significantly reducing the time and cost of the conversion process. vConverter SC also automates many time consuming and error prone conversion tasks such as target VM configuration and post conversion clean up.

vOptimizer WasteFinder is powerful freeware product that scans through VMware vCenter Servers (formerly Virtual Center) to locate over allocated virtual storage and misaligned Virtual Machines (VMs). The vOptimizer WasteFinder Space and Alignment Report provides totals of wasted storage and also a potential savings estimate if the space is reclaimed.

This unique storage optimization solution allows organizations to determine whether they are wasting expensive storage assets, to locate which VMs will yield the best storage reclamation results, and to discover how much money they are really spending on unused virtual storage. Potential savings estimates are calculated using customer provided storage costs and free space requirements to ensure accuracy.

The Go interface is the only way to interact with that data at this time. Although future versions will be able to export data and get more extensive reports.

VMware Go can read and write from your ESXi installation using the VMware PowerCLI. It does not interface to ESXi through APIs.

VMware Go is a SaaS application that runs in the cloud and cannot be run locally on your network. However, since the VMware Go agent runs on your client machine, you can access ESXi and VMs running on your network and they can be used by VMware Go. VMware Go is available for free on the internet, there are no plans for intranet versions for personal use.

The information stored by VMware Go like IP address, ESXi Config data, etc, are stored only to create a good user experience in VMware Go and improve future reporting capabilities.

So from these answers I was left with even more questions? (and Texiwill - forgive me for being the paranoid security guy here in your place)

People will have issues "entrusting" their infrastructure to an application that they have absolutely no control over

I have no idea of what information is stored in on VMware's servers.

I have no idea what VMware will do with this information?

Who can assure that the information will not be compromised?

How all of a sudden did the read-only API in the free ESXi become read/write?

If the configuration can be triggered from the WWW is this not punching a whole in the corporate LAN?

I know that this is free, I know that is targeted to the SMB market but quoting Wikipedia

EU Member States traditionally have their own definition of what constitutes an SME, for example the traditional definition in Germany had a limit of 250 employees, while, for example, in Belgium it could have been 100. But now the EU has started to standardize the concept. Its current definition categorizes companies with fewer than 10 employees as "micro", those with fewer than 50 employees as "small", and those with fewer than 250 as "medium".[1] By contrast, in the United States, when small business is defined by the number of employees, it often refers to those with fewer than 100 employees, while medium-sized business often refers to those with fewer than 500 employees.

Will those businesses allow the first 5 points that I mentioned above to endanger their environment?

I as one would suggest that they make this available as a application (Virtual Appliance like almost everything that is being added today) that each customer can run in his own infrastructure.