WEBVTT 1 00:00:00.120 --> 00:00:00.960 When it comes time 2 00:00:00.960 --> 00:00:03.090 to install and configure your virtual machines 3 00:00:03.090 --> 00:00:04.740 when you're using virtualization, 4 00:00:04.740 --> 00:00:05.790 it's important to understand 5 00:00:05.790 --> 00:00:08.250 the different resource requirements that exist. 6 00:00:08.250 --> 00:00:09.900 When it comes to resource requirements, 7 00:00:09.900 --> 00:00:12.690 we really focus on four main areas. 8 00:00:12.690 --> 00:00:15.390 The CPU and its virtualization extensions, 9 00:00:15.390 --> 00:00:18.930 the system memory, storage and networking. 10 00:00:18.930 --> 00:00:20.580 Let's take a look at each of these. 11 00:00:20.580 --> 00:00:24.150 First, we have the CPU and its virtualization extensions. 12 00:00:24.150 --> 00:00:25.980 Now, when we talk about CPUs, 13 00:00:25.980 --> 00:00:28.710 each manufacturer, such as Intel and AMD, 14 00:00:28.710 --> 00:00:31.470 uses different technology for virtualization. 15 00:00:31.470 --> 00:00:33.420 If you're using Intel-based chips, 16 00:00:33.420 --> 00:00:36.150 you're going to be looking for VT-x, 17 00:00:36.150 --> 00:00:38.100 which is its virtualization technology, 18 00:00:38.100 --> 00:00:39.840 which stands for VT. 19 00:00:39.840 --> 00:00:41.910 If you're using an AMD processor, 20 00:00:41.910 --> 00:00:45.600 they call their virtualization extension AMD-V 21 00:00:45.600 --> 00:00:48.180 for AMD virtualization. 22 00:00:48.180 --> 00:00:50.310 Now whether you're using a hosted hypervisor 23 00:00:50.310 --> 00:00:52.080 or a bare metal hypervisor, 24 00:00:52.080 --> 00:00:54.996 both them will get significant performance gains 25 00:00:54.996 --> 00:00:57.990 if you have a CPU that supports virtualization. 26 00:00:57.990 --> 00:00:59.700 Now, some virtualization software 27 00:00:59.700 --> 00:01:01.380 does not require that a CPU 28 00:01:01.380 --> 00:01:03.600 have virtualization support enabled 29 00:01:03.600 --> 00:01:05.490 for you to be able to use virtualization. 30 00:01:05.490 --> 00:01:07.830 But if you don't have virtualization enabled 31 00:01:07.830 --> 00:01:09.360 as a processor extension, 32 00:01:09.360 --> 00:01:12.090 it is going to significantly slow down your performance. 33 00:01:12.090 --> 00:01:14.820 And you're going to have a very unusable virtual machine 34 00:01:14.820 --> 00:01:17.550 when it comes to doing some real production work. 35 00:01:17.550 --> 00:01:19.830 Now, if your processor supports virtualization 36 00:01:19.830 --> 00:01:21.750 and most modern processors do, 37 00:01:21.750 --> 00:01:23.713 you're going to have to go into the BIOS or UEFI 38 00:01:23.713 --> 00:01:27.210 to be able to enable those virtualization extensions. 39 00:01:27.210 --> 00:01:28.800 Usually, if you try installing 40 00:01:28.800 --> 00:01:30.060 a virtual machine in something 41 00:01:30.060 --> 00:01:32.070 like VirtualBox or VMware, 42 00:01:32.070 --> 00:01:33.180 and it doesn't detect that there 43 00:01:33.180 --> 00:01:34.710 is virtualization enabled, 44 00:01:34.710 --> 00:01:36.060 it will give you an error message 45 00:01:36.060 --> 00:01:39.720 telling you you need to enable VT-x or AMD-V. 46 00:01:39.720 --> 00:01:40.830 Now, in addition to these two 47 00:01:40.830 --> 00:01:42.990 virtualization technology extensions, 48 00:01:42.990 --> 00:01:45.690 there's another one out there called SLAT, 49 00:01:45.690 --> 00:01:48.540 which stands for the second level address translations. 50 00:01:48.540 --> 00:01:50.070 And this is a processor feature 51 00:01:50.070 --> 00:01:51.810 in a lot of modern processors 52 00:01:51.810 --> 00:01:53.160 that'll help improve the performance 53 00:01:53.160 --> 00:01:55.020 of virtual memory when you're running 54 00:01:55.020 --> 00:01:56.370 multiple virtual machines 55 00:01:56.370 --> 00:01:58.500 on a single physical host. 56 00:01:58.500 --> 00:02:00.540 Now, if you're using an Intel processor, 57 00:02:00.540 --> 00:02:03.690 they call SLAT as EPT, 58 00:02:03.690 --> 00:02:06.000 which is the extended page table. 59 00:02:06.000 --> 00:02:07.980 If you're using an AMD processor, 60 00:02:07.980 --> 00:02:11.160 they call SLAT as RVI, 61 00:02:11.160 --> 00:02:14.010 which is rapid virtualization indexing. 62 00:02:14.010 --> 00:02:19.010 Either way, if you see the term SLAT, EPT or RVI, 63 00:02:19.110 --> 00:02:20.430 you're really talking about the ability 64 00:02:20.430 --> 00:02:23.040 to access virtual memory in a faster method, 65 00:02:23.040 --> 00:02:24.570 and be able to get better performance 66 00:02:24.570 --> 00:02:25.590 out of your CPU. 67 00:02:25.590 --> 00:02:27.180 And it is something that your processor 68 00:02:27.180 --> 00:02:28.860 has to support for you to be able 69 00:02:28.860 --> 00:02:30.660 to use these extensions. 70 00:02:30.660 --> 00:02:31.890 Now, in addition to talking 71 00:02:31.890 --> 00:02:33.450 about virtualization extensions 72 00:02:33.450 --> 00:02:35.640 inside of our processors and CPUs, 73 00:02:35.640 --> 00:02:38.490 we also want to talk about the CPU themselves. 74 00:02:38.490 --> 00:02:40.650 If you want to have a very high performance machine 75 00:02:40.650 --> 00:02:42.360 when you're dealing with virtualization, 76 00:02:42.360 --> 00:02:43.350 you're going to want to seek out 77 00:02:43.350 --> 00:02:46.080 a processor that supports multi-core 78 00:02:46.080 --> 00:02:49.050 hyper threading or multiple physical processors 79 00:02:49.050 --> 00:02:50.640 on your given system. 80 00:02:50.640 --> 00:02:52.470 By having additional cores available, 81 00:02:52.470 --> 00:02:54.810 that means you have additional processing capability. 82 00:02:54.810 --> 00:02:56.310 If you have multiple processors, 83 00:02:56.310 --> 00:02:58.680 that means you have two or more physical processors 84 00:02:58.680 --> 00:03:00.630 installed on that motherboard. 85 00:03:00.630 --> 00:03:01.770 Now, this is fairly rare, 86 00:03:01.770 --> 00:03:04.470 unless you're using a server-based technology 87 00:03:04.470 --> 00:03:06.960 but in your desktop at home or your laptop, 88 00:03:06.960 --> 00:03:08.130 you're more likely to find 89 00:03:08.130 --> 00:03:09.990 either multicore or hyper threading 90 00:03:09.990 --> 00:03:12.810 on your processor to give you virtual cores. 91 00:03:12.810 --> 00:03:14.400 And that way it gives you additional ability 92 00:03:14.400 --> 00:03:17.760 to assign processors to your individual virtual machines 93 00:03:17.760 --> 00:03:19.560 running those guest operating systems 94 00:03:19.560 --> 00:03:21.540 and giving them more dedicated resources 95 00:03:21.540 --> 00:03:23.520 that will increase their performance. 96 00:03:23.520 --> 00:03:24.540 Now, one other side note 97 00:03:24.540 --> 00:03:25.650 when it comes to CPUs, 98 00:03:25.650 --> 00:03:27.600 remember, CPUs really come 99 00:03:27.600 --> 00:03:29.250 in three different mechanisms 100 00:03:29.250 --> 00:03:31.260 that you're going to find in the market these days. 101 00:03:31.260 --> 00:03:34.320 The first is the old school x86. 102 00:03:34.320 --> 00:03:36.720 Now, when we talk about x86-based processors, 103 00:03:36.720 --> 00:03:39.180 we're really talking about a 32-bit processor. 104 00:03:39.180 --> 00:03:41.580 And this means you're going to be significantly limited 105 00:03:41.580 --> 00:03:44.310 in your system's ability to use other things. 106 00:03:44.310 --> 00:03:45.143 Because when you're dealing 107 00:03:45.143 --> 00:03:47.130 with a 32-bit operating system, 108 00:03:47.130 --> 00:03:49.740 you can only access four gigabytes of RAM, 109 00:03:49.740 --> 00:03:51.090 which is a very small amount 110 00:03:51.090 --> 00:03:52.290 when you want to deal with hosting 111 00:03:52.290 --> 00:03:53.490 multiple virtual machines 112 00:03:53.490 --> 00:03:55.290 on a single physical server. 113 00:03:55.290 --> 00:03:58.860 Instead it's better to run an x64 base processor, 114 00:03:58.860 --> 00:04:01.560 which gives you access to up to 16 exabytes 115 00:04:01.560 --> 00:04:03.780 of RAM for your given system, 116 00:04:03.780 --> 00:04:05.850 depending on whether or not your underlying 117 00:04:05.850 --> 00:04:08.100 host operating system will support that. 118 00:04:08.100 --> 00:04:09.870 This 16 exabytes compared 119 00:04:09.870 --> 00:04:11.310 to the four gigabytes means 120 00:04:11.310 --> 00:04:14.820 we have over 4 billion times more RAM available 121 00:04:14.820 --> 00:04:17.580 if we're using an x64 base processor. 122 00:04:17.580 --> 00:04:20.070 Now, if you're running a 64-bit processor, 123 00:04:20.070 --> 00:04:22.590 you can still run 32-bit programs 124 00:04:22.590 --> 00:04:24.690 and 32-bit operating systems 125 00:04:24.690 --> 00:04:27.630 as guest operating systems on that physical server 126 00:04:27.630 --> 00:04:28.890 if you'd like to. 127 00:04:28.890 --> 00:04:30.060 The real limitation though 128 00:04:30.060 --> 00:04:32.430 is if you have a 32-bit processor, 129 00:04:32.430 --> 00:04:34.920 you cannot run 64-bit applications 130 00:04:34.920 --> 00:04:37.260 or 64-bit operating systems 131 00:04:37.260 --> 00:04:39.810 as virtual machines in a guest operating system. 132 00:04:39.810 --> 00:04:41.430 So again, it's better to go 133 00:04:41.430 --> 00:04:44.520 with an x64-based processor instead. 134 00:04:44.520 --> 00:04:45.900 Now the third type of processor 135 00:04:45.900 --> 00:04:47.587 you might come across is what's known as an ARM. 136 00:04:47.587 --> 00:04:49.890 And an ARM is reduced instruction 137 00:04:49.890 --> 00:04:51.480 set computer architecture 138 00:04:51.480 --> 00:04:53.310 for your computer processor. 139 00:04:53.310 --> 00:04:54.840 Now, where are you going to come across ARM 140 00:04:54.840 --> 00:04:56.760 processors in the fields these days? 141 00:04:56.760 --> 00:04:59.130 Well, if you're using any modern Mac, 142 00:04:59.130 --> 00:05:01.110 they all use ARM processors. 143 00:05:01.110 --> 00:05:03.210 And this is important because if you're running 144 00:05:03.210 --> 00:05:05.970 one of the modern systems, like a MacBook Pro 145 00:05:05.970 --> 00:05:07.050 or one of the new iMACs 146 00:05:07.050 --> 00:05:10.290 that's running one of these M1 or M2 processors, 147 00:05:10.290 --> 00:05:11.610 these are all ARM-based. 148 00:05:11.610 --> 00:05:13.230 And because they're ARM-based, 149 00:05:13.230 --> 00:05:16.290 they cannot natively host guest operating systems 150 00:05:16.290 --> 00:05:18.330 that are not running on ARM. 151 00:05:18.330 --> 00:05:20.880 Because there's got to be a translation that occurs. 152 00:05:20.880 --> 00:05:23.820 So for example, if you buy a Mac or a MacBook Pro 153 00:05:23.820 --> 00:05:26.760 that's using an M1 or an M1 Pro processor, 154 00:05:26.760 --> 00:05:28.530 that is an ARM-based processor. 155 00:05:28.530 --> 00:05:30.660 And if you try to install Windows 11 156 00:05:30.660 --> 00:05:33.240 or Windows 10 into a guest operating system, 157 00:05:33.240 --> 00:05:37.740 and those are x86 or x64-based operating system versions, 158 00:05:37.740 --> 00:05:40.410 they're not going to run and you're going to get errors. 159 00:05:40.410 --> 00:05:42.240 So if you're using an ARM-based processor 160 00:05:42.240 --> 00:05:43.470 on your physical system 161 00:05:43.470 --> 00:05:44.730 that you're going to be hosting 162 00:05:44.730 --> 00:05:46.320 your different virtual machines on, 163 00:05:46.320 --> 00:05:47.910 this is going to significantly limit 164 00:05:47.910 --> 00:05:49.920 your choices of guest operating systems 165 00:05:49.920 --> 00:05:51.450 because not all operating systems 166 00:05:51.450 --> 00:05:53.340 have an ARM-based version. 167 00:05:53.340 --> 00:05:54.510 At the time of this filming, 168 00:05:54.510 --> 00:05:56.400 Windows 11 is currently making 169 00:05:56.400 --> 00:05:58.560 a version for ARM-based processors 170 00:05:58.560 --> 00:06:00.990 and those will work on those ARM chips. 171 00:06:00.990 --> 00:06:02.580 And there's also Linux versions 172 00:06:02.580 --> 00:06:04.290 that are ARM-based that you can run 173 00:06:04.290 --> 00:06:07.170 on a MacBook or other ARM-based processor. 174 00:06:07.170 --> 00:06:08.250 But I just wanted to point this out 175 00:06:08.250 --> 00:06:09.510 to you because it is a limitation 176 00:06:09.510 --> 00:06:11.160 you're going to come across. 177 00:06:11.160 --> 00:06:12.150 Now, the second area we need 178 00:06:12.150 --> 00:06:13.800 to talk about in terms of resources 179 00:06:13.800 --> 00:06:15.240 is your system memory. 180 00:06:15.240 --> 00:06:16.650 When we talk about system memory, 181 00:06:16.650 --> 00:06:18.120 we're really talking about the amount 182 00:06:18.120 --> 00:06:20.070 of physical memory that's installed 183 00:06:20.070 --> 00:06:22.470 in your physical server or workstation 184 00:06:22.470 --> 00:06:25.200 that's acting as the host operating system. 185 00:06:25.200 --> 00:06:27.810 So for example, if I have eight gigabytes 186 00:06:27.810 --> 00:06:30.960 or 16 gigabytes or 32 gigabytes more 187 00:06:30.960 --> 00:06:32.400 is always better when it comes 188 00:06:32.400 --> 00:06:33.630 to hosting virtual machines, 189 00:06:33.630 --> 00:06:35.820 because if I only have eight gigabytes 190 00:06:35.820 --> 00:06:38.040 of RAM on my laptop, for example, 191 00:06:38.040 --> 00:06:39.690 and I want to run four different 192 00:06:39.690 --> 00:06:40.920 guest operating systems, 193 00:06:40.920 --> 00:06:43.320 well, if each one takes two gigabytes of RAM, 194 00:06:43.320 --> 00:06:44.580 I've already used up all 195 00:06:44.580 --> 00:06:46.170 of my physical memory and that didn't leave 196 00:06:46.170 --> 00:06:49.140 any for my underlying host operating system. 197 00:06:49.140 --> 00:06:50.550 Just to put this in perspective, 198 00:06:50.550 --> 00:06:53.160 if you're running something like Mac OS, 199 00:06:53.160 --> 00:06:55.980 this takes roughly about eight gigabytes of memory 200 00:06:55.980 --> 00:06:57.150 just to boot up Mac 201 00:06:57.150 --> 00:06:59.130 and be able to do what it needs to do. 202 00:06:59.130 --> 00:07:00.600 If you're using a Windows machine, 203 00:07:00.600 --> 00:07:03.300 generally, it takes around four gigabytes 204 00:07:03.300 --> 00:07:05.340 to be able to run Windows sufficiently 205 00:07:05.340 --> 00:07:06.720 as a host operating system. 206 00:07:06.720 --> 00:07:08.970 So if you have eight gigabytes 207 00:07:08.970 --> 00:07:10.290 and you want to run Windows 11 208 00:07:10.290 --> 00:07:13.110 as your guest inside of a Windows 10 host, 209 00:07:13.110 --> 00:07:14.820 that is going to take four plus four 210 00:07:14.820 --> 00:07:17.160 or all eight gigabytes of your memory. 211 00:07:17.160 --> 00:07:19.410 So again, when you talk about your resources, 212 00:07:19.410 --> 00:07:20.400 you really want to be looking 213 00:07:20.400 --> 00:07:22.350 at how much memory you can dedicate 214 00:07:22.350 --> 00:07:24.090 towards those guest operating systems 215 00:07:24.090 --> 00:07:25.860 and the more physical memory you have, 216 00:07:25.860 --> 00:07:28.230 the more you'll be able to do that. 217 00:07:28.230 --> 00:07:31.440 The next consideration for resources is our storage. 218 00:07:31.440 --> 00:07:33.780 And we're talking about where are you going to store 219 00:07:33.780 --> 00:07:35.850 all these virtual machine images. 220 00:07:35.850 --> 00:07:37.710 Remember, all of these virtual machines 221 00:07:37.710 --> 00:07:39.990 we're creating with their guest operating systems 222 00:07:39.990 --> 00:07:42.870 are going to take up disk space on your physical server. 223 00:07:42.870 --> 00:07:44.430 So if you have a laptop 224 00:07:44.430 --> 00:07:47.130 that only has 256 gigabytes of space, 225 00:07:47.130 --> 00:07:48.780 and you want to install a Windows 10 226 00:07:48.780 --> 00:07:51.210 guest operating system on that system, 227 00:07:51.210 --> 00:07:52.260 that's probably going to take you 228 00:07:52.260 --> 00:07:54.480 about 50 gigabytes of space. 229 00:07:54.480 --> 00:07:56.070 So you just used one fifth 230 00:07:56.070 --> 00:07:57.360 of your total hard drive 231 00:07:57.360 --> 00:07:59.610 on that one virtual machine image. 232 00:07:59.610 --> 00:08:01.860 Now, if you had three or four different copies 233 00:08:01.860 --> 00:08:03.600 of that you now have taken up 234 00:08:03.600 --> 00:08:05.130 three or four times 50, 235 00:08:05.130 --> 00:08:07.530 which is now 150 to 200 gigabytes, 236 00:08:07.530 --> 00:08:09.480 which is almost your entire disk drive. 237 00:08:09.480 --> 00:08:11.040 And so mass storage becomes 238 00:08:11.040 --> 00:08:13.080 something you really have to be aware of. 239 00:08:13.080 --> 00:08:15.390 Typically, when you're doing a Windows installation 240 00:08:15.390 --> 00:08:17.130 a barebones Windows installation 241 00:08:17.130 --> 00:08:19.440 is going to take about 20 gigabytes of space, 242 00:08:19.440 --> 00:08:22.230 but you want to use probably 40 or 50 243 00:08:22.230 --> 00:08:24.210 because you need to have additional space 244 00:08:24.210 --> 00:08:25.740 when you want to store files on there, 245 00:08:25.740 --> 00:08:28.230 install applications and things like that. 246 00:08:28.230 --> 00:08:30.000 If you're using Linux, generally, 247 00:08:30.000 --> 00:08:31.470 they are much more lightweight 248 00:08:31.470 --> 00:08:33.480 and you can find most distros will install 249 00:08:33.480 --> 00:08:36.120 in about four to eight gigabytes of space, 250 00:08:36.120 --> 00:08:38.460 which is significantly less than windows. 251 00:08:38.460 --> 00:08:40.200 If you're dealing with a Mac environment 252 00:08:40.200 --> 00:08:41.640 as a guest operating system, 253 00:08:41.640 --> 00:08:43.140 this, again, takes up usually 254 00:08:43.140 --> 00:08:45.840 around 20 to 40 gigabytes worth of space. 255 00:08:45.840 --> 00:08:47.070 So keep that in mind, 256 00:08:47.070 --> 00:08:48.630 and if you have a very limited amount 257 00:08:48.630 --> 00:08:50.730 of disk space on your physical device, 258 00:08:50.730 --> 00:08:52.050 you may want to upgrade that 259 00:08:52.050 --> 00:08:53.760 and increase your amount of storage. 260 00:08:53.760 --> 00:08:56.130 That way you can host more guest operating systems 261 00:08:56.130 --> 00:08:58.320 on that same physical server. 262 00:08:58.320 --> 00:09:01.380 And the final area we need to consider is networking. 263 00:09:01.380 --> 00:09:03.240 And this is because the hypervisor 264 00:09:03.240 --> 00:09:05.640 that's operating on the host operating system 265 00:09:05.640 --> 00:09:08.010 is going to be creating a virtual network environment 266 00:09:08.010 --> 00:09:09.690 for all of the other virtual machines 267 00:09:09.690 --> 00:09:11.220 that are being hosted on that system 268 00:09:11.220 --> 00:09:12.480 to communicate through. 269 00:09:12.480 --> 00:09:14.490 But if they all want to get out to the internet 270 00:09:14.490 --> 00:09:17.100 or out to your local area network to download files, 271 00:09:17.100 --> 00:09:17.940 they're all doing that 272 00:09:17.940 --> 00:09:20.220 through your same network interface card 273 00:09:20.220 --> 00:09:21.810 on the physical device. 274 00:09:21.810 --> 00:09:24.000 So if you're using an older networking card 275 00:09:24.000 --> 00:09:26.490 that only operates at a hundred megabits per second 276 00:09:26.490 --> 00:09:29.340 and you're running five virtual machines on that server, 277 00:09:29.340 --> 00:09:30.780 each one is effectively getting 278 00:09:30.780 --> 00:09:32.820 only 20 megabits per second. 279 00:09:32.820 --> 00:09:34.110 In this case, you would definitely 280 00:09:34.110 --> 00:09:36.090 want to upgrade your network interface card 281 00:09:36.090 --> 00:09:37.110 on the physical server 282 00:09:37.110 --> 00:09:38.280 that's hosting these guests 283 00:09:38.280 --> 00:09:40.500 and put in a gigabit networking card 284 00:09:40.500 --> 00:09:43.200 or even a 10 gigabit networking card 285 00:09:43.200 --> 00:09:45.870 if you're hosting multiple virtual machines. 286 00:09:45.870 --> 00:09:47.760 This will allow you to have additional throughput 287 00:09:47.760 --> 00:09:49.560 and bandwidth to be able to host 288 00:09:49.560 --> 00:09:50.970 all these virtual machines without 289 00:09:50.970 --> 00:09:53.280 the network becoming your slowdown. 290 00:09:53.280 --> 00:09:54.690 In addition to this as you'll learn 291 00:09:54.690 --> 00:09:56.430 in your networking studies later on, 292 00:09:56.430 --> 00:09:58.890 you can also put in multiple network interface cards 293 00:09:58.890 --> 00:10:00.030 and place them into what's known 294 00:10:00.030 --> 00:10:01.980 as a teaming configuration. 295 00:10:01.980 --> 00:10:04.500 This allows multiple cards to be working together 296 00:10:04.500 --> 00:10:06.600 in tandem to give you higher speeds. 297 00:10:06.600 --> 00:10:09.330 So if you have two, one gigabit networking cards 298 00:10:09.330 --> 00:10:10.710 and they're working in a team, 299 00:10:10.710 --> 00:10:12.540 you now have two gigabits 300 00:10:12.540 --> 00:10:13.950 of throughput that you can use 301 00:10:13.950 --> 00:10:15.330 to connect to the network. 302 00:10:15.330 --> 00:10:16.560 Often, if you're working on a server 303 00:10:16.560 --> 00:10:18.330 that's hosting lots of virtual machines 304 00:10:18.330 --> 00:10:20.310 in a corporate or enterprise environment, 305 00:10:20.310 --> 00:10:21.330 you will see they will have up 306 00:10:21.330 --> 00:10:23.130 to four network interface cards, 307 00:10:23.130 --> 00:10:24.300 all working in a team 308 00:10:24.300 --> 00:10:26.580 so they can get up to four gigabits per second 309 00:10:26.580 --> 00:10:28.680 or even up to 40 gigabits per second. 310 00:10:28.680 --> 00:10:30.840 If they're using 10 gigabit per second network 311 00:10:30.840 --> 00:10:33.240 interface cards on that particular server. 312 00:10:33.240 --> 00:10:36.090 So remember when it comes to resource requirements 313 00:10:36.090 --> 00:10:38.850 it's important to consider the CPU and the processor 314 00:10:38.850 --> 00:10:42.030 and its capabilities, as well as how much memory you have, 315 00:10:42.030 --> 00:10:44.850 how much storage you have and how much network you have. 316 00:10:44.850 --> 00:10:47.430 These four areas are all areas you want to consider. 317 00:10:47.430 --> 00:10:49.230 As you're deciding how many virtual machines 318 00:10:49.230 --> 00:10:51.900 you be able to host on a given server or workstation 319 00:10:51.900 --> 00:10:53.700 as well as how you can increase the performance 320 00:10:53.700 --> 00:10:56.250 of those guest operating systems that are being run 321 00:10:56.250 --> 00:10:59.373 inside your virtual machines on that particular hypervisor.