1
00:00:06,450 --> 00:00:09,330
- [Instructor] Virtualization basics.

2
00:00:09,330 --> 00:00:14,330
What is the purpose of a
virtual machine or a VM?

3
00:00:14,550 --> 00:00:18,540
The purpose is to run
another operating system

4
00:00:18,540 --> 00:00:23,540
or an application internally
on a hosting platform.

5
00:00:23,940 --> 00:00:27,600
So you might have a regular PC computer

6
00:00:27,600 --> 00:00:31,440
and that might be running
Windows 8.1 or Windows 10

7
00:00:31,440 --> 00:00:32,790
or what have you.

8
00:00:32,790 --> 00:00:35,520
But inside of that, you could
run the virtual machine,

9
00:00:35,520 --> 00:00:38,340
a separate operating system that is stored

10
00:00:38,340 --> 00:00:41,760
as a file as a virtual
machine on the computer

11
00:00:41,760 --> 00:00:43,410
on the hosting computer.

12
00:00:43,410 --> 00:00:46,323
And these virtual machines
are known as guests.

13
00:00:47,460 --> 00:00:49,140
You might have wished in the past

14
00:00:49,140 --> 00:00:51,600
that you had a couple extra
computers lying around

15
00:00:51,600 --> 00:00:54,660
so that you could run
additional versions of Windows

16
00:00:54,660 --> 00:00:57,360
and run Linux, and maybe a Windows server

17
00:00:57,360 --> 00:01:01,230
with virtual software, with virtualization

18
00:01:01,230 --> 00:01:03,900
and virtual workstations, you can do this

19
00:01:03,900 --> 00:01:08,670
and you do this with Virtual
Machine Manager software,

20
00:01:08,670 --> 00:01:13,500
such as Hyper-V or VirtualBox or VMware.

21
00:01:13,500 --> 00:01:16,920
And remember the two types
you've got the type one

22
00:01:16,920 --> 00:01:18,810
which is native.

23
00:01:18,810 --> 00:01:20,490
And that means that the hypervisor

24
00:01:20,490 --> 00:01:23,730
or the Virtual Machine
Manager runs directly

25
00:01:23,730 --> 00:01:25,950
on the host computers hardware.

26
00:01:25,950 --> 00:01:29,640
That's also known as bare
metal and you've got type two.

27
00:01:29,640 --> 00:01:31,470
That type two hypervisor

28
00:01:31,470 --> 00:01:35,670
or Virtual Machine
Manager is one that runs

29
00:01:35,670 --> 00:01:37,740
inside of the operating system.

30
00:01:37,740 --> 00:01:41,310
And so guests run within
that hypervisor instead of

31
00:01:41,310 --> 00:01:44,670
directly on the bare metal
directly on the hardware.

32
00:01:44,670 --> 00:01:46,620
So type two is not gonna be as quick

33
00:01:46,620 --> 00:01:49,800
but it'll usually be cheaper if not free

34
00:01:49,800 --> 00:01:52,680
and a little bit if an easier solution.

35
00:01:52,680 --> 00:01:54,870
But if you're in a high tech situation

36
00:01:54,870 --> 00:01:56,643
you wanna go with the type one.

37
00:01:58,590 --> 00:02:00,840
Resource requirements.

38
00:02:00,840 --> 00:02:02,100
You have to make sure

39
00:02:02,100 --> 00:02:04,680
that the system that will host

40
00:02:04,680 --> 00:02:07,560
the Virtual Machine Manager software

41
00:02:07,560 --> 00:02:10,830
has the right virtualization extensions.

42
00:02:10,830 --> 00:02:13,170
So you need to make sure that you have

43
00:02:13,170 --> 00:02:16,050
the extensions for the CPU

44
00:02:16,050 --> 00:02:21,050
and for Intel that's VT-x and
for AMD CPUs, that's AMD-V.

45
00:02:21,300 --> 00:02:24,180
Those need to be enabled in the firmware

46
00:02:24,180 --> 00:02:29,180
within your BIOS or UFI and
most new UFI systems have this.

47
00:02:30,750 --> 00:02:34,080
Also, you have virtualization
extensions for the chip set.

48
00:02:34,080 --> 00:02:36,130
For Intel that's VT-d

49
00:02:37,080 --> 00:02:39,060
and VT-c.

50
00:02:39,060 --> 00:02:43,710
VT-d is for input output memory management

51
00:02:43,710 --> 00:02:47,370
and VT-c is for network virtualization.

52
00:02:47,370 --> 00:02:49,470
And on the AMD side for the chip set

53
00:02:49,470 --> 00:02:53,310
you have the AMD-Vi extension.

54
00:02:53,310 --> 00:02:55,710
So you wanna make sure that those are

55
00:02:55,710 --> 00:02:57,543
enabled in the firmware.

56
00:02:58,410 --> 00:03:02,070
Now different machine managers will have

57
00:03:02,070 --> 00:03:03,960
different requirements.

58
00:03:03,960 --> 00:03:06,570
And this also depends
on the amount of hosts

59
00:03:06,570 --> 00:03:09,420
that you'll be supporting
within that software.

60
00:03:09,420 --> 00:03:12,030
If you look here, I have an older system

61
00:03:12,030 --> 00:03:15,870
from Microsoft Virtual
Machine Manager 2007

62
00:03:15,870 --> 00:03:20,820
and this shows what types
of requirements you need

63
00:03:20,820 --> 00:03:25,820
if you have five to 10 hosts,
or if you have 11 to 20 hosts

64
00:03:26,490 --> 00:03:30,360
and you can see the recommended
processor is about the same

65
00:03:30,360 --> 00:03:34,470
but the RAM goes up and the
hard drive space goes up.

66
00:03:34,470 --> 00:03:36,480
Now newer systems will need even more.

67
00:03:36,480 --> 00:03:40,980
Hyper-V recommends that you
have even more memory available

68
00:03:40,980 --> 00:03:43,350
per guest operating system.

69
00:03:43,350 --> 00:03:46,920
If we take a look at Windows 10 Hyper-V

70
00:03:46,920 --> 00:03:48,990
we'll see that you can easily find out

71
00:03:48,990 --> 00:03:50,760
if you meet the Hyper-V requirements

72
00:03:50,760 --> 00:03:53,130
by typing systeminfo.exe

73
00:03:53,130 --> 00:03:55,200
and we'll do that later in the lesson.

74
00:03:55,200 --> 00:03:58,860
And you can see here, the
VM monitor mode extensions,

75
00:03:58,860 --> 00:04:01,350
the firmware needs to be enabled,

76
00:04:01,350 --> 00:04:03,240
the second level address translation,

77
00:04:03,240 --> 00:04:06,420
and DEP or data execution prevention.

78
00:04:06,420 --> 00:04:08,940
All these have to say yes
for you to run Hyper-V.

79
00:04:08,940 --> 00:04:10,950
So you wanna check that
before you actually do that

80
00:04:10,950 --> 00:04:13,530
on a Windows 8.1 or 10 system.

81
00:04:13,530 --> 00:04:16,080
So different requirements,
depending on the amount of hosts

82
00:04:16,080 --> 00:04:19,530
and it's different based
on which program you use.

83
00:04:19,530 --> 00:04:22,770
A type two hypervisor or a type two VMM

84
00:04:22,770 --> 00:04:25,590
such as VirtualBox won't have as much

85
00:04:25,590 --> 00:04:27,510
as far as resource requirements

86
00:04:27,510 --> 00:04:31,830
as say Hyper-V for Windows server 2012.

87
00:04:31,830 --> 00:04:34,470
Then there's the network requirements.

88
00:04:34,470 --> 00:04:36,510
And you need to make sure that your

89
00:04:36,510 --> 00:04:40,050
Virtual Machine Manager can
work with your network card,

90
00:04:40,050 --> 00:04:41,730
your network adapter on your system

91
00:04:41,730 --> 00:04:45,360
because not all network
adapters are compliant

92
00:04:45,360 --> 00:04:48,480
with virtualization software.

93
00:04:48,480 --> 00:04:50,460
So you wanna make sure the
virtual network adapter

94
00:04:50,460 --> 00:04:52,323
is compatible with your VMM.

95
00:04:53,790 --> 00:04:57,840
And then as a kind of, as
a general rule of thumb

96
00:04:57,840 --> 00:05:00,930
you wanna make sure that you
have 20 megabits per second

97
00:05:00,930 --> 00:05:04,800
per virtual machine, as a bare minimum

98
00:05:04,800 --> 00:05:07,110
for that connectivity through the network.

99
00:05:07,110 --> 00:05:08,520
Because you can throttle this

100
00:05:08,520 --> 00:05:11,310
by the virtual machine, if you need to.

101
00:05:11,310 --> 00:05:12,660
And you want to have more than that

102
00:05:12,660 --> 00:05:16,110
if high data transfer or
multimedia is involved.

103
00:05:16,110 --> 00:05:19,200
But generally I like to go
with 20 megabits per second,

104
00:05:19,200 --> 00:05:22,980
as connectivity for one particular guy

105
00:05:22,980 --> 00:05:25,890
as just a basic connection.

106
00:05:25,890 --> 00:05:29,763
Now, if you're gonna be
transferring video or what have you,

107
00:05:30,810 --> 00:05:33,270
that number's gonna get a lot higher.

108
00:05:33,270 --> 00:05:36,300
So you're gonna want to
check this on your systems

109
00:05:36,300 --> 00:05:38,640
and verify that you have
the amount of bandwidth

110
00:05:38,640 --> 00:05:42,840
that you need 20 megabits
per second, per VM

111
00:05:42,840 --> 00:05:45,060
as a bare minimum.

112
00:05:45,060 --> 00:05:48,210
And then also you can calculate
the typical amount of data

113
00:05:48,210 --> 00:05:49,950
that will be transferred.

114
00:05:49,950 --> 00:05:51,690
You might have a server system

115
00:05:51,690 --> 00:05:54,990
or a powerful Linux system
running as a virtual machine

116
00:05:54,990 --> 00:05:56,010
or you might have a

117
00:05:56,010 --> 00:05:58,830
separate Windows 10 system
running as virtual machine

118
00:05:58,830 --> 00:06:01,980
that has to constantly
move data back and forth.

119
00:06:01,980 --> 00:06:04,050
And you wanna think
about how long it takes

120
00:06:04,050 --> 00:06:05,790
to move that data.

121
00:06:05,790 --> 00:06:08,670
For example, if you have
10 gigabytes of data

122
00:06:08,670 --> 00:06:11,970
that will take approximately two minutes

123
00:06:11,970 --> 00:06:14,130
on a one gigabyte per second network

124
00:06:14,130 --> 00:06:16,740
if the entire channel is available

125
00:06:16,740 --> 00:06:19,560
but if you have other
guest operating systems

126
00:06:19,560 --> 00:06:22,860
then you wanna make sure that
you're calculating properly.

127
00:06:22,860 --> 00:06:25,440
You're gonna have to divvy
up the total bandwidth,

128
00:06:25,440 --> 00:06:28,980
the total network throughput

129
00:06:28,980 --> 00:06:32,010
amongst the different
guest operating systems

130
00:06:32,010 --> 00:06:34,617
and the hosts that are using that system.

131
00:06:34,617 --> 00:06:37,440
The physical hosts that
are using that system.

132
00:06:37,440 --> 00:06:39,690
So you wanna think about
those network requirements.

133
00:06:39,690 --> 00:06:44,040
And if we go over here to
VMware, VMware has a page

134
00:06:44,040 --> 00:06:46,080
where you can calculate
the bandwidth requirements

135
00:06:46,080 --> 00:06:49,830
for vSphere and for other types of

136
00:06:49,830 --> 00:06:52,140
virtual machines that
you might use with them.

137
00:06:52,140 --> 00:06:54,153
And it really gets into depth with that.

138
00:06:55,800 --> 00:06:58,860
And so you wanna take into
account your link speed.

139
00:06:58,860 --> 00:07:00,150
You wanna take into account

140
00:07:00,150 --> 00:07:03,390
what type of hardware you're
using, how many hosts there are

141
00:07:03,390 --> 00:07:06,540
on the physical side
and on the virtual side

142
00:07:06,540 --> 00:07:08,910
and put that all together
to think about, okay

143
00:07:08,910 --> 00:07:10,950
what are our network requirements?

144
00:07:10,950 --> 00:07:13,500
Do we need a new switch?

145
00:07:13,500 --> 00:07:17,760
Do we need a new router
to control all these

146
00:07:17,760 --> 00:07:19,800
virtual machines that'll be sending data?

147
00:07:19,800 --> 00:07:22,440
How much data will the
virtual machines be sending?

148
00:07:22,440 --> 00:07:27,300
And finally for the hosting
computer or computers

149
00:07:27,300 --> 00:07:30,660
that are running the Virtual
Machine Manager software again

150
00:07:30,660 --> 00:07:33,060
make sure the virtual
network adapter is compatible

151
00:07:33,060 --> 00:07:34,203
with that software.

152
00:07:35,580 --> 00:07:38,790
Next is security requirements.

153
00:07:38,790 --> 00:07:41,970
The security of the virtual
machine should be similar

154
00:07:41,970 --> 00:07:44,640
to the physical host security.

155
00:07:44,640 --> 00:07:47,730
So the actual PC or server that you have

156
00:07:47,730 --> 00:07:50,700
the physical box is gonna have
a certain level of security.

157
00:07:50,700 --> 00:07:53,070
You wanna make sure that
that device is secure

158
00:07:53,070 --> 00:07:54,240
but also the security

159
00:07:54,240 --> 00:07:56,610
of the virtual machines
running inside of that guy

160
00:07:56,610 --> 00:07:58,930
they should be similar to that security

161
00:07:59,820 --> 00:08:03,750
or equivalent to that physical
machine's operating system.

162
00:08:03,750 --> 00:08:06,930
The virtual machine should be
updated to the latest patches,

163
00:08:06,930 --> 00:08:10,140
the latest service pack, whatever
version of Windows it is,

164
00:08:10,140 --> 00:08:11,340
the latest updates.

165
00:08:11,340 --> 00:08:13,590
If you have multiple virtual machines

166
00:08:13,590 --> 00:08:16,860
especially ones that are going
to interact with each other

167
00:08:16,860 --> 00:08:19,650
you make sure that they're
updated in the same manner.

168
00:08:19,650 --> 00:08:21,300
They should be at the same point release

169
00:08:21,300 --> 00:08:24,000
of the operating system
or the same service pack.

170
00:08:24,000 --> 00:08:26,130
And that ensures patch compatibility

171
00:08:26,130 --> 00:08:27,960
between the virtual machines.

172
00:08:27,960 --> 00:08:29,790
The virtual machine should have the latest

173
00:08:29,790 --> 00:08:32,280
antivirus definitions.

174
00:08:32,280 --> 00:08:35,280
Perhaps it should have a firewall enabled.

175
00:08:35,280 --> 00:08:37,350
It should have strong passwords.

176
00:08:37,350 --> 00:08:39,060
All of the security that you would do

177
00:08:39,060 --> 00:08:40,590
with the regular physical host.

178
00:08:40,590 --> 00:08:43,080
And we'll be talking more about security

179
00:08:43,080 --> 00:08:44,763
as we move on through the course.

180
00:08:45,690 --> 00:08:47,910
But there are a lot of
other things to watch for

181
00:08:47,910 --> 00:08:51,720
that if not addressed
could really cause problems

182
00:08:51,720 --> 00:08:55,353
with your virtual machines and
even your hosting computer.

183
00:08:56,640 --> 00:08:58,440
So first you wanna make
sure you update that

184
00:08:58,440 --> 00:08:59,880
virtual machine software.

185
00:08:59,880 --> 00:09:02,580
If you're running VirtualBox
or if you're running Hyper-V

186
00:09:02,580 --> 00:09:04,020
or you're running VMware

187
00:09:04,020 --> 00:09:06,000
you wanna make sure that guy is updated

188
00:09:06,000 --> 00:09:08,790
because that's gonna
patch some security holes

189
00:09:08,790 --> 00:09:10,290
and have it perform better

190
00:09:10,290 --> 00:09:13,443
with the latest OS within
the virtual system.

191
00:09:15,300 --> 00:09:18,270
Configure any applicable security settings

192
00:09:18,270 --> 00:09:21,723
and options within that virtual
machine software as well.

193
00:09:23,130 --> 00:09:27,480
Watch out for network shares
within the virtual machine.

194
00:09:27,480 --> 00:09:30,750
You might have network shares
between the virtual machine

195
00:09:30,750 --> 00:09:35,750
and the physical computer or
between two virtual machines.

196
00:09:35,880 --> 00:09:40,800
And by default malicious
software and attacks

197
00:09:40,800 --> 00:09:45,210
cannot travel between one
virtual machine and another.

198
00:09:45,210 --> 00:09:50,210
But if you create a network
share between the two malware

199
00:09:50,880 --> 00:09:53,940
and attacks could easily go
from one system to the other.

200
00:09:53,940 --> 00:09:55,830
So you have to be careful
with network shares.

201
00:09:55,830 --> 00:09:58,830
If a network share is needed, map it

202
00:09:58,830 --> 00:10:02,580
then use it and then disconnect
it when you're finished

203
00:10:02,580 --> 00:10:06,180
and document where those
network shares are.

204
00:10:06,180 --> 00:10:08,970
If you're done with it you
should just disconnect it

205
00:10:08,970 --> 00:10:11,610
or better yet when you set
up the mapped network drive

206
00:10:11,610 --> 00:10:15,810
in Windows you'll see that
option reconnect at logon

207
00:10:15,810 --> 00:10:18,990
and just go ahead and
deselect that this way

208
00:10:18,990 --> 00:10:21,240
when you log off and log back on

209
00:10:21,240 --> 00:10:23,160
or restart the virtual machine

210
00:10:23,160 --> 00:10:25,350
that mapped network drive will be gone.

211
00:10:25,350 --> 00:10:27,783
So watch out for a mapped network drives.

212
00:10:28,620 --> 00:10:31,590
Disable any unnecessary hardware

213
00:10:31,590 --> 00:10:34,440
and you could do this from
within the virtual machine.

214
00:10:34,440 --> 00:10:37,380
Optical drives USB ports.

215
00:10:37,380 --> 00:10:39,720
If there's any type of removable media

216
00:10:39,720 --> 00:10:42,930
that you need to use enable the device,

217
00:10:42,930 --> 00:10:47,340
make use of it, and then disable
it immediately afterwards.

218
00:10:47,340 --> 00:10:50,640
Now you can disable these
devices within the OS,

219
00:10:50,640 --> 00:10:54,240
the virtual OS, say
within the device manager

220
00:10:54,240 --> 00:10:56,700
but quite often, devices
can also be disabled

221
00:10:56,700 --> 00:11:00,780
within the Virtual Machine
Manager software as well.

222
00:11:00,780 --> 00:11:02,880
And if you have a virtual BIOS

223
00:11:02,880 --> 00:11:06,300
or UFI check the boot priority

224
00:11:06,300 --> 00:11:08,370
and make sure that it
sets a hard drive first

225
00:11:08,370 --> 00:11:11,283
just like you would with
a physical computer.

226
00:11:12,390 --> 00:11:16,470
Limit the resources a
virtual machine can use.

227
00:11:16,470 --> 00:11:18,810
A compromised virtual
machine can be a threat

228
00:11:18,810 --> 00:11:21,390
in the form of a denial of service attack.

229
00:11:21,390 --> 00:11:23,160
But if you limit the amount of resources

230
00:11:23,160 --> 00:11:26,040
especially on the network side of things

231
00:11:26,040 --> 00:11:28,710
you could eliminate that possibility.

232
00:11:28,710 --> 00:11:32,160
And you want to throttle
this network activity.

233
00:11:32,160 --> 00:11:34,620
To mitigate this you
could just set a limit

234
00:11:34,620 --> 00:11:35,970
on the amount of resources

235
00:11:35,970 --> 00:11:38,490
any particular virtual
machine can utilize.

236
00:11:38,490 --> 00:11:40,200
The better the hypervisor,

237
00:11:40,200 --> 00:11:42,210
the better the Virtual Machine Manager

238
00:11:42,210 --> 00:11:44,820
the more power you'll have with this.

239
00:11:44,820 --> 00:11:46,620
So if you're using Hyper-V or VMware

240
00:11:46,620 --> 00:11:48,873
you can easily throttle this.

241
00:11:49,830 --> 00:11:54,330
Also periodically monitor the
usage of the virtual machine.

242
00:11:54,330 --> 00:11:56,220
But you wanna be careful with monitoring.

243
00:11:56,220 --> 00:11:59,580
Enable it only for
authorized users, admins,

244
00:11:59,580 --> 00:12:02,583
and disable the monitoring
whenever it's not necessary.

245
00:12:04,410 --> 00:12:08,460
Next protect the raw
virtual machine files.

246
00:12:08,460 --> 00:12:11,040
The virtual machine is just one big file.

247
00:12:11,040 --> 00:12:13,800
It's almost, you could consider an image,

248
00:12:13,800 --> 00:12:15,690
a file on the hard drive.

249
00:12:15,690 --> 00:12:19,860
So you wanna protect that
raw virtual disc file

250
00:12:19,860 --> 00:12:22,740
because if something was
to go wrong with that file

251
00:12:22,740 --> 00:12:25,290
the whole virtual machine is gone.

252
00:12:25,290 --> 00:12:28,590
So look into setting permissions

253
00:12:28,590 --> 00:12:32,223
for who can access the folder
where the VM files are stored.

254
00:12:33,060 --> 00:12:36,690
And if your virtual machine
software supports logging

255
00:12:36,690 --> 00:12:40,440
or auditing, consider implementing that

256
00:12:40,440 --> 00:12:41,730
and see exactly who

257
00:12:41,730 --> 00:12:45,003
started or stopped the
virtual machine and when.

258
00:12:46,230 --> 00:12:47,670
Otherwise in Windows

259
00:12:47,670 --> 00:12:51,270
you can audit the folder where
the VM files are located.

260
00:12:51,270 --> 00:12:52,860
And finally, you can make a copy

261
00:12:52,860 --> 00:12:54,240
of the virtual machine file.

262
00:12:54,240 --> 00:12:56,310
You know, every once in a
while, you should back it up,

263
00:12:56,310 --> 00:12:58,230
make a snapshot of that guy.

264
00:12:58,230 --> 00:13:03,180
You can also encrypt the disc
file and digitally sign it

265
00:13:03,180 --> 00:13:06,840
and validate that
signature prior to usage.

266
00:13:06,840 --> 00:13:10,713
And last comment protect the
hosting computer as well.

267
00:13:11,910 --> 00:13:14,670
The virtual machine should
be as secure as possible

268
00:13:14,670 --> 00:13:17,490
but it's only as secure
as the hosting computer

269
00:13:17,490 --> 00:13:19,140
that's in the controlling position

270
00:13:19,140 --> 00:13:22,350
the computer that's
running the VMM software.

271
00:13:22,350 --> 00:13:25,530
So harden that computer

272
00:13:25,530 --> 00:13:30,063
and then harden the virtual
machines in a similar manner.

273
00:13:31,440 --> 00:13:34,950
Let's show a quick example
of a virtualization program.

274
00:13:34,950 --> 00:13:37,890
This is Oracle VirtualBox

275
00:13:37,890 --> 00:13:40,590
and this is the VirtualBox manager.

276
00:13:40,590 --> 00:13:44,010
This is the Virtual
Machine Manager software.

277
00:13:44,010 --> 00:13:47,340
This is a type two hypervisor.

278
00:13:47,340 --> 00:13:49,320
It runs within the operating system.

279
00:13:49,320 --> 00:13:52,590
It's not bare bones, but
it's good for my purposes

280
00:13:52,590 --> 00:13:55,230
for training and it's good for testing.

281
00:13:55,230 --> 00:13:56,730
So this works pretty well,

282
00:13:56,730 --> 00:13:59,340
but if you're gonna have
systems in production,

283
00:13:59,340 --> 00:14:02,343
then you want to have a type
one hypervisor of some sort.

284
00:14:03,240 --> 00:14:05,100
And you could see the list of

285
00:14:05,100 --> 00:14:07,890
virtual machines that I'm
running here, I have Ubuntu,

286
00:14:07,890 --> 00:14:09,870
I've got Windows Server 2012,

287
00:14:09,870 --> 00:14:11,670
I've got an old version of Windows XP,

288
00:14:11,670 --> 00:14:13,980
just in case a question comes up on it.

289
00:14:13,980 --> 00:14:16,890
Windows 7, Windows 10, Windows 8,

290
00:14:16,890 --> 00:14:19,620
everything is here and
all of these are separate

291
00:14:19,620 --> 00:14:21,510
virtual machine files,

292
00:14:21,510 --> 00:14:24,030
but they're all stored in
the same place on a drive.

293
00:14:24,030 --> 00:14:25,890
So you gotta be careful with this.

294
00:14:25,890 --> 00:14:28,260
You wanna make sure that
you protect those files.

295
00:14:28,260 --> 00:14:30,990
And then you can see the
settings for each of these.

296
00:14:30,990 --> 00:14:33,780
You can see the amount of
memory that I've assigned

297
00:14:33,780 --> 00:14:35,280
to the virtual machine,

298
00:14:35,280 --> 00:14:38,580
and you can see how much
video memory it's using.

299
00:14:38,580 --> 00:14:40,680
You can find out
information about the audio,

300
00:14:40,680 --> 00:14:42,240
the network, the USB.

301
00:14:42,240 --> 00:14:45,720
If we were to click on one
and then go to settings

302
00:14:45,720 --> 00:14:47,973
we'd get even more information about this.

303
00:14:49,260 --> 00:14:51,153
Where the file is stored,

304
00:14:52,440 --> 00:14:55,680
how much memory we're using,
which we can modify here.

305
00:14:55,680 --> 00:14:57,540
The boot order, as I mentioned before

306
00:14:57,540 --> 00:15:00,273
make sure that hard disc
is first in the list.

307
00:15:01,230 --> 00:15:03,330
Chip set compatibility,

308
00:15:03,330 --> 00:15:06,090
the mouse or pointing
device that you're using,

309
00:15:06,090 --> 00:15:08,040
additional features.

310
00:15:08,040 --> 00:15:11,310
For example, EFI, which we
definitely would want to enable

311
00:15:11,310 --> 00:15:14,130
on say Windows Vista or higher

312
00:15:14,130 --> 00:15:16,020
and some other operating systems.

313
00:15:16,020 --> 00:15:18,180
There's tons of stuff here to look at

314
00:15:18,180 --> 00:15:20,913
as far as what you're
doing with the system.

315
00:15:22,410 --> 00:15:25,320
Audio network, serial ports, USB.

316
00:15:25,320 --> 00:15:28,320
And again, if you're not
gonna use something like USB

317
00:15:28,320 --> 00:15:31,980
on this system then
disable it all together,

318
00:15:31,980 --> 00:15:32,880
right from here.

319
00:15:32,880 --> 00:15:33,933
Just get rid of it.

320
00:15:35,190 --> 00:15:38,670
No need to go ahead and disable
it in the device manager

321
00:15:38,670 --> 00:15:40,680
within the virtual
machine operating system

322
00:15:40,680 --> 00:15:42,780
because we've disabled it right here

323
00:15:42,780 --> 00:15:45,120
from the Virtual Machine Manager.

324
00:15:45,120 --> 00:15:48,933
So that could be very powerful
more higher level control.

325
00:15:50,280 --> 00:15:53,010
Shared folders, we mentioned this can be,

326
00:15:53,010 --> 00:15:55,325
this could be deadly when it comes

327
00:15:55,325 --> 00:15:57,750
to malware and when it comes to attacks.

328
00:15:57,750 --> 00:16:01,470
So monitor these shared
folders within here as well.

329
00:16:01,470 --> 00:16:03,780
So you can see all this stuff from here.

330
00:16:03,780 --> 00:16:07,140
And this is just a very basic example

331
00:16:07,140 --> 00:16:09,060
of a virtualization program

332
00:16:09,060 --> 00:16:11,070
but something that you
can download for free.

333
00:16:11,070 --> 00:16:11,940
So I would say,

334
00:16:11,940 --> 00:16:15,030
go and check out the latest
version of VirtualBox,

335
00:16:15,030 --> 00:16:18,780
download it, and you could
download Ubuntu for free

336
00:16:18,780 --> 00:16:20,640
and there's plenty of other types of Linux

337
00:16:20,640 --> 00:16:21,930
you could download for free.

338
00:16:21,930 --> 00:16:25,230
Install that directly to a virtual machine

339
00:16:25,230 --> 00:16:26,820
and see how it works.

340
00:16:26,820 --> 00:16:28,650
And we'll show a little bit more with this

341
00:16:28,650 --> 00:16:32,370
and other Virtual Machine
Manager software programs

342
00:16:32,370 --> 00:16:35,010
in the last sub lesson of this lesson.

343
00:16:35,010 --> 00:16:36,930
So that's about it for this one.

344
00:16:36,930 --> 00:16:40,200
Again, make sure that you're
checking your requirements

345
00:16:40,200 --> 00:16:42,780
your network requirements,
your system requirements

346
00:16:42,780 --> 00:16:44,760
and your security requirements,

347
00:16:44,760 --> 00:16:47,070
and make sure that they will all work

348
00:16:47,070 --> 00:16:49,410
with the software you wanna run

349
00:16:49,410 --> 00:16:51,990
within the virtual
machine and make sure that

350
00:16:51,990 --> 00:16:54,933
your hosting computer can
support all this as well.