VMGuru.nl – I choose (a virtual) life!

With the release of vSphere 4.1 it will be the last version of ESX to be released in an ESX and an ESXi version. After this version only the ESXi flavor will be released. We at VMguru.nl predicted that this would happen a few years back, so we advised our customers to go for the ESXi version, too make it a lot easier to migrate to a newer version in the future.

VMware recommends that customers deploy vSphere 4.1 on the ESXi hypervisor architecture as a best practice.

In the past some features from the ESX architecture weren’t supported on the ESXi platform. As of vSphere 4.0, all the functionality of VMware vSphere is supported on both architectures, including support for Jumbo Frames, Cisco Discovery Protocol (CDP), NetQueue, and NetFlow.

VMware ESXi is the latest hypervisor architecture from VMware. It has an ultra-thin architecture with no reliance on a general purpose OS, yet still offers all the same functionality and performance of VMware ESX. For a comparision between ESX and ESXi 4.1 see the following article.

(more…)

While designing and writing administrator guides, I often use pictures instead of words. In my opinion: a picture says more then 1000 words. When VMware vSphere 4 went live I started collecting pictures from  Sphere and the Virtual Infrastructure client, I combined them in a Microsoft Visio 2007 shape so I could track off them and use them more often in pictures and designs accompanying virtual infrastructures.

Using them in memo style documents to tackle known issues or incorrect handling is quit effective. Also with the new menu driven style of the vSphere VI Client combined with VMware vCenter Server some administrators are looking for the right path to get to the correct content.

This Visio stencil is a combination of different icons, shape and such. You can design a Host and Clusters drill down with it or use components to use in manuals or troubleshooting documents.

(more…)

Last year we published an Enterprise Hypervisor comparison and we got very positive comments and feedback on it.

During the last few weeks I received many update requests so I decided to update the old hypervisor comparison but this time I changed the setup a bit.

Changes:

• No beta or pre-release versions are used. In the last document we also compared Hyper-V R2 beta which wasn’t officially released.
  This time all software is available and no features are subject to change due to beta-test, etc.;
• The versions used are the platinum/ultimate/fully-featured versions of the hypervisors. Product features can be limited by lower license versions;
• No free versions have been used in this comparison.

(more…)

There was an issue discovered earlier today that prevents View Composer from working with vSphere 4.1.

VMware apologizes for any inconvenience this may have caused you. If you know how to spread the word to your friends and colleagues, please do so.

With yesterdays release of vSphere 4.1 comes the challenge to upgrade your existing installation to this new version. Because I have been testing the beta for a while now, I couldn´t wait to try it in our new testing environment.

However, there are a few caveats:

• VMware released a KB article with the supported upgrade methods for ESX(i) 3.0.x, 3.5 and 4 full, embedded or installable;
• Do NOT upgrade vCenter server to version 4.1 if you are using VMware View Composer 2.0.x. Check out this VMware KB article for more information.

Before you start the upgrade process, back-up the vCenter- and Update Manager databases.

After downloading the needed ISO´s, I started with the upgrade of the vCenter server.

But first of all, I had to uninstall all incompatible vCenter components, in this case Guided Consolidation 4.0.

When this is done, it´s time to update the vCenter server.

(more…)

A few minutes ago VMware has released the new version of VMware vSphere, version 4.1.

This new vSphere version contains 150 new features and has improved scalability, memory management, DRS, etc.

Besides all the new features the greatest news is that vSphere 4.1 is the last version which will have an ESX version (with service console). As of the next version there will only be two versions, ESXi embedded and installable.

Below you will find a detailed list of features that are include with the vSphere 4.1 release:

• Scalable vMotion;
• Wide VM NUMA;
• Storage I/O can be shaped by I/O shares and limits through the new Storage I/O Control quality of service (QoS) feature;
• Network I/O can be partitioned through a new QoS engine that distinguish between virtual machines, vMotion, Fault Tolerance (FT) and IP storage traffic;
• Memory compression will allow to compress RAM pages instead of swapping on disk, improving virtual machines performance;
• Distributed Resource Scheduling (DRS) now can follow affinity rules defining a subset of hosts where a virtual machine can be placed;
• Virtual sockets can now have multiple virtual CPUs. Each virtual CPU will appear as a single core in the guest operating system;
• Support vCenter on 64 bit operating systems only;

(more…)

With the release of vSphere 4.1, VMware has released a new licensing model.

The management products below change from a CPU-based pricing model to one that is VM-based.

• VMware vCenter CapacityIQ;
• VMware vCenter AppSpeed;
• VMware vCenter Site Recovery Manager;
• VMware vCenter Chargeback.

Until December 15th these product can be offered both ways, CPU-, or VM-based.

As of today VMware vCenter Lifecycle Manager is end-of-sale.

This new licensing model has no impact on VMware vSphere licensing!

If you haven’t upgraded to VMware vSphere 4 by now, you should consider it and rethink your strategy. VMware has removed all but the most recent versions of their Virtual Infrastructure product binaries from their download page on June 17th. As of May 2010, the following Virtual infrastructure products have all reached end of general support according to the published support policy:

• ESX 3.5 versions 3.5 GA, Update 1, Update 2, Update 3, Update 4
• ESX 3.0 versions 3.0 GA, 3.01, 3.02, 3.03
• ESX 2.x versions 2.5.0 GA, 2.5.1, 2.5.2, 2.1.3, 2.5.3, 2.1.2, 2.5.4
• Virtual Center 2.5 GA, Update 1, Update 2, Update 3, Update 4, Update 5
• Virtual Center 2.0

(more…)

During the last month I have been very busy building a new infrastructure at a client site. I’m responsible for the overall technical solution and the basis, a VMware vSphere infrastructure build on five Dell PowerEdge R805’s, Dell EqualLogic PS5000 and 6000 storage and Cisco switches for LAN, DMZ and IP storage networking.

Just before the customer initiated their functional test period we discovered that the overall Windows network  performance was slow. We did several test like copying an 8 GB file from local vmdk to local vmdk and VM to VM and found that the storage performance was no issue but the network performance was very slow.

In the last few years that I have been working with virtualization I have always been a fan of a static network configuration. Meaning, when I configure ESX networking I like my network interfaces and physical switch ports to be configured at 1000MB full duplex if the switch/network interface combination allows it. The idea is that if you purchase gigabit network interfaces and switches you know the maximum speeds. So you configure it to run at it’s maximum capacity, eliminating overhead and using as much bandwidth as possible purely for data transfer.

So when we experienced slow network performance I had a colleague check the Cisco LAN switches for errors, drops, packet loss or any other flaw which might indicate a speed or duplex mismatch. None were found so I assumed that the network configuration was not the issue. But as we know by now, ‘Assumption is the mother of all fuck-ups!‘.

(more…)

Up until a week ago, I hadn’t had the pleasure to work a lot with vSphere. Now with a test environment at the customer site I was able to freely play a bit with vSphere. One of the features I was curious on trying was Fault Tolerance (FT). I just created a random VM and enabled FT on it which all went fine.

After FT was enabled on the VM we wanted to see how we could upgrade the ESX hosts in that cluster as the documentation states that FT only works on hosts with the same build number.

(more…)

Last week I had another nice discussion around the 90 day assignment rule for Windows Server licensing on a VMware environment.  To answer this shortly: You may move running instances between licensed servers without acquiring additional licenses. However you cannot exceed the maximum number of instances each server is licensed to run.

Microsoft Operating System Environments (OSE)

Microsoft defines Operating System Environments for allocating licenses. This is a nice and flexible way to accommodate customer demand.  To understand how licensing works under virtualization, it is important to understand how Microsoft defines an OSE.

An “operating system environment” is:

1 all or part of an operating system instance, or all or part of a virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and

2 instances of applications, if any, configured to run on the operating system instance or parts identified above.

(more…)

While I was updating the Determining VMware vCenter and ESX Build Numbers post I thought I would semi-automate the updating of the post with new build numbers for new releases, while working on it I started too fill an excel sheet and ended up with an excel sheet with the following products and build numbers for easy reference:

VMware vSphere 4 Suite (combines several products)
VMware Infrastructure 3 Suite (combines several products)
Cisco Nexus v1000 (1.0)
VMware ESXi (4.0, 3.5, 3.0)
VMware ESX  (4.0, 3.5, 3.0, 2.5, 2.0, 1.5, 1.0)
VMware Server (2.0, 1.0)
VMware vCenter Server (4.0, 2.5, 2.0)
VMware vCenter Converter Standalone (4.0, 3.0)
VMware vCenter Lab Manager (4.0, 3.0, 2.5, 2.4)
VMware vCenter Site Recovery Manager (4.0, 1.0)
VMware vCenter Server Heartbeat (5.5)
VMware vCenter Lifecycle Manager (1.0)
VMware vCenter CapacityIQ (1.0)
VMware vCenter AppSpeed (1.0)
VMware vCenter Chargeback (1.0)
(more…)

May 21th VMware released their new flagship product VMware vSphere 4 which should bring us tons of new features and performance improvements.

But how is the vSphere experience almost 9 months later?

Starting with the installation and setup experience, my personal experience with vSphere is very good. During the installation and setup of VMware ESX or ESXi 3.x I experienced a lot of issues like BIOS settings causing HA issues, HA issues when changing the ESX IP addresses, Problems with VMware Update Manager and faulty HP USB sticks. We even created a HA checklist for you to easily address HA issues.

Once up and running ESX(i) 3.x ran fine with the occasional HA error which 99% of the time could be fixed by reconfiguring HA from Virtual Center.

Now with vSphere the installation and setup is simple, error free and straight forward. Setup HA in the cluster properties wait for all progress indicators to reach 100% and you’re done.

(more…)

Last week a colleague, who sells applications running on an Oracle Database, had some questions regarding Oracle and running it in a Virtual Machine (VM) on top of a VMware infrastructure with a customer.

1) How to license Oracle in a virtual environment?

I pointed him to an article about licensing the Oracle software in a virtual environment I wrote some time ago.

Oracle can namely be hard- and soft partitioned, where VMware, XenServer, Hyper V and Oracle VM are all marked as soft partitioning, while looking into the way Oracle VM can be hard partitioned I stumbled on the following how to do it:

There are two methods to pin virtual CPUs. You can use the xm command to pin a guests’s virtual CPUs or you can hardcode the CPU mapping in a guest’s vm.cfg file. The difference between pinning CPUs with xm and hard coding the CPU mapping in a guest’s vm.cfg file is the persistence of the CPU mapping. CPUs that are pinned with xm are not persistent between reboots. Hard coding the CPU mapping in a guest’s vm.cfg file is persistent between reboots. To comply with Oracle’s hard partitioning policy, you must hardcode the CPU mapping in a guest’s vm.cfg file.

(more…)

About two weeks ago I attended a session at the VMware User Group meeting here in the Netherlands about Project VRC.  After the presentation I asked myself: ‘What is the value of this project?‘.

For you who don’t know what Project VRC is:

“Project Virtual Reality Check (VRC) is a joint venture of Log•in Consultants and PQR, who have researched the optimal configuration for the different available hypervisors (hardware virtualization layers). The project arises from the growing demand for a founded advice on how to virtualise Terminal Server and Virtual Desktop (VDI) workloads. Through a number of researches, Log•in Consultants and PQR show you the scaling possibilities for Terminal Server environments as well as Virtual Desktops.” http://www.virtualrealitycheck.net/

Don’t get me wrong: What they did was a very good initiative, it showed the performance differences between different hypervisors. Although the results were not that surprising it was good to see the validation numbers of the things we already knew.

I also think that the guys who did the project where totally surprised by the attention vendors and customers gave to the project. It was an outstanding (marketing) tool to show the value of virtualization and especially XenApp on a hypervisor. Because of this attention the whole project got out of hand. Although this was not the goal of the project, vendors and customers used it as a reference guide for vitalizing XenApp. That’s the point where I started to wonder what the real value of the project VRC was.

(more…)

Based on the real life results when virtualizing XenApp I thought it was about time to summarize some of the best practices for virtualizing XenApp servers.

Why we DO want to virtualize XenApp?

1. For server consolidation:  vSphere enables scale up XenApp deployments;
2. For mixing server editions: 32-bit and 64-bit XenApp VMs can coexist;
3. For management: Better management through flexibility & isolation think about Change Management and VMware DRS;
4. For high availability and disaster recovery: VMware HA and vCenter Site Recovery Manager;
5. For less costs for server hardware, maintenance contracts, power, cooling, floor and rackspace.

Virtualizing XenApp servers is very complex. There are a lot more layers involved, like the type of hardware, the capabilities of the processor, the performance of the shared storage, the hypervisor used, the specific settings per hypervisor, operating system settings in a virtual environment, the XenApp settings in a virtual environment, the Workspace management settings in a virtual environment etc, etc.

In the following sections I tried to summarize some of the best practices we use in our projects:

(more…)

On a regular basis we have info sessions with our most important vendors.  Last week we had a session with HP to tell us more about virtualization in their hardware products. The session was especially targeted at Flex-10. Flex-10 is the way how HP breaks s a 2 x 10Gb Ethernet pipe into a flexible, easy to change, smaller Ethernet ports.

Why is this so important for us virtual friends? Of course it is a huge cost saver not only in hardware but also in management of the environment but the most important thing is that it opens up a lot of new virtual design opportunities.

.

One of the coolest things is that we now can make a design for up to 4 blade chassis with each physical 16 server blades and let’s say 320 virtual servers where all the traffic between the servers never leaves the blade chassis. It is all handled with the blade chassis. Also all of the vSphere traffic like VMotion and service console can be handled within the chassis at 10Gb speeds.

(more…)

Last night VMware has released Update 1 for ESXi 4, ESX 4, and vCenter server 4.

According to the release notes Update 1 includes the following improvements:

• Support for Windows 7 and Windows Server 2008 R2;
• Support for View 4;
• Support for 160 VMs per host in a HA cluster with 8 hosts or less;
• Increased vCPUs per core limit from 20 to 25;
• Paravirtualized SCSI support has been extended to Windows 2003 and 2008 boot drives;
• vDS performance improvements;
• Support for DB2 database;
• Improved support for Microsoft Clustering.

Besides this vCenter server now includes a pre-upgrade checker tool which enables you to proactively check ESX hosts for any potential issues that you might encounter while upgrading vCenter agents on these hosts as part of the vCenter Server upgrade process. You can run this tool independently prior to upgrading an existing vCenter Server instance. The tool can help identify any configuration, networking, disk space or other ESX host-related issues that could prevent ESX hosts from being managed by vCenter Server after a successful vCenter Server upgrade.

The release note can be found here.

vSphere 4 Update 1 can be downloaded here.

Since last week I’ve got a new assignment which is a long way from home. Next to the downsides of traveling 5 hours a day and staying in hotels, it certainly has advantages.

During my 5 hour drive or when I’m staying in a hotel i have time to listen to the VMware Community Roundtable podcasts I put on my iPhone. For those of you who don’t know this. VMware Community Roundtable is a weekly conference call/chat for VMware enthusiasts. Every week there’s a different topic and this is your change to discuss these topics with the experts in the community. For those of you who don’t have time to attend, there’s the possibility to listen online or download the sessions as podcasts.

Last week I listened to a great topic which was called the ‘#66 – iSCSI Super Friends with EMC, NetApp, Dell, HP, VMware‘. This podcast was from September 30 so it was quite an old podcast but this was such a great session that I don’t want to keep it from you. This session discusses the multi vendor blog post by VMware (Andy Banta), EMC (Chad Sakac), NetApp (Vaughn Stewart), Dell/EqualLogic( Eric Schott), HP/Lefthand Networks (Adam Carter) on how to implement iSCSI with VMware VI3.5 and vSphere 4.

So for those of you who already heard it, sorry for the ‘old’ intel, for those of you who haven’t, this is a must read/hear.

The mult vendor blog post discusses can be found here:

• Using iSCSI with VMware VI 3.x
• Using iSCSI with VMware vSphere 4
  

I really liked the conclusion that you can build iSCSI storage solutions which are as fast as fiber storage solutions and that tier 1, tier 2 and tier 3 storage definitions should not be based on the technique used but on the service level agreement with your end user.

Personally I wonder what the future will bring. Will fiber channel disappear in favor of iSCSI? As discussed during this podcast, ethernet is ideal for storage connections, the questions is which protocol to use, NFS, iSCSI or FCoE. We will see ……

Back in April we we’re the first to report the limited management and automation support in vSphere, but now VMware has released version 4.0 of vCenter Site Recovery Manager.

Besides that vCenter Site Recovery Manager can now be used with VMware’s vSphere 4 it has some additional new features and improvements, like:

• Support for NFS storage arrays;
• Support for Shared Recovery Sites;
• Support for VMware Fault Tolerance;
• Support for Distributed vSwitches;
• Maximum number of protected VMs increased to 1000;
• Graphical interface to advanced settings;
• Support for DB2 as an SRM database server;
• Fully compatible with Distributed Power Management.

Licensing remains to be socket based as it was the case with SRM 1.0

For more information visit VMware’s website or see the release notes.

Project Virtual Reality Check finally posted a new document about previous results and possible clock drift when using the “Login Virtual Session Indexer (VSI)”.  Previous test setups and results didn’t take into account how different hypervisors handle passing time.

In my opinion this is a serious setback to Project VRC which is considered an institute in the virtualization world. People will start questioning the results when no new tests will be performed.

Below is a description from the Project VRC website explaining the new whitepaper they published on September 14th 2009. This is a must read for people that already did some testing as well as new tests. In short: ‘Because of Windows clock behavior in virtual machines the results were affected and some hypervisors may come out better than they really are.

This whitepaper is a review and reflection on previous Project VRC publications, the benchmark: “Login Virtual Session Indexer (VSI)” and Windows clock behavior within virtual machines.  This discussion is fueled by the fact that results from the individual Project VRC whitepapers are set side-by-side to compare hypervisors. Project VRC has been in discussion with both vendors and community, and performed additional research in this context. Before Project VRC can publish new results, it is important to address any questions, review the impact of this discussion and improve VSI where possible.

You can download it at www.projectvrc.nl

The major conclusions in this Whitepaper are:

(more…)

After becoming a VCP4 I regularly get questions from my colleagues on how to become a VCP4.

Can I take the VCP410 exam without further training?
I attended the VI3, Install & configure course but didn’t take the exam yet. Can I take the VCP exam instead?

Maureen Lonergan wrote a very neat article on this, ‘Ahead of the learning curve’

In this article Maureen talks about the various road which lead to VCP4 certification. In short?
(more…)

I’m in IT for more then 12 years and during that period I learned, never to trust something another professional tells you. So as I am studying for my VCP410 exam, coming Friday, I came across the Virtual Machine configuration maximums. I saw the info at Simon Long’s blog, took his VCP vSphere 4 Practice Exam and also took notes.

When running through all configuration maximums I remembered the ‘never trust anyone‘ motto and as I’m in between project I thought it would be cool to check/confirm the presented maximums. Some seem so ridiculous that you can hardly believe them to be true.

After 10 minutes of editing the virtual machine configuration I got my ‘MAXVM‘ and I must say VMware delivers one awesome virtual machine. I can’t imagine anyone using a virtual machine which approaches these configuration maximums.

To sum it up:

(more…)

At VMworld 2009, which started yesterday, VMware launched two new products.

VMware GO and VMware vCenter Product Family.

VMware launched VMware GO which is targets small to medium sized businesses. VMware GO is a free beta service that makes it simple for clients to get started with virtualizing their applications. VMware Go is a web-based service which will let companies run multiple operating systems and applications on a single server. By doing so VMware helps SMBs to spend less money on hardware, energy and server administration. VMware Go beta will start next Monday and will be generally available in Q4 of 2009.

The second product, VMware vCenter Product Family, is actually a suite of existing VMware virtualization solutions . The suite is built on top of VMware vSphere 4 to help enterprises create and maintain dynamic and flexible IT infrastructures.

(more…)

On the site www.vReference.com I came across a post announcing the “vSphere 4 reference card”. Wondering what this was I started reading the post.

It seems that Forbes Guthrie made a document containing hard limits for the vSphere 4 products. I found the list of items very wide and should come in handy when looking for limits of the vSphere 4 products.

The reference card is refreshed every now and then, so check out the site periodically. Or subscribe to the RSS feed of the site.

Hopefully this card can help you as future reference. I found it to be very helpful.