A Primer on Virtualization
Virtualization is an essential component for any IT outfit looking to run an efficient, manageable, waste-not-want-not shop. It’s not just a tool for large call centers with big server farms. Even small- to medium-sized businesses with growing computer demands can benefit from virtualization.
Why? Virtualization reduces costs by lowering hardware needs and repetitive maintenance tasks. Often, scheduled maintenance on multiple servers and patching dozens of workstation computers requires IT staff to work after normal business hours when the hardware can be taken offline.
Even better, virtualization does not require an army of elite, top-shelf IT experts and a large cache of spare corporate funds to deploy. Sure, there is some initial layout of funds, and it must be operated by people who know what they’re doing. Still, virtualization can be implemented with out-of-the-box simplicity and a smidgeon of hand-holding from a software provider’s tech support crew.
“A misconception that many of our customers bring to us is that virtualization is new technology. It is actually very old. It started back in the mainframe days of the 1950s. Virtualization from its core is actually segregating space and separating processing power in order to run separate work loads,” Lew Smith, practice manager of virtualization solutions for Interphase Systems, told TechNewsWorld.
Virtualization 101
The actual term was born in the 1960s to refer to a pseudo or virtual machine. That process was created on experimental IBM mainframe computers to describe computing processes that ran in an induced virtual environment rather than directly on the metal and wires that comprised the computer. But unlike back then, the term “virtualization” no longer refers to exactly the same thing. The term does, however, ring true to its original definition.
Today, the term “virtualization” is used a bit more generically. It stands for one of several different methods and purposes for the virtualized environment. For instance, the concept is applied to three IT areas: network, storage and server virtualization. While these three categories may appear to be drastic different, they are fairly similar.
Virtualization got a foothold in the data center. From there, IT departments brought the concept to enterprise networks. Along the way, they applied related strategies to virtualization applications delivered to computers rather than the servers themselves.
“They separated the hardware and the software to eliminate hardware or appliance sprawl. Then this spread to the branch locations,” Gareth Taube, vice president of marketing for Certeon, told TechNewsWorld.
Virtual Differences
If you keep in mind that the ultimate purpose behind virtualization is to conserve resources, the three categories can be viewed as merely different approaches to achieving that same goal.
Network virtualization combines the available resources in an entire network by separating the available bandwidth into differently configured channels. Each one remains independent from the others and can be physically assigned to a particular server or device in real time. The end result is that the virtualization process tricks one network into behaving as separate manageable parts. Think of the same thing applied to partitioning a large hard drive into several smaller drives with their own identifying letters and content.
Storage virtualization pools the physical storage from numerous devices into what appears to be one storage device managed from a central console. This approach is typically found in storage area networks (SANs).
Servers, Servers Everywhere
Server virtualization was an early term that was often switched with the term “platform virtualization.” It masks server resources — things like operating systems, processors and physical identity — from the actual server users. This masking spares the user from having to understand and manage complicated details of server resources.
At the same time, the process increases resource sharing and utilization, allowing for expanded capacity. A control program, often called “host” or “guest” software, creates a simulated computer environment, or virtual machine.
Technologies differ for virtualizing data center servers versus enterprise networks, noted Hemma Prafullchandra, chief security architect at HyTrust. So matching needs to existing hardware is one of the first things to consider in selecting virtualization software.
“The virtual machine platform does not always provide application integration. The industry is still building tools to maximize use with virtualization platforms,” Prafullchandra told TechNewsWorld.
Software Basics
The process of setting up a virtualized environment is not as intimidating as it may sound. Basically, it is nothing more than installing and configuring a piece of software right out of the box.
“For the basics, the hypervisor is the core. This is the software that runs on the hardware and bridges the gap between the hardware and everything you’re going to run from an OS (operating system) and virtual machine perspective. It is a layer that sits on the ‘metal’ and brokers all the communications in and out and handles driver concerns,” Smith said.
The beauty of the process is that users can run any OS on top of the hypervisor. It gives better throughput, performance and portability, he noted.
“From the server consolidation perspective, I can take any OS I’m running and dump it onto any other piece of hardware that has that hypervisor running on it,” Smith explained.
More Is Better
One advantage to setting up virtualization is that users are not locked into one proprietary package. As long as the selected hypervisor runs on the hardware system, data created by the virtualized applications can be converted to another hypervisor product.
Some compatibility matrices exist, though. So you must be sure that your hardware meets the requirements of a particular hypervisor software, according to Smith.
The only precaution is in licensing, regardless of which hypervisor product is used. However, as long as legitimately obtained software is in hand, no legal entanglements exist.
“You need the license to run the virtualization layer on the hardware. You can convert the operating system from physical hardware to the virtual machine with the existing OS license. But you must remove the OS from the original hardware and remove the license key,” said Smith.
Some Choices
Many of these products run on both Windows and Unix/Linux. Documentation and tech support forums are available. The choices range from open source products with fully functional free versions through paid commercial versions. Keep in mind, however, that some full-fledged proprietary products may limit the ability to convert data to other products later on.
VMWare is perhaps one of the most well-known virtualization software makers in the market. VMWare also offers virtual appliances, which are virtual machines for download, sometimes for free. VMWare products are generally compatible with the Windows and Linux Platform s. There is also a version that runs on Mac OS X.
Xen is a lightweight open source hypervisor which runs on Intel or AMD x86 and 64-bit processors, with or without virtualization technologies.
Microsoft Virtual Server and Virtual PC are relatively new entrants into this software space. If you run only Windows desktops and servers, you may not need to look any further for virtualization software.
Parallels is one of the most widely used options for Mac computers. It was among the first to create commercial virtualization products that could run non-Apple OSes on Mac hosts. Parallels also runs on Windows and Linux hosts.
Other free or Open-Source choices include Qemu and FreeVPS.
VirtualBox is a general-purpose full virtualizer for x86 server, desktop and embedded hardware.
Setting up VMware Workstation on OpenSuse 11.0
Setting up VMware Workstation
From openSuse.org
| Full Link : http://en.opensuse.org/Setting_up_VMware_Workstation |
Introduction
VMware Workstation is a very popular proprietary virtual machine suite. There are other alternatives such as VirtualBox and QEMU (both open source software) which, unfortunately, are not as a feature rich as a VMware Workstation.
| This article explains how to install VMware Workstation 6.5.0 on openSUSE 11.0 and 11.1 beta 5. It may work on older/newer versions. |
Installing required packages
Before beginning the installation of VMware Workstation 6.5.0, you have to install the following packages:
- gcc
- make
- kernel-source
- kernel-syms
- linux-kernel-headers (this is probably already installed)
There are different ways of installing packages on openSUSE. For instance, you can use YaST or zypper.
Using YaST
Go to YaST -> Software Management. Search for the packages you need (one at a time) and select them by clicking on the checkbox.
Using zypper
Open the terminal, type the following as the root user:
zypper in gcc make kernel-source kernel-syms linux-kernel-headers
Starting the VMware installer
Once you have installed the aforementioned packages, you can proceed to run the installer. Before doing so, make it executable;
Note: this is an example, replace the version number with the one you have.
chmod +x VMware-Workstation-6.5.0-118166.i386.bundle
Then type (as root):
./VMware-Workstation-6.5.0-118166.i386.bundle
Running VMware Workstation
To run VMware Workstation on openSUSE, you can either click on the VMware Workstation icon or run it from a terminal.
from a Menu entry
There are two ways of doing running VMware Workstation from a menu entry;
- Click on the lizard, type vmware and click on VMware Workstation
OR
- go to lizard -> Applications -> System -> More Programs -> VMware Workstation
from a Terminal
Open a terminal and type
vmware
See Also
VMware vCloud Express?
The cloud express explained by David Davis, the Traing Signal Author of the vMware vSphere Video Training,
” vCloud Express is an Infrastructure as a Service (IaaS) offering delivered by leading VMware service provider partners. It provides reliable, on-demand, pay-as-you-go infrastructure that ensures compatibility with internal VMware environments and with VMware Virtualized™ services…………..”
Follow this link and you will have some more information about the Cloud Express, really worth watching.
MB
VCP!! Done and Dusted
Wow, finally got my VCP exam after a long time studying and playing with it. passed this last Friday and I got 419 which will allow me to continue if I wanted so. Now priority for sure is to Land a job on VMware and hopefully get more experience with this.
If you are plaing to pass your VCP, lots of videos and learning stuff are available at the VMware.com website and also the Simon long blog is one of the best to test your knowledge.
.
Study your way to VCP:
Study your way to VCP:
During my preparation for the VCP exam, I’ve came through a lot of sites that where really useful and I really thanks all the people who managed to get VMware VCP much easier.
All what you need to know about the vSphere.
Have a look at this article from vsphere-land.com about a must read in VMware vSphere.
One of my favourit website where I’ve started seriously learining about vSphere and ESX in general is at hypervisor.com; they have a wide range of video links, howto’s and much more about VMware and vSphere.
Scott Vessey is a VMware cetified Instrictor and his blog have a lot to talk about the exam and the preparation as well, worth having a look.
vSphere 4 Refrence card helped me a lot in learining the vSphere maximums which was partly the exam focus, have a look at Forbes at vRefrence.com.
Also a big thank to the Vladan who is lost in the Reunion Island for all his work on his website, lots of tutorials and news i’ve found intresting and I which him a good luck on his work.
London VMware Users Group (VMUG) – 24 November 2009
The London VMware Users Group (VMUG) will be held on the 24 November 2009,
Simon Gallagher (vinf.net) and Simon Seagrave (techhead.co.uk) will be presenting a session on putting together and running your own VMware vSphere home or work lab. This will cover most aspects of the implementation including real world advice, gotchas and a live demonstration using HP Proliant ML115 G5’s and shared storage ( iSCSI OpenFiler)
Surely I will be present this time as I’ve missed the last Users Group Meeting, I hope to meet new people and discuss more about VMware and the Virtualisation in general.
MB
Links for Hardware Compatibility List
I have been looking for some compatibility informations about some NIC cards that I’ve bought from ebay and got a chance to save these on my bookmarks and why not share it as well!!
Main Search Page
Systems Search Page
Storage/SAN Search Page
I/O Devices Search Page
Full Compatibility Guide
The Hardway to Study VMware
Hard way Study Tips:
1) Installed a lab environment at home. So that i could evaluate, test and get “hands-on” experience on vSphere. (2x ESX hosts + openfiler for shared storage) This is by far the absolute best way to learn about vSphere and get experience and knowledge about this great product.
2) Read and memorized the “vSphere documentation notes” (http://www.vreference.com/downloads/…4-notes1.0.pdf) and the “vSphere reference card” (http://www.vreference.com/downloads/…re4card1.0.pdf) from vreference.com. Many thanks to Forbes Guthrie for his excellent work on these pdfs.
3) Read the “VCP on vSphere4 Exam Blueprint” from VMware () to define what i had to learn to pass the exam. All questions, reflections and obscurity’s that i had on the content of the blueprint i looked up and read about in the main documentation set for vSphere. You can download this in pdf format or you can (as i did) search it in the online version found here WebWorks Help 5.0 . This is the definitive resource and answers all your questions.
good luck!!
Free VMware Workstation 7 Course
VMware are providing a free fundamental training for VMware workstation 7, you will need to have an account to register of course,
Follow this link and get started,
good luck
mb
Verifying that VT-x is Enabled and Locked at Boot
Verifying that VT-x is Enabled and Locked at Boot
Having had issues during the last few months regarding installing an ESX4 inside an ESX4, I cam across a solution which might have resolved my problem happily as ever, I have been fighting to get my ESX4 box to run on an other Hypervisor and this wasn’t that easy.
This is written by jmattson from the VMware Cummunity and I would really thank him for all this information,
Feel free to comment in any case,
“Intel first introduced VT-x on late-model P4 processors (codenamed Paxville). Many Core, Core 2, Core i7 and Core i5 processors are VT-capable (as are their Xeon-branded counterparts). However, some skus of these models are not VT-capable. (For example, the Q8200 Intel Core 2 Quad Processor is not VT-capable). You can check to see if your processor is VT-capable here. If your processor is VT-capable, “Intel Virtualization Technology” will be listed as one of the supported features.
On Intel CPUs, it is expected that the BIOS (or other firmware) will either enable or disable VT-x at boot, and will then lock the setting so that it cannot be subsequently changed without powering down the CPU. Note that VT-x must be both enabled and locked before software can make use of the VMX extensions. This operation must be performed for each core of a multi-core system, and for each thread of a multi-threaded system.
Because the VT-x setting is typically locked at power on, it is necessary to fully power down the system after changing any VT-x options in the BIOS. A simple reboot is not sufficient! After saving your BIOS changes, I recommend that you actually pull the power cord(s) out of the wall and wait ten seconds. For laptop systems, you may have to remove the battery as well.
Some BIOSes do not have VT-x enable/disable options. Some BIOSes with such an option fail to enable/disable VT-x on each core of a multi-core system or on each thread of a multi-threaded system. To verify that VT-x is enabled and locked on each core/thread of your system, download the attached ISO, burn it to a CD, and boot your host from the CD.
If the ISO reports that your CPU is not VT-capable, and your CPU should be VT-capable, you may have encountered an Intel chip erratum (possibly AW67 or AV69, depending on the CPU). The effect of this erratum is that some CPU features are reported incorrectly after a particular machine specific register has been updated by the BIOS. The solution to this problem is to obtain an updated BIOS from your system vendor.
If the ISO reports that VT-x is unlocked on one or more threads/cores, a workaround is available for current VMware hosted products. Simply add the following option to your system-wide configuration file:
hv.enableIfUnlocked = TRUE
On Linux systems, the system-wide configuration file is /etc/vmware/config. On Windows systems, the system-wide configuration file varies according to VMware product and Windows version. For VMware Workstation on XP hosts, the system-wide configuration file is C:\Documents and Settings\All Users\Application Data\VMware\VMware Workstation\config.ini. For VMware Workstation on Vista hosts, the system-wide configuration file is C:\ProgramData\VMware\VMware Workstation\config.ini. For other VMware products, adjust the path appropriately.
Note that this workaround can also be helpful if your BIOS fails to enable and lock VT-x when waking from hibernation. However, the ISO is not helpful in diagnosing this failure. If VT-x works after a power-cycle but fails after resuming from hibernation, then you should try the above workaround.
If your BIOS specifically disables VT-x and locks it in that state, then it is impossible to subsequently enable VT-x through software.
Note that VT-x is unavailable to normal software if you have enabled “trusted execution,” which restricts VT-x to “trusted” code. You should disable trusted execution in the BIOS and power-cycle the system.”
