USING "HYPER-V" IN "WINDOWS 8.." TO RUN "VIRTUAL MACHINES"

(1)

1

USING

"HYPER-V"

IN "WINDOWS 8.." TO RUN

"VIRTUAL MACHINES"

(2)

2

Web location for this

presentation:

http://aztcs.org

(3)

3

SUMMARY

If you run the 64-bit version of

"Windows 8 Release Preview"

in your real computer, you can

run the bundled "Hyper-V"

program to create "virtual

machine" computers, in order

to save money, space, and

(4)

4

SUMMARY (continued)

In the near future, if you run the

"Windows 8 Pro" version or

"Windows 8 Enterprise" version

of "Windows 8", you can run the

bundled "Hyper-V" program to

create "virtual machine"

computers, in order to save

money, space, and time.

(5)

5

3 Virtual Machines

Running in "Hyper-V"

running in my real

"Windows 8 Release

Preview" computer!

(6)

(7)

7

EXPLANATION

(8)

8

Upstream to the real Internet

Real Physical

Computer running "Windows 8

Release Preview 64-bit"

Start with your real physical computer

(9)

9

"Hyper-V" Virtual Machine Program

Upstream to the real Internet Upstream to the real Internet

Real Physical Computer running "Windows 8.."

Activate the free "VMware Player" virtual machine program in

"Programs and Features" in the "Control Panel" of "Windows 8.."

(10)

10

Upstream to the real Internet Upstream to the real Internet

Virtual External Network Switch

Create a virtual "External Network Switch" using the "Hyper-V"

(11)

11

Blank Virtual Machine

with no Operating System

Use the "Hyper-V" program to make an empty virtual machine

(12)

12

"Windows 7.." Virtual Machine

Get into the empty virtual

machine program and install "Windows 7 Enterprise Trial 64-bit" into it.

(13)

13

"Windows 7.." Virtual Machine

with No Operating System

Use the "Hyper-V" program to make a second empty virtual machine.

(14)

14

"Windows 8" Virtual Machine

"Windows XP" Virtual Machine

Hyper-V's External Virtual Network Switch

Real Physical Computer running "Windows 8.." Get into the empty virtual

machine and install "Windows XP" into it.

(15)

15

Real Physical Computer running "Windows 8.." Use the "Hyper-V" program

to make a third empty virtual machine

(16)

16

Real Physical Computer running "Windows 8.." Get into the empty virtual

machine and install "Ubuntu 12.04" into it

"Ubuntu 12.04" Virtual Machine

(17)

17

Real Physical Computer running "Windows 8.." The end result is three virtual

machines and a virtual network switch inside a real "Windows 8.." computer

"Ubuntu 12.04" Virtual Machine

(18)

18

View of the three virtual machines from "Windows Explorer" in the real, "Windows 8" host computer:

(19)

19

View of the three virtual machines from "Windows Explorer" in the "Windows XP" virtual machine:

(20)

20

View of the three virtual machines from "Windows Explorer" in the "Windows 7" virtual machine:

(21)

21

View of the three virtual machines from the "Nautilus" file manager applet in the "Ubuntu 12.04" virtual machine:

(22)

22

More Explanation of the Demo

• A virtual machine running

“Windows 7 Release Preview" is running inside my real computer. • A second virtual machine running

"Windows XP Professional" is also running inside my real

(23)

23

More Explanation of the Demo

• A third virtual machine running "Ubuntu 12.04" is also running inside my real computer.

(24)

24

More Explanation.. (continued)

• The three virtual machines

and my real host computer are

all sharing files with each

other, using the virtual external

network switch that "Hyper-V"

has provided.

(25)

25

OBJECTIVES FOR USING

VIRTUAL MACHINES

1. Save real money

2. Save real space

3. Save real time

(26)

26

STRATEGIES FOR OBJECTIVE 1 TO SAVE MONEY

• You can use "virtual machines" to reduce the number of physical computers that you operate and this can help you to avoid buying additional computers:

(27)

27

STRATEGIES FOR OBJECTIVE 1 TO SAVE MONEY (continued)

• Thin Provisioning of hard drives: Virtual machines can help you to

avoid buying more hard drives

because, by default, they are set up to "fool" their guest operating systems into "seeing" more hard drive space than is actually

(28)

28

– In a virtual machine system, each guest operating system can be

"shown" a much larger amount of hard drive space than is actually

utilized by it, but the actual usage of physical hard drive space is just the "used" space--not the "free space“ that the virtual machines “see”.

(29)

29

–When you use virtual machines in free "virtual machine programs", it is like getting a pile of computers to use for free with all of them

residing inside your existing physical "host" computer.

(30)

30

–You can use a virtual machine to

attempt to repair failed hard drives.

•See

http://aztcs.org/meeting_notes/ winhardsig/harddrives/repairin g/030-HDsoftrepairs.pdf

(31)

31

– You can easily run software that normally conflicts with each other

or slows each other down (such as multiple versions of “Microsoft Office”) in separate virtual

machines so that they do not "see" each other.

(32)

32

–You can test beta software such as the prolific "Mozilla Firefox" betas

without causing permanent problems with the production version of the

same software, since many betas inactivate or remove the existing production version of the same program.

(33)

33

STRATEGIES FOR OBJECTIVE 2 TO SAVE SPACE (CONTINUED) • With virtual machines, you no

longer need to keep older

computers around in order to run those beloved MS-DOS games or to run prior year versions of

income tax software or old

versions of financial software

such as "Quicken“, "QuickBooks“ or “Turbotax”.

(34)

34

STRATEGIES FOR OBJECTIVE 3 TO SAVE TIME

• You can

clone existing "virtual

machines" in a fraction of the

time

that it takes to set up,

“reload”, or “re-image” real,

physical computers.

(35)

35

STRATEGIES FOR OBJECTIVE 3 TO SAVE TIME (continued)

• If you use a cloned "virtual

machine" for accessing the Web

and it catches a

virus/malware/trojan, you can

delete the cloned "virtual

machine" and create a fresh new

one in tens of minutes

.

(36)

36

ADDITIONAL BENEFITS OF VIRTUAL MACHINES

• All virtual machine programs provide you with "virtual

networks":

–By default, the "virtual

networks" give you an extra measure of security when

you are accessing Web sites on the Internet.

(37)

37

IMPLEMENTATION

• PROJECT 1:

Compare "Hyper-V" to other "Virtual

Machine Programs” to decide if it meets your needs

• PROJECT 2:

Install the “Hyper-V” program into your

"Windows 8 Release Preview" computer.

• PROJECT 2A:

Create a Virtual "External Network Switch" using the "Hyper-V" program

• PROJECT 3:

(38)

38

IMPLEMENTATION (continued)

• OPTIONAL PROJECT 4:

Do “Physical to Virtual" ("P2V") to convert an existing computer(s) into virtual

machines that will run inside the "Hyper-V" program

• PROJECT 5:

(39)

39

PROJECT 1 DETAILS

(COMPARE "HYPER-V TO OTHERS..")

• "Project 1" from the standpoint of

software for an organization or

business

compared to

"Project 1" from the standpoint of

(40)

40

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS)

• "Project 1" for an organization or

business: In order to select the "virtual machine

program" that is best for a "Windows 8.." end-user computer in a business or a not-for-profit organization, you should

compare the capabilities of the Windows 8's bundled "Client Hyper-V" program to

"VMware Workstation”, "Windows Virtual PC", and "Microsoft Virtual PC 2007".

(41)

41

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS..)

o "Oracle VM VirtualBox” is not a viable alternative for an organization because Oracle does not offer a way for you to legally purchase it for your organization or business.

o "Windows Virtual PC" is available for free in any end-user computer that is running "Windows 7 Professional" (or higher). It has no usage restrictions:

You can use it for your organization or business.

(42)

42

PROJECT 1 DETAILS

o "Microsoft Virtual PC 2007" is available for free in "Windows XP Pro" (or

higher) or "Windows Vista..". It has no usage restrictions: You can use it for your organization or business.

(43)

43

PROJECT 1 DETAILS

o See

http://en.wikipedia.org/wiki/Windows_Vi rtual_PC

(44)

(45)

(46)

(47)

(48)

48

PROJECT 1 DETAILS (continued)

(COMPARE "HYPER-V” TO OTHERS)

• In a business or any type of

organization (where "Oracle VM VirtualBox" and "VMware Player" cannot legally be used for free), "Hyper-V" will have a compelling advantage in cost (since it is

"bundled in with "Windows 8 Pro and Enterprise") relative to non-free

virtual machine programs such as "VMware Workstation".

(49)

49

• On May 14, 2012, Paul Thurott stated that the cost of upgrading from the

"Windows 8" edition of "Windows 8" to the "Windows 8 Pro" edition of

"Windows 8" will be about $15. See

http://www.winsupersite.com/blog/sup ersite-blog-39/windows8/windows-8-pro-pc-upgrade-cost-15-143077

(50)

50

• See

http://webhostinggeeks.com/blog/the-future-of-vmware-questioned/ for

more discussion on how the almost-free pricing of "Hyper-V" makes it a viable product.

(51)

51

PROJECT 1 DETAILS

• "Project 1" for private, in-home use: In order to select the "virtual machine

program" that is best for private, in-home use, you should compare the capabilities of the Windows 8 Pro's bundled "Hyper-V"

program to it's free alternatives which are o "VMware Player”

o "Oracle VM VirtualBox” o "Windows Virtual PC"

(52)

52

PROJECT 1 DETAILS

o "Hyper-V" can be activated at no charge in "Windows 8 Release Preview" (and

"Hyper-V" will be available in the future "Windows 8 Pro 64-bit" and "Windows 8 Enterprise 64-bit”)

o "VMware Player” is free for private use in "Windows XP" and higher, including

"Windows 8". However, it cannot be

legally used by a business or any other organization.

(53)

53

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS)

o

"Oracle VM VirtualBox” is free

for private use in "Windows XP"

and higher including "Windows

8.."

o "Windows Virtual PC" is free with

"Windows 7 Home Premium" and

higher. "Windows Virtual PC"

will not install into a "Windows

8.." computer.

(54)

54

PROJECT 1 DETAILS

o "Microsoft Virtual PC 2007" is free for

Windows Vista Business, Windows Vista Business 64-bit edition, Windows Vista Enterprise, Windows Vista Enterprise 64-bit edition, Windows Vista Ultimate,

Windows Vista Ultimate 64-bit edition, Windows XP Professional Edition,

Windows XP Professional x64 Edition ,

Windows XP Tablet PC Edition "Microsoft Virtual PC 2007" will not install into a "Windows 7" or "Windows 8.."

(55)

55

PROJECT 1 DETAILS

• "Hyper-V" is available for free inside the 64-bit version of "Windows 8

Release Preview" (May 31, 2012). • "Hyper-V" is also available for free

inside the 64-bit versions of "Windows 8 Developer Preview" (Sept. 13,

2011) and "Windows 8 Consumer Preview" (Feb. 29, 2012).

(56)

56

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS..)

• In the near future, "Hyper-V"

will be bundled into the

production 64-bit edition of

the "Windows 8 Pro" and the

production 64-bit edition of

"Windows 8 Enterprise"

(57)

57

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS..)

• In the near future, "Client

Hyper-V" will NOT be

available inside the regular

"Windows 8" version of

(58)

58

PROJECT 1 DETAILS

• Microsoft's preliminary documentation

on "Client Hyper-V" is located at

http://technet.microsoft.com/en-us/library/hh857623.aspx and http://social.technet.microsoft.com/wik i/contents/articles/7704.client-hyper-v-survival-guide.aspx

(59)

59

PROJECT 1 DETAILS

• Inside "Windows 8..", "Client Hyper-V" is called "Hyper-V".

• However, in Microsoft's Web sites and blogs, "Hyper-V" is called "Client

Hyper-V" and it is occasionally called

"Hyper-V version 3".

• The "V" stands for "Varidian" which is a shade of blue-green.

(60)

60

PROJECT 1 DETAILS

Hardware requirements for "Hyper-V" • 4GB RAM is required (in the host

computer)

• Hyper-V requires a 64-bit processor that has Second Level Address Translation (SLAT). For information on checking and changing the virtualization support

settings in your system's BIOS, consult your system manufacturer. See also:

http://social.technet.microsoft.com/wiki/c ontents/articles/3190.aspx

4GB RAM is required. The RAM on your

Client Hyper-V machine is allocated and de-allocated dynamically as required by the

VMs. You can run several VMs on a Client Hyper-V machine (also called a “host”) that has the minimum 4GB of RAM, but you will need additional RAM for 5 or more VMs,

depending on the RAM requirements for each VM.

(61)

61

PROJECT 1 DETAILS

Hardware requirements for "Hyper-V" • To determine if your 64-but CPU

supports SLAT, see

http://www.edtittel.com/win7view/be-

(62)

62

PROJECT 1 DETAILS

Hardware requirements for "Hyper-V"

• A comprehensive list of the features of "Hyper-V" can be found at

(63)

63

PROJECT 1 DETAILS

Hardware requirements for "Hyper-V" (continued)

• "Hyper-V" is not available in the 32-bit version of "Windows 8..". In other words, "Hyper-V" requires a 64-bit

version of "Windows 8.." which requires a 64-bit processor.

(64)

64

PROJECT 1 DETAILS

Hardware requirements for "Hyper-V" (continued)

• Apparently, "Hyper-V" requires 4 Gigabytes of RAM while "VMware

Player 4" and "Oracle VM VirtualBox 4" only require 2 Gigabytes of RAM.

(65)

65

PROJECT 1 DETAILS

• “Hyper-V” has limited USB support

by means of "USB passthrough" from a "RDP" remote connection.

• “RDP” stands for “Remote Desktop Protocol” which is Microsoft’s

scheme for letting one Windows computer access the Desktop of another.

(66)

66

PROJECT 1 DETAILS

• "VMware Player 4" has excellent USB 2 support: You can connect USB devices such as flash drives and USB wireless adapters "on the

(67)

67

PROJECT 1 DETAILS

• "Oracle VM VirtualBox" has

problematic USB 2 support (but no USB 3 support"). It sort of works if you fight with it!

(68)

68

PROJECT 1 DETAILS

• "USB passthrough" from a "RDP" remote connection:

• You cannot connect a USB device

directly to a Hyper-V virtual machine. • You can pass through USB external

hard drives, USB flash drives, and any USB/IDE/SCSI/NAS/SATA/eSATA-

connected device that acts like a hard drive in "Windows Explorer" by means of a RDP connection.

(69)

69

PROJECT 1 DETAILS

(COMPARE "HYPER-V" TO OTHERS..) • “Hyper-V” does not allow USB, PCI, or PCIe

wireless network adapters to be connected to virtual machines

• "VMware Player 4" has excellent support for USB 2 wireless network adapters but no

support for PCI or PCIe wireless network adapters

• "Oracle VM VirtualBox" has problematic

support for USB 2 wireless network adapters but no support for PCI or PCIe wireless

(70)

70

PROJECT 1 DETAILS

• “Hyper-V” virtual machines cannot be installed in a computer that has a 32-bit processor (Your computer must have a 64-bit processor.)

• "VMware Player 4" virtual machines can reside in a computer that has a 32-bit

processor

• "Oracle VM VirtualBox" virtual machines can reside in a computer that has a 32-bit processor

(71)

71

(COMPARE "HYPER-V” TO OTHERS..)

• "Hyper-V" cannot be installed

into any "Windows 8.."

computer where either

"VMware Player" or "VMware

Workstation" is already

(72)

(73)

73

• To install both "Hyper-V" and "VMware

Workstation" OR "VMware Player" into the same computer, you have to play tricks

with the "Windows Boot Manager" as shown in http://blogs.msdn.com/b/virtual_pc_guy/ar chive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx and http://graegert.com/general/hyper-v-vmware-only-one-at-a-time

(74)

74

and

http://terrytlslau.tls1.cc/2011/03/using-bcdedit-set-up-boot-menu-for.html

(75)

75

• You can install and run "Hyper-V" and "Oracle VM VirtualBox" into the same "Windows 8.." computer.

• However, if you have both "Hyper-V" and "Oracle VM VirtualBox" installed, virtual machines that are running in

"Oracle VM VirtualBox" will run extremely slowly.

(76)

76

•

When both "Hyper-V" and "Oracle VM VirtualBox" are installed into the same computer: virtual machines running in

"Oracle.." will get an incorrectly emulated virtual processor which is a lot less

capable than the actual processor in the real host computer. For example, a 64-bit Intel processor will often be emulated as a 32-bit one. You can take advantage of

this to slow down old DOS and Windows 3.1 games.

(77)

77

• When both "Hyper-V" and

"Oracle VM VirtualBox" are

installed into the same computer:

You will be unable to run

"Windows 8" or "GNU/Linux"

guest operating systems inside

virtual machines inside "Oracle

VM VirtualBox" running in a

(78)

(79)

(80)

(81)

81

PROJECT 1 DETAILS (continued) (COMPARE "HYPER-V” TO OTHERS)

• When "Windows 7 Enterprise Trial 32-bit" was installed into a virtual machine

running in "Oracle VM VirtualBox" in a "Windows 8.." host, we were unable to increase the swap file to greater than 4095 Megabytes until we forced on

"Physical Address Extension" ("PAE"). The procedure for doing this is located in

Pages 114 through 150 of "Speeding Up Windows 7" which is located at

http://aztcs.org/meeting_notes/winhardsig /speedupWindows/win7speedup.pdf

(82)

82

• Because Hyper-V is part of the

“Windows 8..” operating system, it has speed advantages over its

competition: virtual machines in “Hyper-V” will

start up faster and run faster

compared to virtual machines in “VMware Player” (free), "VMware Workstation", and “Oracle VM

(83)

83

(COMPARE "HYPER-V” TO OTHERS”)

• SiSoftware Sandra 2012 Lite (version 2012-05-18.40) benchmarks for

virtual machines running "Windows 7 Enterprise Trial 64-bit" with "Service Pack 1", 5.5 Gigabytes of assigned RAM, 4 (out of 8) virtual cores of a virtual i7-920 Intel processor, a 750 Gigabyte virtual IDE hard drive,

Microsoft Security Essentials, and Adobe Acrobat Reader 10, :

(84)

84

(COMPARE "HYPER-V” TO OTHERS”)

o 4.76 kPT--Hyper-V virtual machine (in a Windows 8 RC 64-bit host)

o 4.28 kPT--Oracle VM Virtualbox 4.1

virtual machine (in a Windows 7 64-bit host)

o 4.11 kPT--VMware Workstation 8 virtual machine (in a Windows 7 64-bit host)

o 3.76 kPT--VMware Player 4.0 virtual machine (in a Windows 7 64-bit host)

(85)

(86)

(87)

(88)

(89)

(90)

(91)

(92)

(93)

93

• See

http://soerennielsen.wordpress.com/ 2011/07/07/vmware-or-hyper-v-for-virtualization/

(94)

94

• Due to the overhead of virtualizing hardware, virtual machines always run slower than the real host

(95)

95

o 4.76 kPT-- Hyper-V vm

o 4.28 kPT-- Win 7 VM Virtualbox 4.1 vm o 4.11 kPT--VMware Workstation 8 vm

o 3.76 kPT--VMware Player 4.0 vm

o 6.45 kPT--Windows 7 Real Physical (Host) Computer

o 6.48 kPT--Windows 8 Real Physical (Host) Computer

(96)

(97)

(98)

(99)

(100)

100

• You can compensate for some

of the slowdowns that are

inherent in virtual machines by

performing various speedup

tweaks on both your host

computer and the virtual

machines that reside in it.

See:

(101)

101

• "Speeding Up Windows Vista":

PowerPoint .PPT format Adobe .PDF format --- • "Speeding Up Windows 7": PowerPoint .PPT format Adobe .PDF format --- • "Speeding Up Windows XP": PowerPoint .PPT format Adobe .PDF format

(102)

102

• Many "Windows.." and "GNU/Linux" distros running in Hyper-V virtual

machines can gain extra speed by using Microsoft's "Enlightened I/O"

through the virtual "VMBus". See

http://en.wikipedia.org/wiki/Hyper-V • Use the "Network Adapter" test to

(103)

103

• See http://en.wikipedia.org/wiki/Hyper-V and http://www.virtuatopia.com/index.php /An_Overview_of_the_Hyper-V_Architecture and http://msdn.microsoft.com/en-us/library/cc768520(v=bts.10).aspx

(104)

(105)

105

• For "Windows.." virtual machines, the ability to communicate with the VMBus has to be built into the kernel of

"Windows.." (which is true for "Windows XP", "Windows Vista", "Windows 7", and "Windows 8")

• For distros of the "GNU/Linux" operating system, the ability to communicate with VMBus is either built in by the developer or you can add it in yourself.

(106)

106

(107)

References: http://blogs.technet.com/b/iftekhar/archive /2009/04/15/virtualizing-linux-on-microsoft-hyper-v.aspx and http://rmicteched.files.wordpress.com/200 8/06/hyper-v.ppt and

(108)

(109)

109

• Some comparisons between "Hyper-V" and other virtual machine

programs can be found at

http://social.technet.microsoft.com/F

orums/en- US/w8itprovirt/thread/9e297615-19e1-4134-8450-c0bdf5adddc7

(110)

110

• A very extensive comparison

between "Hyper-V" and "VMware.." can be found at

http://www.zdnet.com/debate/hyper-v-or-vmware/6348000

(111)

111

• Some special considerations for

“Windows Virtual PC” and “Microsoft Virtual PC 2007” (continued):

‾ “Windows Virtual PC” and

“Microsoft Virtual PC 2007" will not allow "Windows 8 Release

Preview" to be installed inside a virtual machine.

(112)

112

“Windows Virtual PC” and “Microsoft Virtual PC 2007” (continued):

‾ “Windows Virtual PC” and

“Microsoft Virtual PC 2007" will not install into a host computer that is running "Windows 8 Release

(113)

113

• Some special considerations for “VMware Player”:

‾ It is much easier and faster to clone a virtual machine in “VMware

Player”, compared to "Hyper-V" and “Oracle VM VirtualBox”.

(114)

114

• Some special considerations for “VMware Player” (continued):

-To clone a virtual machine in

“VMware Player”, you just use a file manager such as “Windows

Explorer” to copy the entire virtual machine folder.

(115)

115

• Some special considerations for “VMware Player” (continued):

-To clone a virtual machine in other virtual machine programs, you have to follow a longer and more involved procedure.

(116)

116

• Some special considerations for “Oracle VM VirtualBox”

-In addition to its own .VDI virtual hard drive format, “Oracle VM

VirtualBox” can use .VMDK virtual hard drives that were created by “VMware Player” and .VHD virtual hard drives that were created by “Windows Virtual PC” and "Hyper-V".

(117)

117

• Some special considerations for “Oracle VM VirtualBox” (continued)

-The degree to which an “Oracle VM VirtualBox” virtual machine can use a .VMDK or a .VHD file depends on the specific operating system that is being installed into the virtual machine. Sometimes you can boot up from the .VMDK or .VHD file and sometimes you can only use the .VMDK or .VHD file as a data drive.

(118)

118

• Some special considerations for “Oracle VM VirtualBox” (continued)

‾ A .VHDX virtual hard disk file (that was

created by "Hyper-V" in "Windows 8.." cannot be opened or attached to an “Oracle VM

(119)

119

• "Hyper-V" has virtual IDE and

SCSI hard drive adapters--no

virtual SATA network adapters

are available. In a "Hyper-V"

virtual machine, the bootable

"virtual hard drive" of a virtual

machine has to be attached to a

virtual IDE adapter.

(120)

120

• "Hyper-V" lets you make virtual hard drives that are up to 60 Terabytes in

size. Other "virtual machine programs" only let you make much smaller virtual hard drives: For example "VMWare

Player 4" and "Oracle VM VirtualBox 4" allow you to create virtual hard drives that are 2 Gigabytes (2040.0

Megabytes) in size.

(121)

121

“Oracle VM VirtualBox”(continued) ‾ “Oracle VM VirtualBox” provides

you with more options for the type of virtual hard drive

controller (that is used to connect to the virtual hard drive of a

(122)

122

“Oracle VM VirtualBox”(continued)

‾ “Oracle VM VirtualBox” provides you with virtual IDE, SCSI, SATA and

SAS hard drive controllers.

‾ “VMware Player” only provides

virtual machines with IDE and SATA virtual hard drive controllers.

(123)

123

• Some special considerations for

“Oracle VM VirtualBox”(continued)

‾ “Windows Virtual PC” and “Microsoft

Virtual PC 2007” do not give you any virtual hard drive controller

options when you are setting up a virtual machine: You get a virtual “Intel” “IDE Controller”.

(124)

124

“Oracle VM VirtualBox” (continued) ‾ In “..VirtualBox”, if your host

computer has a 64-bit CPU chip with Intel VT-# support or AMD-V support, even if you are running a 32-bit host operating system, you can create (slow) virtual machines with 64-bit operating systems.

(125)

125

• "Hyper-V" in "Windows 8" has less reliable Linux support for running

Linux in virtual machines relative to "VMware Player" and "Oracle VM VirtualBox".

(126)

126

PROJECT 2 DETAILS

(INSTALL "HYPER-V"..)

• For instructions on how to install

"Hyper-V" into a “Windows 8..” host computer, see

http://www.howtogeek.com/76532/ho

(127)

127

PROJECT 2 DETAILS

• "Hyper-V" is a legacy Desktop

applet that is part of "Windows 8 Pro" and "Windows 8 Enterprise"

that runs as a "snap-in" in "Microsoft Management Console" ("MMC").

(128)

128

• "Hyper-V" is a legacy Desktop

(129)

129

(INSTALL "HYPER -V"..)

• Microsoft's official documentation for "Hyper-V" is located at http://technet.microsoft.com/en-us/library/hh857623.aspx and http://social.technet.microsoft.com/wiki/co ntents/articles/7704.client-hyper-v-survival-guide.aspx

(130)

130

PROJECT 2A DETAILS

(CREATE A VIRTUAL "EXTERNAL NETWORK SWITCH" USING THE HYPER-V PROGRAM)

• Unlike other virtual machine

programs, "Hyper-V" does not provide you with a virtual network for the

virtual machines that you create, so you have to create one prior to

(131)

131

PROJECT 2A DETAILS

(CREATE .. "EXTERNAL NETWORK SWITCH"..)

• Step 1: Start the Hyper-V program:

Double-click on virtmgmt.msc from

inside C:\Windows\System32\ or run

virtmgmt.msc from any command prompt window or

(132)

(133)

133

PROJECT 2A DETAILS

(CREATE .."EXTERNAL NETWORK SWITCH"..)

• Step 2: Click on "Virtual Switch Manager"

(134)

(135)

135

PROJECT 2A DETAILS

• Step 3: Make sure that "External" is

(136)

(137)

137

PROJECT 2A DETAILS

• Step 4: Make sure that "New Virtual Network

(138)

(139)

139

PROJECT 2A DETAILS

• Step 5: Click on the "Create Virtual Switch"

(140)

(141)

141

PROJECT 2A DETAILS

• Step 6: Change the "Name" from "New Virtual

Switch" to an appropriate name. We recommend "External Virtual Switch 01".

(142)

(143)

143

PROJECT 2A DETAILS

• Step 7: Click on the "Apply" button.

(144)

(145)

(146)

(147)

147

PROJECT 3 DETAILS

(CREATE VIRTUAL MACHINES) • Project 3 Method 1:

Use the installation media provided by the maker of the operating system.

• Project 3 Method 2:

Clone an existing virtual machine so that it runs in the same “virtual machine program”.

• Project 3 Method 3:

Clone an existing virtual machine so that it runs in a different “virtual machine program” (=

(148)

148

PROJECT 3 (CREATE VIRTUAL MACHINES) Method 1: Use Installation Media (or an .ISO file)

(149)

149 149

PROJECT 3 (CREATE VIRTUAL MACHINES)

Method 2: Clone an Existing Virtual Machine So That it Runs in the Same “Virtual Machine Program”

(150)

150 150

PROJECT 3 (CREATE VIRTUAL MACHINES)

Method 3: Clone a Virtual Machine So That It Runs in a Different “Virtual Machine Program” (V2V)

VMware Player

Oracle VM

(151)

151

PROJECT 3 DETAILS

(CREATE VIRTUAL MACHINES)

• Method 1 Details:

Use the installation media

(floppy disks, CDs, DVDs,

or .ISO files) provided by

the maker of the operating

system.

(152)

152

PROJECT 3 DETAILS

• Method 1 Details: If you are creating a virtual machine which will

run "Windows XP", "Windows 7", or "Windows 8" as a guest OS, create a "Legacy Network

Adapter" for the virtual machine prior to starting

the virtual machine to install the guest OS. Then add a regular VMBus-based "Network

Adapter" after the operating system is installed. Then remove the "Legacy Network Adapter".

Then reboot the virtual machine to force a "plug and play" synch up with the VMBus-based

(153)

153

PROJECT 3 DETAILS

• Method 1 Details: If you are creating a virtual machine which will

run "Windows Vista" as a guest OS, create a "Legacy Network Adapter" for the virtual

machine prior to starting the virtual machine to

install the guest OS. Then add a regular VMBus-based "Network

Adapter" after the operating system is installed. Then perform the workaround described at

(154)

154

PROJECT 3 DETAILS

• Method 1 Details: (If you are creating a virtual machine which will

run "Windows Vista"..(continued)) Then remove the "Legacy Network Adapter".

Then reboot the virtual machine to force a "plug and play" sync up with the VMBus-based

(155)

155

PROJECT 3 DETAILS

• Method 1 Details:

If you are creating a virtual machine which will run "Ubuntu" or a "Ubuntu" derivative, create a (regular)

"Network Adapter" for the virtual

machine prior to starting the virtual machine. (This is because "Ubuntu" has VMBus drivers for the "Network Adapter" already in it.)

(156)

156

PROJECT 3 DETAILS

If you are creating a virtual machine which will run "Ubuntu" or

non-"Ubuntu" derivative distros of GNU/Linux, create a legacy "Network Adapter" for the virtual machine prior to starting the virtual machine. After the operating system is

installed, you can attempt to download

and install drivers for a (regular) "Network Adapter".

(157)

157

PROJECT 3 DETAILS

For advice on installing "Ubuntu 11.10" into a virtual machine in

"Hyper-V" in "Windows 8..", see http://www.eightforums.com/tutorials

(158)

158

PROJECT 3 DETAILS

Clone an existing Hyper-V virtual machine (so that the cloned virtual machine also runs inside the Hyper-V “virtual machine program”).

(159)

159

PROJECT 3 DETAILS

Method 2: Clone Virtual Machines (continued)

–Two alternative procedures for cloning a

virtual machine in “Hyper-V": Cloning Procedure 1: Use the "Export"

and "Import" functions of "Hyper-V" Cloning Procedure 2: Copy the .VHDX or

.VHD virtual hard drive and then run the "New" "Virtual Machine" function of

(160)

160 PROJECT 3 DETAILS

–"Cloning Procedure 1"--To clone a virtual machine by using the "Export" and

"Import" features of "Hyper-V": Step 1: Use the "Export" feature of

Hyper-V to create a backup "image" of a virtual

machine Step 2: Use the "Import" feature of Hyper-V to create a new virtual machine from the backup image that was created in "Step

(161)

–"Cloning Procedure 2"--To clone a virtual machine by copying the .VHDX or .VHD

virtual hard disk file: Use "Windows Explorer" to make a copy of

the .vhd or .vhdx virtual hard drive file. From the Menu bar of "Hyper-V", click on

"Action", "New", and "Virtual Machine". Specify the copy of the virtual hard drive

file when you arrive at the "Connect Virtual Hard Disk" dialog box.

(162)

162

PROJECT 3 DETAILS

"Method 3" consists of using an

existing virtual machine to create a new virtual machine that runs on a different “virtual machine program”

(= “V2V” which” stands for “Virtual to Virtual”)

(163)

163

PROJECT 3 DETAILS

• Method 3 Details (continued):

You can use Microsoft's free “Disk2VHD” program to use a “Oracle VM VirtualBox” virtual machine to create a new virtual

machine for "Hyper-V". See

http://www.aztcs.org/meeting_notes/winha rdsig/virtualmachines/v2v/Disk2VHD-v2v-VBoxtoVHD.pdf

(164)

164

PROJECT 3 DETAILS

• Method 3 Details (continued): You can use the free

"VMDK(VMWare) to VHD Converter" to convert a VMware virtual machine to a new virtual machine for Hyper-V. See

http://community.spiceworks.com/ho w_to/show/635

(165)

165

PROJECT 3 DETAILS

• “ADD-ON” SOFTWARE TO INSTALL INTO EACH VIRTUAL MACHINE:

After you create a virtual machine using any of the three methods, you should

start the virtual machine and install “add-on” software that is provided by the maker of the virtual machine program.

(166)

166

PROJECT 3 DETAILS

• For "Windows.." virtual machines running in "Hyper-V", you can install the "Integration

Services" Add-on to enable enhanced functions such as better mouse control, a driver for the

non-legacy network adapter, AND faster

communications between the virtual machine

and the host operating system: Start up the guest operating system of the

virtual machine Click on "Action"; then click on "Insert

(167)

167

PROJECT 3 DETAILS

(CREATE VIRTUAL MACHINES) • When you install Hyper-V's "Integration

Services" as a software program into a guest operating system, you are adding a "VMBus" module into the virtual machine.

• See

http://www.virtuatopia.com/index.php/Understan

(168)

168

PROJECT 3 DETAILS

• For "GNU/Linux.." virtual machines running in "Hyper-V", you can install

"Integration Services" to make VMBus-based virtual "Network Adapters" work after you download it from

http://www.microsoft.com/en-us/download/details.aspx?id=28188 or

(169)

169

PROJECT 3 DETAILS

• For an example of how to install "Integration Services" into a Linux distro, see

http://jaredheinrichs.com/how-to-

(170)

170

PROJECT 3 DETAILS

• Some distros of Linux already have Microsoft's "Integration Services"

incorporated by their developers so

you do not need to install "Integration Services" after installing them into a virtual machine: Ubuntu 12.04, Linux Mint 13

(171)

171 171

OPTIONAL PROJECT 4

(P2V=“PHYSICAL TO VIRTUAL”)

Use a Real Computer to Make a Virtual Machine

(172)

172

OPTIONAL PROJECT 4 DETAILS (continued) (DO "PHYSICAL TO VIRTUAL”)

• To use a real, physical computer to create a "virtual machine" (P2V) that can be "played" in any "Windows 8.." computer that has "Hyper-V" activated in it, you can use Microsoft’s

(173)

173

• “Physical to Virtual” (P2V) By

Microsoft’s Free “Disk2VHD” Program –The “Disk2VHD” program can be

downloaded from

http://technet.microsoft.com/en-us/sysinternals/ee656415

(174)

174

• “Physical to Virtual” (P2V) By the Microsoft’s Free “Disk2VHD” Program

–You can install it into any physical

computer that has Windows XP Service Pack 2 and higher, Windows Vista, or

Windows 7 and use it to create a .VHD virtual hard drive file that can be used to create a virtual machine in “Windows

Virtual PC”, “Microsoft Virtual PC 2007”, or “Oracle VM VirtualBox”.

(175)

175

• “Physical to Virtual” (P2V) By Microsoft’s Free “Disk2VHD” Program (continued)

–For detailed instructions for using

“Disk2VHD” to use a “Windows XP” computer to create a virtual machine that runs in "Hyper-V", see

http://www.techrepublic.com/photos/con

(176)

176

• “Physical to Virtual” (P2V) By Microsoft’s Free “Disk2VHD” Program (continued)

–The steps for using “Disk2VHD” to create a virtual machine from a real

computer are almost exactly the same as the (V2V) steps for using an “Oracle VM VirtualBox” virtual machine to create a “Windows Virtual PC” or “Microsoft

(177)

177

PROJECT 5 DETAILS: USE VIRTUAL MACHINES

• Virtual Hardware

• Full virtualization means that all major hardware components are virtualized in software by the "virtual machine

(178)

USE VIRTUAL MACHINES

• Virtual Hardware (continued)

–A view of itself from inside a

“Windows 7” virtual machine

inside “Hyper-V”:

(179)

179

PROJECT 5 DETAILS: USE VIRTUAL MACHINES

• Virtual Hardware (continued):

The manufacturer of this virtual machine computer is shown to be “Microsoft Corporation”.

(180)

180

• Virtual Hardware (continued)

–The "virtual hardware" in a virtual machine contains a set of

standardized hardware that the

"virtual machine program" creates for each virtual machine: BIOS,

motherboard, drive controllers, network adapter(s), monitor,

(181)

181

• Virtual Hardware (continued)

•This makes virtual machines

easy to transfer from one

computer to another as long

as we run them in the same

“virtual machine program”.

(182)

182

PROJECT 5 DETAILS (continued) USE VIRTUAL MACHINES

• Virtual CPUs (continued)

–"Hyper-V" provides each virtual

machine with a virtual processor that is the same as the actual processor of

(183)

183

• Virtual motherboards

• “Hyper-V” provides each virtual machine with a virtual

(184)

(185)

(186)

(187)

(188)

(189)

(190)

190

• Virtual motherboards

• All virtual machines get a "Virtual Machine 7.0” motherboard that

shows "Microsoft Corporation" as the manufacturer.

(191)

(192)

192

• Virtual BIOS

For a "Hyper-V" virtual machine, the only BIOS settings that you can adjust are Num Lock On/Off and Boot Device Order.

(193)

(194)

(195)

195

• Virtual BIOS

For “Hyper-V” virtual machines, you can only configure the virtual BIOS settings from the "Settings" box:

(196)

(197)

197

• Allocated RAM

For a Hyper-V virtual machine, you can assign RAM up to the total amount of free RAM in the host computer.

(198)

(199)

(200)

200

• An extensive comparison between various “virtual machine programs” can be found at

http://en.wikipedia.org/wiki/Compari son_of_platform_virtual_machines