win8 hyper v

1

USING "HYPER-V"

IN "WINDOWS 8.." TO RUN

"VIRTUAL MACHINES"

http://aztcs.org/

2

Web location for this

presentation:

http://aztcs.org

Click on “Meeting Notes”

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

time.

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

3 Virtual Machines

Running in "Hyper-V"

running in my real

"Windows 8 Release

Preview" computer!

7

EXPLANATION

OF THE LIVE DEMO

8

Upstream to the real Internet

Real Physical

Computer running

"Windows 8

Release Preview

64-bit"

Start with your real

physical computer

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


Upstream to the real Internet Upstream to the real Internet

Virtual External Network Switch


Create a virtual "External Network

Switch" using the "Hyper-V"

program

11


Blank Virtual Machine

with no Operating System




Use the "Hyper-V" program

to make an empty virtual

machine

12


"Windows 7.."

Virtual Machine




Get into the empty virtual

machine program and install

"Windows 7 Enterprise Trial

64-bit" into it.

13


"Windows 7.."

Virtual Machine


with No Operating System





to make a second empty

virtual machine.

14


"Windows 8"

Virtual Machine

"Windows XP"

Virtual Machine

Hyper-V's External Virtual Network Switch




machine and install

"Windows XP" into it.

15


"Windows 8"

Virtual Machine

"Windows XP"

Virtual Machine





to make a third empty

virtual machine


with No Operating System

16


"Windows 8"

Virtual Machine

"Windows XP"

Virtual Machine





machine and install

"Ubuntu 12.04" into it

"Ubuntu 12.04"

Virtual Machine

17


"Windows 8"

Virtual Machine

"Windows XP"

Virtual Machine




The end result is three virtual

machines and a virtual network switch

inside a real "Windows 8.." computer

"Ubuntu 12.04"

Virtual Machine

18

View of the three virtual machines from "Windows

Explorer" in the real, "Windows 8" host computer:

19


Explorer" in the "Windows XP" virtual machine:

20


Explorer" in the "Windows 7" virtual machine:

21

View of the three virtual machines from the "Nautilus" file

manager applet in the "Ubuntu 12.04" virtual machine:

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

computer.

23

More Explanation of the Demo

• A third virtual machine running

"Ubuntu 12.04" is also running

inside my real computer.

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

OBJECTIVES FOR USING

VIRTUAL MACHINES

1. Save real money

2. Save real space

3. Save real time

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


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

physically available:

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



–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



–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

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





http://aztcs.org/meeting_notes/winhardsig/harddrives/repairing/hard_drive_soft_repairs.htm

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



–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


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”.

http://quickbooks.intuit.com/product/accounting-software/small-business-financial-software.jsp

http://turbotax.intuit.com/

34


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


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

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

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: Create Virtual Machines inside "Hyper-V".

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: (Learn to) Use Virtual Machines

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 software for private, in-home use.

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

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


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


o See http://en.wikipedia.org/wiki/Windows_Virtual_PC

http://en.wikipedia.org/wiki/Windows_Virtual_PC

http://en.wikipedia.org/wiki/Windows_Virtual_PC

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


• 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/supersite-blog-39/windows8/windows-8-pro-pc-upgrade-cost-15-143077

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




















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.

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









51


• "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"

o "Microsoft Virtual PC 2007"

52


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

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


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.." computer.

55


• "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


• 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"

versions of "Windows 8".

57


• In the near future, "Client

Hyper-V" will NOT be

available inside the regular

"Windows 8" version of

"Windows 8".

58


• 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/wiki/contents/articles/7704.client-hyper-v-survival-guide.aspx

http://technet.microsoft.com/en-us/library/hh857623.aspx



http://social.technet.microsoft.com/wiki/contents/articles/7704.client-hyper-v-survival-guide.aspx










59


• 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.

• We do not care what they call it!

60


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/contents/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.

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

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

61



• To determine if your 64-but CPU supports SLAT, see http://www.edtittel.com/win7view/be-prepared-for-windows-8-hyper-v-gotcha.html

http://www.edtittel.com/win7view/be-prepared-for-windows-8-hyper-v-gotcha.html















62



• A comprehensive list of the features of "Hyper-V" can be found at http://www.aidanfinn.com/?p=11979

http://www.aidanfinn.com/?p=11979

63


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


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


• “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


• "VMware Player 4" has excellent

USB 2 support: You can connect

USB devices such as flash drives

and USB wireless adapters "on the

fly" while a virtual machine is running.

67


• "Oracle VM VirtualBox" has

problematic USB 2 support (but no

USB 3 support"). It sort of works if

you fight with it!

68


• "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


• “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

network adapters

70


• “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

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

• "Hyper-V" cannot be installed into any "Windows 8.." computer where either "VMware Player" or "VMware Workstation" is already installed.

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/archive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx and http://graegert.com/general/hyper-v-vmware-only-one-at-a-time

http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx












http://graegert.com/general/hyper-v-vmware-only-one-at-a-time















74


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

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













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


• 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


• 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 "Windows 8.." host.

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

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


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 VirtualBox” (free).

83

PROJECT 1 DETAILS (continued) (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, :

http://www.soft82.com/version/download/windows/sisoftware-sandra-lite-2012-sp3-18-40/






84

PROJECT 1 DETAILS (continued) (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)

93


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

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












94


• Due to the overhead of virtualizing hardware, virtual machines always run slower than the real host computer that they reside on.

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

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


• "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

http://aztcs.org/meeting_notes/winhardsig/speedupWindows/vistaspeedup.ppt

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

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


http://aztcs.org/meeting_notes/winhardsig/speedupWindows/xp_speedup.ppt

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

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 determine if the "VMBus" is in use.

http://en.wikipedia.org/wiki/Hyper-V



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




http://msdn.microsoft.com/en-us/library/cc768520(v=bts.10).aspx







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

Reference: http://en.wikipedia.org/wiki/Hyper-V




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

http://blogs.technet.com/b/iftekhar/archive/2009/04/15/virtualizing-linux-on-microsoft-hyper-v.aspx













http://rmicteched.files.wordpress.com/2008/06/hyper-v.ppt




109


• Some comparisons between "Hyper-V" and other virtual machine programs can be found at http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/9e297615-19e1-4134-8450-c0bdf5adddc7

http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/9e297615-19e1-4134-8450-c0bdf5adddc7












110


• A very extensive comparison between "Hyper-V" and "VMware.." can be found at http://www.zdnet.com/debate/hyper-v-or-vmware/6348000

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







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



“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

Preview"

113



“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



“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



“VMware Player” (continued):

-To clone a virtual machine in other

virtual machine programs, you have

to follow a longer and more involved

procedure.

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


• 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


• 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

VirtualBox” virtual machine

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


• "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



“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

virtual machine).

122




‾ “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.

http://en.wikipedia.org/wiki/Parallel_ATA

http://en.wikipedia.org/wiki/SCSI

http://en.wikipedia.org/wiki/Serial_ATA

http://en.wikipedia.org/wiki/Serial_attached_SCSI

http://en.wikipedia.org/wiki/Parallel_ATA

http://en.wikipedia.org/wiki/Serial_ATA

123




‾ “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



“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


• "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

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

w-to-install-or-enable-hyper-v-

virtualization-in-windows-8/

http://www.howtogeek.com/76532/how-to-install-or-enable-hyper-v-virtualization-in-windows-8/






















http://aztcs.org/meeting_notes/winhardsig/virtualmachines/vmware/VMwarePlayer.pdf

127

PROJECT 2 DETAILS (INSTALL "HYPER-V"..)

• "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

PROJECT 2 DETAILS (continued) (INSTALL "HYPER-V"..)

• "Hyper-V" is a legacy Desktop

application, not a Metro Style App!

http://aztcs.org/meeting_notes/winhardsig/virtualmachines/WindowsVirtualPC/WindowsVirtualPC.pdf

129

PROJECT 2 DETAILS (continued) (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














http://aztcs.org/meeting_notes/winhardsig/virtualmachines/WindowsVirtualPC/WindowsVirtualPC.pdf

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

creating any virtual machines.


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

"Run" box


133

PROJECT 2A DETAILS (CREATE .."EXTERNAL NETWORK SWITCH"..)

• Step 2:

Click on "Virtual Switch Manager"

inside the "Action" pane.


135


• Step 3:

Make sure that "External" is

highlighted.


137


• Step 4:

Make sure that "New Virtual Network

Switch" is highlighted.


139


• Step 5:

Click on the "Create Virtual Switch"

button.


141


• Step 6:

Change the "Name" from "New Virtual

Switch" to an appropriate name. We

recommend "External Virtual Switch

01".


143


• Step 7:

Click on the "Apply" button.


147

PROJECT 3 DETAILS (CREATE VIRTUAL MACHINES)

• Project 3 Method 1:

Use the installation media provided by the

maker of the operating system.


Clone an existing virtual machine so that it runs

in the same “virtual machine program”.


Clone an existing virtual machine so that it runs

in a different “virtual machine program” (=

“V2V” )

148

PROJECT 3 (CREATE VIRTUAL MACHINES)

Method 1: Use Installation Media (or an .ISO file)

"Hyper-V" Program

149 149

PROJECT 3 (CREATE VIRTUAL MACHINES) Method 2: Clone an Existing Virtual Machine So That it

Runs in the Same “Virtual Machine Program”

"Hyper-V" Program

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

VirtualBox "Hyper-V" Program

151


• Method 1 Details:

Use the installation media

(floppy disks, CDs, DVDs,

or .ISO files) provided by

the maker of the operating

system.

152

PROJECT 3 DETAILS

(CREATE VIRTUAL MACHINES) • 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

"Network Adapter.

153

PROJECT 3 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

http://support.microsoft.com/kb/954282

http://support.microsoft.com/kb/954282

154

PROJECT 3 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

"Network Adapter".

155



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



If you are creating a virtual machine

which will run non-"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



For advice on installing "Ubuntu

11.10" into a virtual machine in

"Hyper-V" in "Windows 8..", see

http://www.eightforums.com/tutorials

/5078-hyper-v-create-linux-virtual-

machine-windows-8-a.html

http://www.eightforums.com/tutorials/5078-hyper-v-create-linux-virtual-machine-windows-8-a.html




















158



Clone an existing Hyper-V virtual

machine (so that the cloned virtual

machine also runs inside the Hyper-

V “virtual machine program”).

159

PROJECT 3 DETAILS

(CREATE VIRTUAL MACHINES)

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

"Hyper-V".

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

1".

http://aztcs.org/meeting_notes/winhardsig/virtualmachines/virtualbox/Cloning_VM_in_VirtualBox.pdf

161

PROJECT 3 DETAILS



–"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.

http://aztcs.org/meeting_notes/winhardsig/virtualmachines/virtualbox/Cloning_VM_in_VirtualBox.pdf

162



"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


• 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

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






164


• 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

http://community.spiceworks.com/how_to/show/635

http://community.spiceworks.com/how_to/show/635

165


• “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


• 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

Integration Services Setup Disc".

167


• 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/Understanding_and_Installing_Hyper-V_Integration_Services





168


• 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



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






169


• For an example of how to install

"Integration Services" into a Linux

distro, see

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

install-centos-on-hyper-v-with-

networking.html

http://jaredheinrichs.com/how-to-install-centos-on-hyper-v-with-networking.html

















170


• 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

OPTIONAL PROJECT 4

(P2V=“PHYSICAL TO VIRTUAL”)

Use a Real Computer to Make a Virtual Machine

"Hyper-V" Program

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

“Disk2vhd”.

173



• “Physical to Virtual” (P2V) By

Microsoft’s Free “Disk2VHD” Program

–The “Disk2VHD” program can be

downloaded from


us/sysinternals/ee656415

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



http://www.informationweek.com/news/smb/hardware_software/showArticle.jhtml?articleID=226200112

174


(DO "PHYSICAL TO VIRTUAL”) • “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



• “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

vert-xp-into-a-windows-7-virtual-

machine-with-disk2vhd/466302

http://www.techrepublic.com/photos/convert-xp-into-a-windows-7-virtual-machine-with-disk2vhd/466302




















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

Virtual PC 2007” virtual machine.





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

program".

178

PROJECT 5 DETAILS USE VIRTUAL MACHINES

• Virtual Hardware (continued)

–A view of itself from inside a

“Windows 7” virtual machine

inside “Hyper-V”:

179

PROJECT 5 DETAILS: USE VIRTUAL MACHINES

• Virtual Hardware (continued):

The manufacturer

of this virtual

machine computer

is shown to be

“Microsoft

Corporation”.

180

PROJECT 5 DETAILS (continued) USE VIRTUAL MACHINES


–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,

keyboard, mouse, etc.

181



•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


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 the physical host computer.

183


USE VIRTUAL MACHINES

• Virtual motherboards

• “Hyper-V” provides each virtual

machine with a virtual

motherboard.

190



• Virtual motherboards

• All virtual machines get a "Virtual

Machine 7.0” motherboard that

shows "Microsoft Corporation" as

the manufacturer.

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.

195



• Virtual BIOS

For “Hyper-V” virtual machines,

you can only configure the virtual

BIOS settings from the "Settings"

box:

197


USE VIRTUAL MACHINES • Allocated RAM

For a Hyper-V virtual machine,

you can assign RAM up to the

total amount of free RAM in the

host computer.

200



• An extensive comparison between

various “virtual machine programs”

can be found at

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

son_of_platform_virtual_machines

http://en.wikipedia.org/wiki/Comparison_of_platform_virtual_machines

http://en.wikipedia.org/wiki/Comparison_of_platform_virtual_machines

201



• Virtual hard drives

–When you create a virtual

machine, you can also create a

"virtual hard drive" for it.

202



• Virtual hard drives (continued)

–A virtual hard drive file in “Hyper-V" in

"Windows 8” will have a file extension

of .VHDX or .VHD

203




–In a "Windows 8.." computer

the default location for virtual

hard drives is

C:\Users\Public\Documents\

Hyper-V\Virtual hard disks

204




–See

http://www.hyper-

v.nu/archives/hvredevoort/2012/01/win

dows-8-storage-and-hyper-v-part-2-

vhdx-and-powershell/

http://www.hyper-v.nu/archives/hvredevoort/2012/01/windows-8-storage-and-hyper-v-part-2-vhdx-and-powershell/
























205



• Virtual hard drive controllers

–The type of virtual hard drive

that a “guest operating system”

“sees” depends on which type

of virtual hard drive controller

you connect to the virtual hard

drive.

206


• Mouse cursor control rule #1:

When you first click inside a window

of a virtual machine, you might be

just activating the mouse for that

window. Then you usually have to

click again to make something

happen inside the virtual machine

window.

207



• Mouse cursor control rule #2:

For each virtual machine (window),

your mouse cursor will either be in

"integration mode" or in

"captured"/"in jail" mode.

208


Mouse cursor control rule #2

(continued):

To release the mouse cursor from a

virtual machine that is running in

"Hyper-V", press Ctrl + Alt + Left

arrow once.

209


• Keyboard control:

The keyboard of your computer will

only work inside a virtual machine’s

window if you have the mouse cursor

inside the virtual machine window

AND maybe if you have already

clicked at least once inside the virtual

machine window.

210


USE VIRTUAL MACHINES • Window ownership by which virtual

machine??

To determine if a Window belongs to

a specific virtual machine, move the

Window from side to side and watch

the borders of the window.

In “Windows 7” do not shake the Window

too fast, or all the other Windows might

minimize (“Aero Shake”).

211


• "Hyper-V" requires you to use its

"Virtual Switch Manager" to install

a virtual "network switch(s)" that

your real host computer and all of

your virtual machines have to use

for all network communications to

the real Internet and to the real

Local Area Network (LAN).

212


• When you use Hyper-V's "Virtual

Switch Manager" to install a virtual

"network switch", you can make

three kinds of "network switches":

o Virtual external switch

o Virtual internal switch

o Virtual private switch

216


• When you have Hyper-V running in your

Windows 8 computer and you switch from a

wired to a wireless network adapter, or vice

versa, your existing virtual "External network

switch(s)" will fail to switch over to the new,

real network adapter and all of your virtual

machines will be disconnected from your real

network until you manually connect the

"External network switch(s)" to the new

network adapter from inside the Hyper-V

management console.

217


• Virtual network that you

can create for a Hyper-V

virtual machine when a

real wired network

adapter is present in the

host computer:

218

Real Host Computer

Real Wired Network Adapter

219

Real Host Computer


220


• No direct access to the

virtual "MAC: A" that

connects the host

computer ("root partition")

to the virtual external

switch.

221


• Direct access to the

virtual "MAC: B" network

adapters from inside the

guest operating system of

each virtual machine.

222


• "Mac: A" virtual network

adapter for the host computer

(=root partition) only works

when the virtual network switch

is attached to a wired network

adapter that is connected to the

real LAN.

223


• However, when you disconnect the

real, wired network adapter from the

real network, "Mac: A" virtual network

adapter for the host computer (=root

partition) fails (and the host is no

longer connected to any real or virtual

networks) while the "Mac: B" network

adapters for the virtual machines

continue to work and the virtual

machines can "see" each other.

224

Real Host Computer


225


• Both "Mac: A" virtual network

adapter (for the host computer)

and all "Mac: B" virtual network

adapter(s) (for the virtual

machine) fail when the virtual

external network switch is

disconnected from a real WiFi

network.

226


• Virtual network that is

used by a Hyper-V virtual

machine when a real WiFi

network adapter is

present in the host

computer:

227

Real Host Computer

Real Wireless Network Adapter

228


Real Host Computer

229


• Both "Mac: A" virtual network

adapter (for the host computer)

and all "Mac: B" virtual network

adapter(s) (for the virtual

machine) fail when the virtual

external network switch is

disconnected from a real WiFi

network.

230


Real Host Computer

231



• Reference for previous two diagrams:

http://blogs.msdn.com/b/b8/archive/2011

/09/07/bringing-hyper-v-to-windows-

8.aspx

http://blogs.msdn.com/b/b8/archive/2011/09/07/bringing-hyper-v-to-windows-8.aspx












232


• When you create a virtual

machine, you can create a virtual

"Network Adapter"

or a

virtual "Legacy Network Adapter"

for the virtual machine:

233



• virtual "Network Adapter" in virtual machine

configuration screens

o It runs at 10 Gigabits per second

o It attaches to the virtual machine's virtual

VMBus

o = "synthetic network adapter" in Microsoft

tech literature

o = "Microsoft Hyper-V network adapter" from

viewpoint of guest OS

o It has no real analog in real physical devices

234



• virtual "Legacy Network Adapter" in

virtual machine configuration screens

o It runs at 100 Megabits per second

o It attaches to virtual machine's

emulated/virtual PCI bus

o = virtual "Intel 21140 PCI Fast Ethernet

adapter" which is a virtual analog of a

real wired network adapter that really

existed 10 years ago

242


• Virtual VMBus-based

"Network Adapter" as seen

from inside a "Windows 7.."

virtual machine:

243


• If you use your RIGHT

mouse button to click on

the "Network Adapter":

249


• Virtual "Legacy Network

Adapter" as seen from

inside a "Windows 7.."

virtual machine:

258


• Right-click on the "Network

Adapter":

265



• A "Network Adapter" connects to the

"VMBus" and it is described as having

"Enlightened IO".

• A "Legacy Network Adapter" connects to

the virtual machine by means of an

"Emulation Module" that is provided by

Hyper-V. The "Emulation Module" fools

the guest operating system into "seeing"

a real wired network adapter.

266



• When you give "Windows XP",

"Windows Vista", "Windows 7", and

"Windows 8" virtual machines a

"Network Adapter", you have to install

Hyper-V's "Integration Services" program

as an application program that runs

inside the "Windows.." virtual machine

guest.

267



• To install "Integration Services" into a

virtual machine (or to make sure that

"Integration Services is already installed

into a virtual machine), click on "Action"

on the top Menu Bar. Then click on

"Insert Integration Services Setup Disk"

on the pull-down menu:

268



• When "Windows XP.." runs in a Hyper-V

virtual machine and you install Hyper-V's

"Integration Services", it shows up in

"Add or Remove Programs" in the

"Control Panel":

270



• When "Windows Vista", "Windows 7", or

"Windows 8" runs in a Hyper-V virtual

machine and you install Hyper-V's

"Integration Services", it does not show

up in "Programs and Features" in the

"Control Panel":

274


USE VIRTUAL MACHINES • When a "distro" of GNU/Linux in a Hyper-V

virtual machine is capable of using a

"Network Adapter", it means that the

software developers of the "distro" have

included Microsoft's "Linux Integration

Components" source code in their

compilation of the Linux kernel, or as

drivers in the distro, or the end user of the

Linux computer has added the "Linux

Integration Components" manually as

drivers downloaded from Microsoft.com

275



See

http://blogs.technet.com/b/virtualization/ar

chive/2008/04/01/linux-integration-

components-for-hyper-v-rc-now-

available.aspx

and

http://blog.allanglesit.com/2009/05/hyper-

v-guests-linux-integration-components-

ubuntu-and-debian/

and

http://blogs.technet.com/b/virtualization/archive/2008/04/01/linux-integration-components-for-hyper-v-rc-now-available.aspx


















http://blog.allanglesit.com/2009/05/hyper-v-guests-linux-integration-components-ubuntu-and-debian/

















276



• and

http://blogs.technet.com/b/port25/archive

/2009/07/20/more-on-the-hyper-v-linux-

integration-components.aspx

and



and

http://blogs.technet.com/b/port25/archive/2009/07/20/more-on-the-hyper-v-linux-integration-components.aspx



















277



• and

http://blogs.technet.com/b/virtualization/a

rchive/2008/04/01/linux-integration-

components-for-hyper-v-rc-now-

available.aspx

and

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

ms/en/linuxintegrationservices/thread/c9

019f84-2375-4196-ac8d-4eb7da66d5ea




















http://social.technet.microsoft.com/Forums/en/linuxintegrationservices/thread/c9019f84-2375-4196-ac8d-4eb7da66d5ea











278



• "Hyper-V" has no direct USB support.

However there are two workarounds:

Workaround 1 = File Sharing

(conventional fire sharing, file sharing via

home group, or a network-to-USB

device)

and

Workaround 2 = USB Passthrough

(from a RDP connection from another

physical computer)

279


• USB Workaround 1 = File Sharing: Hyper-V does not provide a USB controller for its virtual machines. However, if you activate file sharing for any folder on an external USB hard drive or any folder on an USB flash drive, you can then access the shared folder from inside a virtual machine:

280



• Workaround 2 = File Sharing (continued):

o From the host computer, start "Windows Explorer",

o Right click on the folder that you wish to share,

o Click on "Properties" in the pop-up utility menu,

o Click on the "Sharing" tab,

o Click on "Advanced Sharing",

o Place a check mark in "Share this folder",

o Click on "Permissions",

o Checkmark "Full Control" for "Everyone",

o Click on the "OK" button.

281


• Workaround 2 = USB Passthrough: Hyper-V does not provide a USB controller for its virtual machines. However, if you activate "Remote Desktop Connection" in a virtual machine, you can use a "Remote Desktop Connection" to do a "USB Passthrough" to loan a USB connection or a USB-connected storage device (external hard drive, flash drive, camera chip, etc.) to a virtual machine that is running in "Hyper-V".

282


• Remote Desktop Workaround for Audio: Hyper-V does not provide a virtual sound controller for its virtual machines. However, if you activate "Remote Desktop Connection" in a virtual machine, you can use a "Remote Desktop Connection" to do a "Sound Passthrough" to loan a sound controller to a virtual machine that is running in "Hyper-V".

283


• Remote Desktop Workaround for Drives on the Host: If you activate "Remote Desktop Connection" in a virtual machine, you “loan” a real or virtual drive that is connected to the host computer to a virtual machine running in "Hyper-V". The real or virtual drive can be internal or external and the drive can be connected by means of IDE, SCSI, SAS, RAID, eSATA, or SATA. It can even be a drive that is mapped to a server location.

284


• When you "loan" a DVD/CD-R/RW drive to a virtual machine, you can access the contents of any DVDs and CDs but you will be unable to write or burn to the DVD or CD media. However, you will be unable to play music CDs and DVD videos that are attached to the host computer.

307


• When you use "Remote Desktop Protocol" to "loan" a sound controller, a drive, or a drive-like device to a virtual machine in Hyper-V, the "loaned" device shows up in the "Other" section of "Windows Explorer" inside the virtual machine. Your application programs will be unable to access the shared drives and drive-like devices directly so you will have to copy them to the virtual hard drive(s) of the virtual machine using "Windows Explorer" inside the virtual machine.

308


• You cannot make more than one "Remote Desktop Protocol" connection into a virtual machine at the same time.

• If you make a "Remote Desktop Protocol" connection to a virtual machine, the local user of the virtual machine will be automatically logged off.

• If you then log into the virtual machine locally, the "Remote Desktop Protocol" connect will be terminated.

309

"Hyper-V"

Virtual Machine Program

Remote Desktop Connection applet in

the host computer, or a workgroup

computer or a virtual machine

"Windows.." Virtual Machine

Hyper-V's

External Virtual

Network Switch

Upstream network switch/router

Real Physical Computer

running "Windows 8.."

Using a RDP remote

connection to "loan" a

USB connection, a hard

drive, a drive-like device,

or sound controller to a

Hyper-V virtual machine

("RDP" = "Remote

Desktop

Protocol")

Remote Desktop Connection

314


• Using virtual machines for secure Web browsing, see

http://www.suite101.com/content/use-virtualization-to-improve-desktop-security-a73715

and

http://www.mobileandsecure.co.uk/articles/safe-surfing-virtual-pc.html

and

http://superuser.com/questions/48939/virtual-machine-and-virus

and

http://www.trustware.com/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=85&cntnt01origid=15&cntnt01detailtemplate=press_detail_with_image&cntnt01returnid=56































315

APPENDIX 3

LEGAL ISSUES

OF USING VIRTUAL MACHINES

• If you are recommending, planning, or installing virtual machine software for your business, school, or other non-profit organization, please read the End User License Agreements for all virtual machine programs and guest operating system software, to determine what is legal.

316

APPENDIX 3 (continued)

LEGAL ISSUES

OF USING VIRTUAL MACHINES

–See

http://aztcs.org/meeting_notes/win

hardsig/virtualmachines/legal.pdf

http://aztcs.org/meeting_notes/winhardsig/virtualmachines/legal.pdf



http://www.slysoft.com/en/virtual-clonedrive.html

317

APPENDIX 4 TROUBLESHOOTING VIRTUAL MACHINES

IN "HYPER-V"

• See http://eniackb.blogspot.com/2009/05/how-to-recover-hyper-v-virtual-machine.html

http://eniackb.blogspot.com/2009/05/how-to-recover-hyper-v-virtual-machine.html














318

APPENDIX 4 (continued) TROUBLESHOOTING VIRTUAL MACHINES

IN "HYPER-V" (continued)

• When you do not have enough available RAM, and you attempt to start up a virtual machine, you get this error message:

321

APPENDIX 4A RESETTING A FAILED NETWORK IN A HOST

COMPUTER THAT IS RUNNING "HYPER-V"

• Step 1: Hover the mouse cursor over the lower-left corner of the Metro or "Desktop" display

• Step 2: When a thumbnail appears in the lower-left corner of the display, use the RIGHT mouse button to perform a single click.

322

APPENDIX 4A (continued) RESETTING A FAILED NETWORK.. (continued)

• Step 3: A "Power Users Menu" will pop-up.

323


• Step 4: When a thumbnail appears in the lower-left corner of the display, use the RIGHT mouse button to perform a single click.

324


• Step 5: Click on "Control Panel" in the "Power Users Menu".

325


• Step 6: A "Control Panel" windows will be displayed.

326


• Step 7: Click on "Control Panel" in the "Power Users Menu".

327


• Step 7: Double-click on "Network and Sharing Center".

328


• Step 8: Click on "Change adapter settings".

329


• Step 9: For each and every object inside the "Network Connections" window: use the RIGHT mouse button to click on the object; a pop-up context menu will be displayed; click on "Disable"; use the RIGHT mouse button to click on the object again; a pop-up context menu will be displayed; click on "Enable"

330

APPENDIX 7 NESTING VIRTUAL MACHINES

• "Hyper-V" in "Windows 8.." does

not allow the nesting of virtual

machines

331

APPENDIX 8

FREE SOFTWARE TRIALS FROM

MICROSOFT

You can download and use

software trials from Microsoft.

They provide time-limited trial

copies of their operating systems

and their application software

programs for you to use.

332

FREE SOFTWARE TRIALS FROM

MICROSOFT (continued)

• “Windows 7 Enterprise Trial” at


us/evalcenter/cc442495.aspx?ITPI

D=wtcpgs

downloads as an .ISO DVD image

file that can be installed into any

real computer or virtual machine

program.

http://technet.microsoft.com/en-us/evalcenter/cc442495.aspx?ITPID=wtcpgs




333

FREE SOFTWARE TRIALS FROM MICROSOFT

(continued)

Our general instructions for

downloading and installing

“Windows 7 Enterprise Trial” are

located at

http://aztcs.org/meeting_notes/win

hardsig/win7eval/win7eval.pdf

http://aztcs.org/meeting_notes/winhardsig/win7eval/win7eval.pdf

http://aztcs.org/meeting_notes/winhardsig/win7eval/win7eval.pdf

334


(continued)

Our specialized instructions for

installing “Windows 7 Enterprise

Trial” into a “VMware Player” virtual

machine are located at

http://aztcs.org/meeting_notes/winh

ardsig/win7intovmware/win7intovm

ware.pdf

http://aztcs.org/meeting_notes/winhardsig/win7intovmware/win7intovmware.pdf



335


(continued)

Our specialized instructions for

installing “Windows 7 Enterprise

Trial” into a “Oracle VM Virtualbox”

virtual machine are located at


ardsig/win7intovirtualbox/win7intovi

rtualbox.pdf

http://aztcs.org/meeting_notes/winhardsig/win7intovirtualbox/win7intovirtualbox.pdf



336


(continued)

• “Microsoft Office 2010” trial at

http://www2.buyoffice.microsoft.co

m/usa/?torb=4&WT.mc_id=ODC_

ENUS_GenTry_Control

downloads as an .exe file that can

be installed into any real computer

or virtual machine program.

http://www2.buyoffice.microsoft.com/usa/?torb=4&WT.mc_id=ODC_ENUS_GenTry_Control



337


(continued)

• “Internet Explorer Application

Compatibility VHD Images” at

http://www.microsoft.com/downloads/

en/details.aspx?FamilyID=21eabb90

-958f-4b64-b5f1-73d0a413c8ef

that can be used to create virtual

machines in “Windows Virtual PC”,

“Microsoft Virtual PC 2007”, or

“Oracle VM VirtualBox”.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=21eabb90-958f-4b64-b5f1-73d0a413c8ef










338


(continued)

– When any.VHD file is used to create a

virtual machine in “Oracle VM

VirtualBox”, you have to connect it to a

virtual IDE hard drive controller

(instead of the virtual SCSI hard drive

controller that is provided by default by

“Oracle VM VirtualBox”). See

http://www.sysprobs.com/virtualbox-

p2v-disk2vhd-errors-fix

http://www.sysprobs.com/virtualbox-p2v-disk2vhd-errors-fix









339

APPENDIX 9

SPEEDING UP A “WINDOWS” COMPUTER

• When you run one or more “virtual machine programs”, you will be using more RAM and CPU cycles than when you run a single host computer by itself. There is a big payoff in terms of computer performance if you tweak “Windows” host computers and virtual machines for optimum performance when you run virtual machines.

• If you run any version of “Windows” in a host computer or in a virtual machine, you can speed up “Windows” by following our detailed directions.

340

APPENDIX 9 (continued) SPEEDING UP A “WINDOWS” COMPUTER

• To speed up a “Windows 7”

computer, follow our instructions at

http://aztcs.org/meeting_notes/winhar

dsig/speedupWindows/win7speedup.

pdf




341


• To speed up a “Windows Vista”


http://aztcs.org/meeting_notes/winhar

dsig/speedupWindows/vistaspeedup.

pdf




342


• To speed up a “Windows XP”



ardsig/speedupWindows/xp_speed

up.pdf




343

APPENDIX 11 WORKAROUND FOR LACK OF FIREWIRE

SUPPORT BY VIRTUAL MACHINES

• None of the free virtual machine programs have support for firewire devices. The workaround is to use the “Shared Folders” virtual network in "VMware Player" or "Oracle VM VirtualBox" or the "Network Switch" in "Windows 8.. to attach a virtual machine to a host-connected firewire device.

344

APPENDIX 11 WORKAROUND FOR LACK OF FIREWIRE

SUPPORT.. (continued)

• See

http://aztcs.org/meeting_notes/winhardsig/virtualmachines/FirewireDevices/FirewireDevices.pdf




345

APPENDIX 13

.VHD COMPLEXITIES

• When you use “Windows..”

installation media to create a new

“virtual machine” in “Windows Virtual

PC”, you will create a new .VHD

virtual disk file.

346

APPENDIX 13

.VHD COMPLEXITIES

• When you use “Windows..”

installation media to create a new

“virtual machine” in “Microsoft Virtual

PC 2007”, you will create a new

.VHD virtual disk file.

347

APPENDIX 13

.VHD COMPLEXITIES (continued)

A .VHD file that has been created by

“Windows Virtual PC” or “Microsoft

Virtual PC 2007” when you create a

virtual machine using installation

media or that has been created by

“Windows XP Mode” cannot be used

to create a virtual machine in “Oracle

VM VirtualBox”.

348

APPENDIX 13


A .VHD file that has been created by

running the “Disk2VHD” program (to

convert a real computer (P2V) or

virtual machine (V2V)) can be used

to create a virtual machine in

“Windows Virtual PC”, “Microsoft

Virtual PC 2007”, or “Oracle VM

VirtualBox” BUT WITH TWO

EXCEPTIONS:

349

APPENDIX 13


A .VHD file that you download from

Microsoft as a time-limited software

trial can be used to create a virtual

machine in “Windows Virtual PC”,

“Microsoft Virtual PC 2007”, or

“Oracle VM VirtualBox” BUT WITH

TWO EXCEPTIONS:

350

APPENDIX 13

.VHD COMPLEXITIES (continued) Exception 1:

You cannot run a 64-bit operating system

in “Windows Virtual PC” or “Microsoft

Virtual PC 2007. This means that a .VHD

virtual hard disk file that was created by

“Disk2VHD” from a 64-bit version of

“Windows” can only be installed into

“Oracle VM VirtualBox”, into a server

version of "Windows..", or "Hyper-V"

running in "Windows 8..".

351

APPENDIX 13

.VHD COMPLEXITIES (continued) Exception 2:

When any.VHD file is used to create a

virtual machine in “Oracle VM VirtualBox”,

you have to connect it to a virtual IDE

hard drive controller (instead of the virtual

SCSI hard drive controller that is provided

by default by “Oracle VM VirtualBox”).

See

http://www.sysprobs.com/virtualbox-p2v-

disk2vhd-errors-fix










352

APPENDIX 14

UNABLE TO RUN SOME DISTROS

OF LINUX INSIDE HYPER-V

• We have been unable to

run some distros of Linux

inside Hyper-V in the

Windows 8 Release

Preview:

355

APPENDIX 15

MULTIPLE MONITORS IN

"WINDOWS 8"

• See

http://www.itproportal.com/

2012/07/17/how-to-utilise-

multiple-displays-in-

windows-8/

http://www.itproportal.com/2012/07/17/how-to-utilise-multiple-displays-in-windows-8/
















win8 hyper v

Documents

real windows

virtual machine computers

virtual machines

real computer

bundled hyperv program

enterprise version of

control panel of windows

release preview computer