Anda di halaman 1dari 13

Summary:

Similarly, in the mid-1990s when preparing to teach classes on the latest Windows server OSs,
a Microsoft certified trainer needed several computers to create the same mix of desktop
computers and servers he would encounter in the classroom.
Likewise, the Novell administrator and engineer classes of the mid-1990s required that you
pair a server and client computer at each desk, so students could experience setting up a
server and configuring a client to connect to that server.
As the 1990s ended and the new millennium began, virtu alization of operating systems
evolved, allowing us to run multiple o perating systems on a single computer.
The student experience changed, as instructors configured classes in which each participant
worked with on e or more servers and clients---all on a single PC.
Today, all you need in addition to specialized virtualization software to emulate hardware is a
computer with the processing power and enough RAM and hard drive space to suppo rt the
number, and types, of OSs you wish to run.
You also need appropriate licenses for all the software you run, including the OSs running in
the virtual machines.
In this chapter, we will explore the exploding phenomenon of OS virtualization, while preparing
you to install the desktop OSs desc ribed in this book into panies that have been around for
decades.
It is happening because desktop virtualization is going mainstream."
Explain the evolution of desktop virtualization and list the common features of today's desktop
virtualization products.
Select and implement a desktop virtualization option on a Windows Vista or Windows 7
desktop.
Describe desktop virtualization options for a Mac OS X desktop.
virtual machines (VM), which will save you the cost (and physical desktop space) of working
with multiple physical computers.
In this chapter we will examine the options available for hosting desktop VMs on Windows and
Mac OS X hosts.
In this section, we will define virtualization and many of the terms associated with it, describe
its background, and tell how it has led to the virtualization of desktop operating systems.
today it seems like virtualization is everywhere in the computing world, and there are many
types.
You can explore a virtual world, such as Second Life or VMware's vmworld (see Figure 3--1).
In a virtual world a user often selects an animated computer-generated human, or avatar, to
represent him or her within the virtual world.

Virtual worlds are used in online training, in marketing of products, and in games.
ed hard drives as though they are one.
involving a network addressing space that exists within one or more physical networks, but
which is logically independent of the physical network structure.
Then there is server virtualization, in which a single machine hosts multiple servers, each of
which performs tasks as i ndependently from the others as separate physical machines would.
Compani es that provide lowcost Web hosting services can create a separate virtual Web
server for each customer.
FIGURE 3--1 VMware's Virtual Pavilion showing Jane's avatar (JazzyYoda) walking into an
exhibitor's virtual booth single person.
This virtual desktop may reside on a server, allowing a user to access it from a computer with
specialized client software, or it may exist on the local computer.
Each individual virtual environment in both server virtualization and desktop virtualization is a
virtual machine---the software emulation of all hardware with which an operating system must
interact.
There is application virtualization, in which a user connects to a server and accesses one or
more applications rather than an e ntire desktop environment.
This chapter is devoted to today's desktop virtualization, but first we will look at the past.
Today's virtual machines have a very long pedigree--- they can trace their roots back to the
1960s when mainframe computer man ufacturers, such as IBM, routinely created multiple
discrete environments on a single computer.
A user connected using a dumb terminal that was little more than a keyboard and display with
a connection to a host computer (mainframe or minicomputer), but it had no native processing
power (hence the term dumb).
A dumb terminal would connect to the host computer, sendin g keystrokes, and displaying the
keystrokes and responses on the display.
Each user connected to a discrete area on the host called a partition.
A single terminal session could access each partition on a server.
Partitioning is the process or act of creating a partition.
The partition to which each user conne cted was not a true virtual machine, as today's virtual
machines are, but an area in which the user had access to programs and data.
This type of a partitioning of a mainframe computer's resources is different from the partitioning
of disk drives described in Chapter 1 and referred to later in this chapter.
After the advent of the IBM PC in the 1980s, a PC configured to emulate a dumb terminal often
replaced the dumb terminal.
For years, this model prevailed for those organizations that wished to have a centralized

system where all the programs and data resided, with the individual users connecting from
whatever served as a terminal.
seamlessly to partitions from their desktop PCs using terminal client software.
These were not, however, virtual machines because the entire hardware and operating system
environment was not part of the partition to which users connected.
They did not have a fully configurable desktop operating system, such as Windows, to work
with beyond their application and data.
In the past decade, many large organizations have adopted the thin client for their desktop
users.
A thin client is a low-cost PC, usually without such common peripherals as diskette drives (now
gone from most PCs), expansion slots, and optical drives.
The purpose of a thin client is to connect to a server, allowing the user to work in a serverhosted environment.
In place of a full-featured operating system as its host OS, a Type I hypervisor has software
that has as its sole purpose the interaction with the physical computer for support of virtual
machines.
The term x86 applies to a PC (processor, motherboard, and other components) that conform to
the Intel 32-bit x86 specification and can run 32-bit software.
provides the entire OS experience and working applications it becomes a virtual desktop, or a
full virtual machine.
This virtual machine may reside on a server and be accessed by a client computer (thin or
not), or it may reside on a desktop computer.
This allows the interactive user (the one sitting in front of that computer) to switch between the
host OS, the operating system installed directly on the computer, and one or more guest OSs,
the operating systems running within a virtual machine.
The term used today for hosting and managing multiple virtual desktops on network servers is
virtual desktop infrastructure (VDI).
The term is attributed to VMware in distinguishing its virtual deskto p server products from the
products offered by competitors, specifically Citrix and Microsoft products that did not provide a
full desktop environment.
Today VDI applies to any server product that provides the full virtual desktop support.
A hypervisor, also called a virtual machine monitor (VMM), is the software layer that emulates
the necessary hardware on which an operating system runs.
The hardware virtualization allows multiple operating systems to run simultaneously on a
single computer, such as a network server.
Each hypervisor normally emulates a computer separate from the un derlying computer, but it
must use a virtual processor compatible with that of the un derlying machine---mainly either an
Intel processor or an AMD processor.

There are two types of hypervisors, Type I and Type II.


A Type I hypervisor---sometimes called a bare-metal hypervisor---can run directly on a
computer without an underlying host operating system.
A Type II hypervisor requires a host operating system.
Bare-metal hypervisors first appeared on high-powered servers.
While it may have been possible to run one of these on desktop computers, until recently
these computers lacked the hardware support required for virtualization of some hardware.
Of course, that was not a big hurdle, and now bare-metal hypervisors have been introduced, or
at least announced, by the major hypervisor manufacturers---notably Citrix and VMware.
Citrix's XenClient is a Type 1 hypervisor targeted at laptop s.
Announced in July 2010, Citrix offers a free evaluation version, XenClient Express, at its Web
site, www.citrix.com.
Most hypervisor products for the desktop today are still Type II, and the hypervisors we discuss
in this chapter are all Type II hypervisors requiring an underlying operating system.
Whatever hypervisor you use for hosting, you will find more and more organizations deploying
server-based virtual machines that are the users' everyday work environment.
The reason for this is easier central management of the operating systems and user
environment.
While most of these virtual machines will continue to be hosted on servers, there may be a
trend by late 2011 of corporations moving to desktop- or laptop-hosted Type 1 hypervisors.
You have several choices for Type II hypervisors for desktops, but today some of the newer
ones run only on computers with hardware-assisted virtualization features, which means they
require a co mputer with either the Intel Virtualization Technology for x86 (Intel VT-x) or AMD
Virtualization (AMD-V) architecture extensions, which improve the performance of virtual
machines on the host.
You can install a Type II hypervisor on your desktop and test another operating system without
the expen se of a separate computer.
There are several choices of desktop Type II hypervisors, depending on both the hosting OS
and the desired guest OSs.
The ones we will discuss in this chapter all have several things in common.
to create a virtual machine, the order in which you do them, and how the host and guest OS
share the mouse and keyboard.
1. Prepare the computer by taking a few cautionary actions: Confirm that the computer's
hardware and operating system meet the minimum requirements for the hypervisor you intend
to install.
Back up your hard drive in case something goes wrong.
You have several options---both commercial and free---for running Linux, DOS, or Windows on

a Windows desktop computer.


At this writing you cannot run any version of Mac OS X in a VM on a PC, due more to licensing
issues than technical issues.
The hypervisors we describe here are free.
Two are from Microsoft, one is from VMWare, and one is from Oracle.
Unlike other software publishers that offer free desktop virtualization software, Microsoft does
not require that you register with it to acquire a Microsoft hypervisor, nor does it require that
you use any type of key to make it work.
However, the installation program will verify that your host OS is a legitimate version of
Windows before the Microsoft virtualization products will install.
The hypervisors we will explore here are Microsoft Virtual PC, Windows XP Mode, Windows
Virtual PC, VMware Player, and Oracle VirtualBox.
Microsoft Virtual PC 2007, as its name implies, is an older version of Microsoft's hypervisor.
It will install and run on certain editions of Windows XP, Windows Server 2003, and Windows
Vista.
You can create VMs and install other versions of Windows, Linux, and DOS.
An impor tant distinction between Microsoft Virtual PC 2007 and its successor, Windows
Virtual PC (discussed next), is that Virtual PC 2007 does not require a CPU that supports
hardware virtualization, but Windows Virtual PC does require this support.
1. Host OS: Windows Vista Business; Windows Vista Enterprise; Windows Vista Ultimate
(Windows Vista must have at minimum Service Pack 1); Windows Server 2003, Standard
Edition; Windows Server 2003, Standard x64 Edition; Windows XP Professional; Windows XP
Professional x64 Edition; or Windows XP Tablet PC Edition.
3. Processor: AMD Athlon or Duron, Intel Celeron, Intel Pentium II, Intel Pentium III, Intel
Pentium 4, Intel Core Duo, and Intel Core2 Duo.
4. RAM: Add the RAM requirement for the host operating system that you will be using to the
requirement for the guest operating system that you will be using.
If you will be using multiple guest operating systems simultaneously, total the requirements for
all the guest operating systems that you need to run simultaneously.
5. Disk space: To determine the hard disk space required, add the requirement for each guest
operating system that you will install.
If you are unsure of the edition of Windows or the system type of your computer (32-bit or 64bit), open the Start menu, right-click on Computer, and select Properties.
If you are thinking that you would like to run Virtual PC 2007 on your Windows 7 computer that
does not have hardware supp ort for virtualization, you are in luck as long as you don't mind
doing some research on exactly how to achieve this.
Download Microsoft Virtual PC 2007 warned that while it is possible to do this, Microsoft does
not officially support it.

open a search engine and search on "Virtual PC 2007 on Windows 7."


You may find a more recent article with updates.
The term x64 (or x86-64) refers to a PC (processor, motherboard, and other components) that
conform to the 64-bit architecture required to run 64-bit operating systems and applications.
You can download Virtual PC 2007 from the Microsoft site.
This requires a high-speed broadband connection, but the 30 MB file should take only a
minute or two to download.
1. Use a search engine to locate the Microsoft download site for Windows Virtual PC 2007.
At this time the site offers Microsoft Virtual PC 2007 SP1 (Service Pack 1) for Windows Server
2008, Vista SP1 and Windows XP SP3, but you may find an even newer update available.
2. Select the appropriate architecture version for your operating system (32-bit or 64-bit), and
begin the download.
3. Verify that the file, presently named "setup.exe," was saved to the Download folder or to the
location you selected.
4. You are ready to install Virtual PC 2007 on your Windows computer.
Using the file you downloaded in the Try This!
on the previous page or a file provided to you by your instructor, install Microsoft Virtual PC
2007 on your Windows XP or Windows Vista computer.
For our example, we will use Windows Vista.
This will start the Microsoft Virtual PC 2007 Wizard.
Click Next on the Welcome page and follow the instructions.
You will need to accept the License Agreement.
Enter the Username (this does not need to match your user account name) and Organization
information in the Customer Information page.
Notice that Microsoft automatically entered the Product Key on this page, and grayed it out, so
you cannot change it.
minimum of 2 GB of RAM installed.
Click Next on the Customer Information page and on the Ready to Install the Program page.
Notice the location in which the program will be installed.
You will normally allow it to install in the default location, but if you need to change this, click
the Change button and browse to another location.
When you are ready to have the installation begin, click the Install button.

The Installing Microsoft Virtual PC 2007 page shows the status of the installation with a
progress bar.
When the installation is complete, the Next button will become active; click it to proceed to the
Installation Comple te page.
Click the Next button when the progress bar shows that the installation is complete.
On the Installation Complete page click Finish.
Verify that Virtual PC was installed by clicking Start | All Programs.
Virtual PC will be highlighted as a new program.
As with any hypervisor, once you have installed Vir tual PC 2007, the next step is creating a
virtual machine appropriate for the first operating system you wish to install.
Begin by launching Virtual PC 2007 from Start | All Programs.
This launches the New Virtual Machine Wizard.
On the Welcome page click the Next button.
On the Options page, there are three choices, as shown in Figure 3--4.
The first choice lets you c reate a virtual machine, allowing you to customize the configuration
beyond the bare minimum for the operating system you will install.
This includes both the virtual machine (saved in a .vmc file) and the virtual hard disk (saved in
a .vhd file).
We prefer to use this when creating a virtual machine.
The second option is quicker, but creates a virtual machine with the default settings, but no
virtual hard disk.
You would choose this if you wanted only a minimall y configured virtual machine and will use
a previously created virtual hard disk.
The third option lets you add a preexisting virtual machine, which means you need an
existing .vmc file.
If you select the first option to create a virtual machine and click Next, the Virtual Machine
name and Location page appears.
En ter a meaningful name---such as the name of the OS you plan to install, as shown in Figure
3--5.
Use the Browse button only if you want to specify a location other than the default location.
Click Next, and in the Operating System page select the operating system you plan to install.
Figure 3--6 shows this page with the dropdown box open and displaying the list of supported
Guest OSs.
Select Other if you wish to install DOS or Linux.

Select an OS and click Next to proceed to the Memory page.


On this page, you may either keep the default setting for the selected OS or choose to adjust
the amount of RAM used by the virtual machine and click Next to move to the Virtual Hard Disk
Options page.
You will need the distribution disc for the OS you wish to install.
an OS installation, open Virtual PC from the Start Menu, which now opens the Virtual PC
Console.
From there, you install the OS just as you would on a physical machine, following the
instructions in the setup program.
For larger organizations Microsoft recommends the Microsoft Enterprise Desktop Virtualization
(MED-V), which is server-based desktop virtualization.
Run the Hardware-Assisted Virtualization Detection Tool, available separately from the
Microsoft Web site, or you can wait and let it run automatically when you initiate a download of
Windows Virtual PC from there.
Like Windows Virtual PC, VMware Player allows you to launch VM-hosted programs from the
hosting OS---even from the Start Menu.
Oracle VirtualBox may be the most versatile of the free virtual machine products available at
this writing because it comes in versions for a variety of host operating systems including
Windows, Linux, and Mac OS X.
Like the other free VM hosting software discussed here, it will run guest versions of Windows,
Linux, and DOS.
And like Microsoft's Virtual PC 2007, Oracle Virtu-alBox will run on hardware that does not
support virtualization, so it is yet FIGURE 3--9 Download the trial version of VMware to test it
before deciding to buy it.
another choice for older computers without hardware virtualization support.
Because this is available for the Mac, we'll leave our discussion of VirtualBox for the next
section.
The most compelling reason for using virtualization software on a Mac is to run Windows to
access certain Windows apps that aren't available for the Mac OS.
There are several options for doing this, including Apple Boot Camp, VirtualBox, and Parallels.
Apple Boot Camp is more of a multi-boot solution, but VirtualBox and Parallels offer
virtualization on the Apple desktop.
Parallels is a commercial product, and you can learn a bout it at www.parallels
Apple Boot Camp is available with Mac OS X.
It is a multi-boot option, meaning it allows you to install Windows onto a separate disk partition,
and then you can choose to boot into either OS.

This is an either-or situation; you need to restart to change from one OS to the other, but you
can run both OSs.
The advantage is performance---each OS is running directly on the Mac with no performance
loss from being in a virtual machine.
FIGURE 3--10 Print the Installation and Setup Guide before proceeding.
The keyboard and mouse or trackpad that came with your computer.
(Alternatively, use a USB keyboard and mouse.)
A built-in optical disk drive or a compatible external optical drive.
A Mac OS X version 10.6 installation disc.
Professional with Service Pack 2 or later (32-bit version only); Windows Vista Home Basic,
Home Premium, Business, or Ultimate; Windows 7 Home Premium, Professional, or Ultimate.
Boot Camp comes with Mac OS X.
Before running the Boot Camp Assistant, back up your Mac because the first step requires that
you create a new partition for the Windows OS.
To begin the installation, run the Boot Camp Assistant program from the Applications | Utilities
folder.
Notice that the first page, seen in Figure 3--10, gives you the option to print the Installation and
Setup Guide for Boot Camp.
After you have printed the Guide, click Continue.
Boot Camp Assistant first has you create a partition on which to install Windows.
This is especially important because you are not likely to have a second physical hard drive in
a standard iMac or M acBook.
That also means you should decide how big a partition you wis h to have for your Windows
OS.
Remember that you will be installing ap plications into Windows, so you will need a bigger
partition than t he minimum recommended for the version of Windows you plan to install.
For instance, when installing Windows 7 on an iMac with a 500 GB hard drive, we considered
the minimum requirements for the OS itself (16 GB for 32-bit or 20 GB for 64-bit) and then we
considered the requirements of the various applications we wish to install and the data we will
generate (unless it is being saved to a server).
Considering these needs, and the overall hard drive space, we decided to create a partition of
100 GB, as Figure 3--11 shows.
and drag the dot between the two spaces.
The iMac described here already contained a single partition using up its entire usable space,
but Mac OS X can repartition such a drive, creating two partitions out of one without losing
data.

Those of us with decades of experience partitioning hard drives in DOS and Windows cringe at
partitioning an alread y fully partitioned drive, but it works.
The next screen prompts you to provide the Windows disc.
Once created, the partition appears as another drive device in Finder, as shown here.
Oracle VirtualBox will run on a variety of host operatin ing Windows, Linux, and Mac OS X.
Like the other free VM ware discussed here, it will run as guest versions of Windows, Linux,
and DOS.
It will also run on hardware that does not support virtualization.
Once you have downloaded the disk image file, when you are ready to install VirtualBox,
simply double-click on the VirtualBox disk icon on the desktop, shown here.
The Boot Camp partition appears with other drives under Devices in Finder.
You can download VirtualBox for Mac OS X from the VirtualBox Web site.
This requires a high-speed broadband connection, but the 30 MB file should take only a
minute or two to download.
2. On the home page locate the Downloads link and click it to navigate to the Downloads page.
3. On the Downloads page locate the link next to the latest version of VirtualBox for OS X
Hosts and click on it.
This action selects the disk image file (a file with a "dmg" extension) for Mac OS X. (See
Figure 3--12 on the next page.)
4. This will first open a dialog box asking if you want to open the file or save it.
Select Save File, which will automatically download, showing the progress.
5. You now have a disk image from which to install VirtualBox.
Using the file you downloaded in the Try This!
or a file provided to you by your instructor, install Or acle Virtual Box.
The instructions provided are for installing it into Mac OS X, but the instructions are nearly
identical when installing on a Windows PC, although you will work from a downloaded
executable or ISO file on a PC, and here we begin with a disk image file (.img).
Locate and double-click the VirtualBox disk image on the desktop.
If you wish to read the documentation, open the UserManual.
Also, note that the VirtualBox Uninstall tool is located here, for when you decide you do not
need this program.
minimum of 2 GB of RAM installed.

account for this computer (even if you are logged on as an administrator, you will need these
credentials to install new software).
To start the VirtualBox installation, double-click on the VirtualBox.mpkg icon.
At first it runs a test to verify that the computer can support VirtualBox.
Follow the instructions and proceed through the pages, including reading and accepting the
software license agreement, after which you can either accept the defaults for a standard
install or select a different destination and installation type.
In a very short time the installation is complete, and you will find VirtualBox listed in
Applications.
Launch the program from there to create your first virtual machine from the management
console.
Click the blue icon labeled New and the New Virtual Machine Wizard will guide you through the
creation of a virtual machine.
This process does not require the guest OS, but you do need to know which OS you will install
into the virtual machine you are creating.
Y ou are simply configuring the machine to accept the guest OS.
When prompted to name the virtual machine, use a meaningful name, such as the name and
version of the OS you plan to install.
Then select the OS you will install and continue.
On the Memory page select the amount of base memory, initially accepting the default and
continuing.
On the virtual Hard Disk page ensure that you selected Boot Hard Disk and Create a new hard
disk.
This will launch the Create New Virtual Disk Wizard.
Continue through this wizard, selecting the Dynamically expanding storage type.
After you install an OS you will probably be disappoint ed in how the desktop appears within
the virtual machine and you may notice that certain features, such as the network adapter, do
not function.
This is because all hypervisors require that you install additional programs and drivers for the
OS to appear and to work well in the VM.
Virtualization had its roots in the dumb terminalmainframe systems of the 1960s and the
terminal service-terminal client systems of the 1990s.
1. In which type of virtualization does a user connect to a server and work within a program,
without an entire virtualized desktop environment?
2. What term describes the hosting and management of multiple virtual desktops on network
servers?

Type I hypervisor c. Virtual PC 2007 d.


4. What term has two definitions that have been described in this book---first, as the space
reserved for a terminal session on a mainframe or minicomputer, and, second, as a portion of
a physical disk allocated for use by a file system?
software on a PC to connect to a specialized server or minicomputer.
is a low-cost PC, usually without such common peripherals as diskette drives (now gone from
most PCs), expansion slots, and optical drives, and is used to connect to a special
environment on a server that could be simply a partition or a virtual machine.
5. What type of hypervisor would you install on a Windows host OS?
6. If you wanted to run Windows XP on an iMac with OS X 10.6, which option would give you
the best performance?
7. Which free hypervisor, studied in this chapter, runs on Windows, Mac OS X, and Linux
OSs?
8. You upgraded your four-year-old PC to Windows 7 and you would like to install a hypervisor
so that you can run and test Linux applications.
A test shows that your computer does not support hardware-assisted virtualization.
Which of the following can you install on the PC that will work for your purposes?
Windows Virtual PC c. Virtual PC 2007 d.
9. Which of the following solutions should you select if you wish to run a Windows guest on
Mac OS X 10.6, but you need frequent access to both the host and guest OSs?
10. Which of the following will release the mouse from the control of a virtual machine?
11. Which of the following is synonymous with hypervisor?
Bare metal c. Virtual hard drive d.
1. What is the purpose of each the two most important files created by a Type II hypervisor
when preparing a new virtual machine?
2. Explain the significance of the Intel VT-x and AMD Virtualization architecture extensions.
3. Explain why an IT person would want to use a Type II hypervisor on a desktop computer.
12. Your PC has an AMD processor installed that includes AMD-V technology and the
motherboard fully supports this processor.
Which is the most capable version of a Microsoft hypervisor you can install on this machine,
provided the computer has all the requirements?
Windows Virtual PC c. Windows XP Mode d.
13. What legal issue must you consider when installing a guest OS in a hypervisor?
Antivirus c. Licensing of guest OS d.

14. After downloading VirtualBox to an iMac with Mac OS X 10.6, which of the following is the
name of the object you should double-click to install VirtualBox on your computer?
15. Which of the following is a multi-boot option for running Windows as a second OS on a
Mac OS X 10.6 computer?
Windows Virtual PC c. Windows XP Mode d.
4. Why is there (at this writing) no hypervisor for running Mac OS X on a Windows PC?
5. You have Windows XP Mode installed on your Windows 7 computer, and you would like to
do a side-by-side comparison of Windows XP Mode and Windows XP in a VirtualBox VM.
What precautions should you take and how many computers are required for this comparison?
Find out how virtualization is being used in an organization in your area.
Arrange an interview with an IT manager, network engineer, or other knowledgeable IT staff
person from an organization in your area.
If you installed a hypervisor on your computer, find another one that will run on your OS.
Uninstall the first one without removing the virtual machines created for that hypervisor; install
the second one.
Find out the latest about Type I and Type II hypervisors.
Browse the Internet using the keyword virtualization and watching for recent articles and news
or medical clinic because privacy laws require that they meet certain minimum standards in IT,
and they often have the best IT staff in a community.
Ask if they are using virtualization, and if so, what type?
What are their future plans for virtualization?
new hypervisor work with the virtual machines you created with the first one?
Decide which one you prefer working with.
If it is the second, then keep it; if you preferred the first one, uninstall the second and reinstall
the first.
Consider turning on Google alerts with the key term virtualization.
Watch the number of alerts you receive over just a period of a few days.

------------Summarized by Copernic Summarizer

Anda mungkin juga menyukai