How to set up VCB (VMWorld 2007 lab materials)

Posted on October 30th, 2007 in dr, esx, how to, vcb, vmworld by Rich

The file attached to this post is the VMWorld 2007 “Leveraging VMware Consolidated Backup for Disaster Recovery” lab materials. I am posting this for those that did not get to go to VMWorld and do not have an ID to log on to the VMWorld site.

This .pdf illustrates the requirements for VCB as well as the step by step technical details of using the VCB framework for backing up VMs, restoring VMs, and restoring files.

VCB for DR VMworld 2007 Lab

updated 01.29.08 - You can also download this lab from my Files Page.

vRanger Pro P2V-DR Module

Posted on October 29th, 2007 in dr, esx, fail over, vizioncore by Rich

Vizioncore: vRanger Pro P2V-DR Module

Vizioncore’s new P2V-DR module adds the ability to create backups of running physical servers on centralized Windows storage.

“The P2V-DR Module in vRanger Pro leverages the robust conversion engine of Vizioncore’s vConverter software. The cloning method employed by vConverter is executed at the “block-level” as opposed to “file-level” which results in extremely fast & reliable conversions with superior completion rates and no data loss.”

Unlike Ghost or other products that allow you capture an image of a server for bare metal restores, Vizioncore’s new module captures the server image while the server is live, and those images are converted for restoring the image to a VM. This sounds similiar to Platespin’s P2I (physical to image) conversions.

32 bit Linux VMware Server with more than 1 GB of RAM

Posted on October 28th, 2007 in how to, linux, treesum, vmware, vmware server by Rich

I run the free VMware Server on 32 bit Linux at home. I have it installed on PCLinuxOS 2007 - only because it was the distribution that I had loaded at the time. Before I installed VM Server I increased the server’s memory from 1 GB to 2 GB. Up until now I was only running a couple of VMs at a time and never really had any resource contention.

Just recently I decided to build some additional VMs, and to my surprise I noticed that the server was only showing 1 GB ram, and therefore VM Server only had 1 GB ram available for hosting guests. After some research I found the following article:

Linux.com :: Got more than a gig of RAM and 32-bit Linux? Heres how to use it

“Nowadays, many machines are running with 2-4 gigabytes of RAM, and their owners are discovering a problem: When they run 32-bit GNU/Linux distributions, their extra RAM is not being used. Fortunately, correcting the problem is only a matter of installing or building a kernel with a few specific parameters enabled or disabled.

Installing VMware Tools in Fedora 7

Posted on October 26th, 2007 in esx, how to, linux, vmtools, vmware, vmware server by Rich

It’s not as simple as in Windows VMs !

This guide is the combined instructions found from the guides at:

http://www.howtoforge.com/vmware_tools_on_linux

http://www.thoughtpolice.co.uk/vmware/howto/fedora-7-vmware-tools-install.html

I started with a fresh install of Fedora 7. I used the LiveCD and installed it to the VM hard disk. I did not apply the 210 package updates or the security updates. (Who says Linux doesn’t have be patched as often as windows?)

Note: I was unable to get the shared folders or the fast network driver feature to work. I’ve never been able to get these features working properly, but I’ve never really needed them to. The VMtools will load without these features anyways. I assumed that the sections for fixing the vmxnet module would finally make this work, but it did not. I might have done something wrong so I kept those sections in these instructions in case someone else gets it to work.

VMKernel Error Codes

Posted on October 23rd, 2007 in esx, how to by Rich

VMware Knowledge Base - New vmkerrcode Utility Displays VMkernel Errors

The following is a list of all vmkernel error codes in ESX 3.0.2. This list was generated by using the new vmkerrorcode utility.

To generate this list enter “vmkerrcode -l” at the service console.

If the table is hard to view on your monitor here is the .txt version.

Free VDI with 2X ThinClientServer

Posted on October 18th, 2007 in 2X, vdi, vmware by Rich

From the 2x.com web site:

Desktop Virtualization with 2X ThinClientServer and VMware

Desktop virtualization takes the headache out of desktop administration by increasing security, redundancy and scalability. With 2X ThinClientServer and VMware server you can run your desktops virtually on central servers, and use the client machines to connect to the virtual machines. Stream your company’s desktops and applications just like a video!

Benefits of Virtual Desktop computing with 2X ThinClientServer and VMware

  • Maintain and secure Windows desktops and builds and all connected hardware devices from one central location
  • Improve support by shadowing sessions and watching the user’s actions
  • Easy addition, recovery and replacement of virtual desktops
  • Centralize control by allowing you to remotely shutdown or restart all devices
  • Reduce costs by converting old PCs to thinclients with the latest XP or Vista
  • No Terminal Services CALs required – re-use existing Windows XP license.

What do I need to achieve this?

1. 2X ThinClientServer PXES edition - Cost: Free
2. VMware Server - Cost: Free
3. An OS, either Linux/Windows - Cost: Free (If re-using same license)

I am using the ThinClientServer at home.


I have VMware Server hosting both a Winodws server and an XP desktop. ThinClientServer is running on the server and is configured to allow a group of users to be assigned an RDP session to the XP VM. I have an old pc that I boot from CD (the ThinClient .iso) to connect to the ThinClientServer VM where my login is authenticated. Then I am able to log in to the XP desktop RDP session.

The old pc I am using has a 333mz cpu and 128 mb of ram. The XP VM is using my host’s 1800+ cpu and 512 mb ram. It works great! I did not have a hard drive for this pc or otherwise I could have permanently installed the thinclient OS. It’s a great solution! All that is missing is 32 bit graphics and DirectX!

There is also commercial edition that has full support. The free edition only provides support via their forums.

Let me know if you have tried 2X ThinClientServer in a production environment.

Maximums for Virtual Infrastructure 3

Posted on October 17th, 2007 in esx, vmware by Rich

Did you know that there are limits to VI3? VMware has published a .pdf explaining the maximum limits for the various objects and features in an ESX environment. Configuration Maximums for Virtual Infrastructure 3 can be found on the VMware Infrastructure 3 Documentation page.

Personally I’ve never noticed if I’ve hit one of these maximums so I’m curious to know if anyone has and how did you know it?

Here are some of the limits I would expect be the most likely to run into:

ESX NIC Teaming and VLANs

Posted on October 15th, 2007 in availability, cisco, esx, fail over, vmware by Rich

Every time I have to work with a customer’s networking engineers, or even my own Cisco consultants, I get funny looks when I have to tell them that there is not much to the nic teaming configuration on an ESX server.

Once a vSwitch is created it’s just a matter of assigning multiple physical NICs, creating port groups with the assigned VLANs, and setting the right policy. To the disbelief of the network guys, that can be done without adding any driver utilities or third party management software. After that ESX will load balance traffic headed out of the ESX host to the physical switch and provide redundancy for NIC fail over. Up to this point no changes to the switch are even needed.

On the physical switch side it does require more involved set up to provide inbound load balancing and setting up an ether channel. There are many guides already available on how to do this. Here are a few for reference:

ESX Server, NIC Teaming, and VLAN Trunking - blog.scottlowe.org

VMware ESX Server 3 802.1Q VLAN Solutions

To scale up or scale out?

Posted on October 14th, 2007 in availability, cluster, esx, fail over, vmware by Rich

When designing VI would you rather scale vertically or horizontally? That is, would you rather increase the number of VMs per ESX host, or increase the total number of ESX hosts in your environment?

A couple of years ago with ESX 2.X it was always about the consolidation ratio.

“How many VMs can I fit on a server that has 32gb of RAM?”

“What’s my ROI on a 16 CPU server?”

Even today a healthy percentage of clients maintain this strategy. Usually for the following reasons:

  • Rack space may be limited
  • VM application connectivity or performance may be maximized
  • VMs with large amounts of RAM and multiple cpus are needed.
  • Switch ports are limited

Now with the features of VI3 it’s more feasible, and sometimes more cost effective, to have many smaller servers as your ESX hosts.

“Should I use a Bladecenter?”

“How many servers will it take to consolidate my datacenter”

Clients who scale horizontally usually:

  • Have a dynamic environment with constant growth
  • Have a more restrictive annual budget.
  • Administer application “farms” spread across hosts (Citrix, Exchange, clustered or load balanced applications)
  • Have multiple network segments to put VMs on (DMZ, Development, Internet, contractor)

In my opinion VI3 facilitates a horizontal scale out strategy that makes more sense. Recent enhancements by hardware manufacturers are focusing on performance and availability for multiple sessions hosted on virtual servers without emulation. Dual core, quad core, Intel VT, AMD-V, and other emerging features make smaller servers more efficient and capable of hosting larger numbers of virtual machines. Assuming a VI design prevents a vmotion boundary, scaling horizontally also helps ensure host fail-over and availability to manage hardware problems or software updates without taking guest VMs offline.

Which strategy do you agree with or recommend, and why?

ESX 3.5 features announced!

Posted on October 10th, 2007 in esx, esx3.5, feature comparison, news, stor vmotion, vmware by Rich

Just when you thought the competition was catching up VMware does it again. Monday VMware announced the new features of the latest version of Virtual Infrastructure 3, which will be ESX 3.5 and VC 2.5. The new versions will be generally available later this year.

A description of the new features can be found in VMware’s news release

Here is the description of the new features from VMware’s announcement:

Virtualization platform enhancements help deliver new levels of performance, scalability and compatibility for running the most demanding workloads in virtual machines:

  • Expanded storage and networking choices such as support for SATA local storage, 10 Gig Ethernet, and Infiniband expand storage and networking choices for virtual infrastructure
  • Support for TCP Segment Offload and Jumbo frames reduce the CPU overhead associated with processing network I/O
  • Support for hardware nested page tables such as in processor assists for memory virtualization
  • Support for paravirtualized Linux guest operating systems enables higher levels of performance through virtualization-aware operating systems
  • Support for virtual machines with 64GB of RAM and physical machines with up to 128GB of memory

New virtual infrastructure capabilities help deliver increased infrastructure availability and resilience:

  • VMware Storage VMotion enables live migration of virtual machine disks from one data storage system to another with no disruption or downtime. VMware VMotion has become an indispensable tool for many infrastructure administrators to dynamically balance their server workloads and eliminate planned downtime for server maintenance. Storage VMotion extends VMotion to storage resources of a virtual machine, namely virtual disks. Using Storage VMotion, administrators can dynamically balance the storage workload and address performance bottlenecks by migrating virtual machine disks to the best available storage resource. Administrators can minimize service disruption previously incurred for upgrading storage arrays and free storage administrators to improve and manage the storage infrastructure without having to co-ordinate extensively with application and server owners.
  • VMware Update Manager automates patch and update management for VMware ESX Server hosts and virtual machines. Update Manager addresses one of the most significant pain points for every IT department: tracking patch levels and manually applying the latest security/bug fixes. Patching of offline virtual machines enforces higher levels of patch standards compliance than physical environments. Integration with VMware Distributed Resource Scheduler (DRS) enables zero-downtime VMware ESX Server host patching capabilities.

New virtual infrastructure management solutions help deliver increased automation for streamlined managed of IT environments.

  • VMware Distributed Power Management is an experimental feature that reduces power consumption in the data center through intelligent workload balancing. Working in conjunction with VMware DRS, Distributed Power Management is designed to automatically power off servers not currently needed in order to meet service levels, and automatically power on servers as demand for compute resources increases.
  • VMware Guided Consolidation, a feature of VMware VirtualCenter enables companies to get started with server consolidation in a step-by-step tutorial fashion. A wizard discovers physical servers, identifies consolidation candidates, converts them to virtual machines, and leveraging intelligently places them onto the best VMware ESX Server or VMware Server hosts. Guided Consolidation helps to make the consolidation process quick and easy for users with little knowledge of virtualization.

Design a clustered VM application that can fully leverage VMotion, DRS, and HA?

Posted on October 9th, 2007 in SAN, appliance, cluster, datacore, esx, iSCSI, lefthand, mscs, openfiler, storage, treesum, vmware, vsa by Rich

This post is more of an idea then a report. If you’ve experimented with a design similar to my thoughts below please post a comment and let me know!

Have you tried to configure VMs in a MS cluster across separate ESX hosts? How about clustering a physical server with a VM? VMware’s guide can be found here. Referencing this guide I am specifically talking about “Clustering Virtual Machines Across Physical Hosts (Cluster Across Boxes)” and “Clustering Physical Machines and Virtual Machines (Standby Host)”.

Read the guide and you’ll find there are several prerequisites and restrictions. The most important ones being:

  • you must use RDMs in physical mode for shared storage
  • dedicate at least 2 physical nics to the VMs
  • you can not use multipathing software
  • you must use the LSILogic virtual SCSI adapter in your VMs
  • you can only use 32 bit VMs. You can not cluster with 64 bit VMs
  • iSCSI disks are not supported. NAS disks are not supported.
  • you can only use 2 node clustering
  • the boot disks for the VMs must be on local storage
  • clustered VMs can not participate in an ESX cluster and use VMotion, DRS and HA

So how do we design a clustered VM application that can fully leverage VMotion, DRS, and HA?