1 00:00:05,240 --> 00:00:06,895 In this video I'm going to explain a bit about 2 00:00:06,895 --> 00:00:10,443 hardware virtualization and the various BIOS settings 3 00:00:10,443 --> 00:00:11,986 that can disable it. 4 00:00:11,986 --> 00:00:14,316 Now laptop manufacturers, in particular, 5 00:00:14,316 --> 00:00:17,778 disable hardware virtualization in the machine's BIOS. 6 00:00:17,778 --> 00:00:19,476 So enabling it can really speed up 7 00:00:19,476 --> 00:00:23,658 the emulators, and will allow HAXM to run on Windows. 8 00:00:23,658 --> 00:00:25,258 So why is this important? 9 00:00:25,258 --> 00:00:28,178 Well the Android virtual devices, or emulators, 10 00:00:28,178 --> 00:00:31,967 that you use to test your apps are on virtual machines. 11 00:00:31,967 --> 00:00:35,036 So what that means is, a programme is running on your computer 12 00:00:35,036 --> 00:00:37,687 that behaves just like an Android device. 13 00:00:37,687 --> 00:00:39,778 It's not a real Android device, and it doesn't have 14 00:00:39,778 --> 00:00:41,687 the hardware that an Android device has. 15 00:00:41,687 --> 00:00:44,854 Instead it's all emulated in software. 16 00:00:46,943 --> 00:00:48,138 So virtual machines. 17 00:00:48,138 --> 00:00:51,195 Firstly, the cloud is built on virtualization. 18 00:00:51,195 --> 00:00:53,687 Modern hardware allows virtual machines 19 00:00:53,687 --> 00:00:56,506 to run on PCs and Laptops. 20 00:00:56,506 --> 00:00:58,138 They can run different operating systems 21 00:00:58,138 --> 00:01:00,826 on a single computer, and Virtual Machines 22 00:01:00,826 --> 00:01:03,576 use the Host computer's hardware. 23 00:01:04,578 --> 00:01:06,959 Virtualization technology has really taken off in 24 00:01:06,959 --> 00:01:08,498 the last past few years. 25 00:01:08,498 --> 00:01:11,066 In fact, the Cloud is largely built on it. 26 00:01:11,066 --> 00:01:13,108 One advantage is when you need a new web server 27 00:01:13,108 --> 00:01:15,107 to meet demand, for example. 28 00:01:15,107 --> 00:01:17,500 Using traditional hardware you'd have to install 29 00:01:17,500 --> 00:01:20,528 the operating system and all the software that it needs. 30 00:01:20,528 --> 00:01:22,284 You'd also have to run network cables 31 00:01:22,284 --> 00:01:24,157 to connect it to the network, make sure 32 00:01:24,157 --> 00:01:26,059 there are enough power sockets nearby, 33 00:01:26,059 --> 00:01:28,142 and loads of other stuff. 34 00:01:30,590 --> 00:01:34,197 By running a powerful computer that hosts virtual servers, 35 00:01:34,197 --> 00:01:35,925 you can start a new server up 36 00:01:35,925 --> 00:01:37,788 from an image really quickly. 37 00:01:37,788 --> 00:01:40,028 When demand drops again, you just shut down 38 00:01:40,028 --> 00:01:42,330 and delete the virtual machine. 39 00:01:42,330 --> 00:01:44,380 Now Virtual Machines aren't actually new. 40 00:01:44,380 --> 00:01:46,428 IBM had them in the 1960s, 41 00:01:46,428 --> 00:01:48,830 but now that we have far more powerful hardware, 42 00:01:48,830 --> 00:01:52,080 virtualization has really taken off. 43 00:01:52,320 --> 00:01:54,951 Another advantage of virtualization is that you can run 44 00:01:54,951 --> 00:01:57,769 different operating systems on the same computer 45 00:01:57,769 --> 00:01:59,551 at the same time. 46 00:01:59,551 --> 00:02:02,471 Now this is extremely useful as a developer 47 00:02:02,471 --> 00:02:06,780 because you can make sure your programme behaves correctly on different systems 48 00:02:06,780 --> 00:02:11,613 with having to actually have loads of different computers. 49 00:02:13,260 --> 00:02:15,711 You still do need a licence for each operating system 50 00:02:15,711 --> 00:02:18,282 that you want to run in a VM of course though. 51 00:02:18,282 --> 00:02:21,090 So as well as my Mac I actually have a licence for Windows 52 00:02:21,090 --> 00:02:23,311 and I can start up a Virtual Machine 53 00:02:23,311 --> 00:02:28,311 running Windows operating system right here on my Mac. 54 00:02:28,482 --> 00:02:32,122 So here I am actually running Windows 10 on my Mac. 55 00:02:32,122 --> 00:02:34,813 So you can see in the background that I've got my Mac. 56 00:02:34,813 --> 00:02:37,085 But in the foreground here, in this Window, 57 00:02:37,085 --> 00:02:41,145 I've actually got a Windows Virtual Machine running. 58 00:02:41,145 --> 00:02:44,970 So for me OS X on my machine is the host operating system, 59 00:02:44,970 --> 00:02:47,405 with Windows running as a guest. 60 00:02:47,405 --> 00:02:49,340 So it's important to remember that there's only 61 00:02:49,360 --> 00:02:51,120 a single set of hardware here. 62 00:02:51,160 --> 00:02:54,460 So the Windows guest is using the same processor, 63 00:02:54,474 --> 00:02:57,899 or processes on a multiprocessor machine, as OS X. 64 00:02:57,899 --> 00:03:01,531 So doing this on a desktop computer 10 or 15 years ago 65 00:03:01,531 --> 00:03:04,303 was possible, but was a lot slower 66 00:03:04,303 --> 00:03:07,334 than it is on average desktops these days. 67 00:03:07,334 --> 00:03:09,543 Even so running two operating systems like this one 68 00:03:09,543 --> 00:03:11,685 does slow things down a little bit. 69 00:03:11,685 --> 00:03:14,255 More importantly memory can become an issue. 70 00:03:14,255 --> 00:03:16,135 The machine, the hardware has still only got 71 00:03:16,135 --> 00:03:17,834 the same amount of RAM. 72 00:03:17,834 --> 00:03:18,976 So there has to be enough RAM installed 73 00:03:18,976 --> 00:03:21,006 for both operating systems to have access 74 00:03:21,006 --> 00:03:22,906 to what they need. 75 00:03:22,906 --> 00:03:25,735 The 64 bit version of Windows 8 or 10 requires 76 00:03:25,735 --> 00:03:28,173 two gigabytes of memory to run, minimum, and 77 00:03:28,173 --> 00:03:30,624 that's just the operating system requirements. 78 00:03:30,624 --> 00:03:33,117 So running say, a Windows 10 VM is going 79 00:03:33,117 --> 00:03:36,325 to need at least 2 gigabytes of your computer's memory. 80 00:03:36,325 --> 00:03:37,960 So on a machine with only 4 gigabytes, you can see 81 00:03:37,960 --> 00:03:41,143 that things can and will get a little bit tight. 82 00:03:41,143 --> 00:03:43,286 Just to show that this is working, I can actually 83 00:03:43,286 --> 00:03:47,156 just come up here and open something on 84 00:03:47,156 --> 00:03:48,425 Windows side of things. 85 00:03:48,425 --> 00:03:51,785 So I can open Notepad, which is a Windows desktop app. 86 00:03:51,785 --> 00:03:54,526 This is a test and so it's running quite nicely, 87 00:03:54,526 --> 00:03:56,136 and for all intents and purposes 88 00:03:56,136 --> 00:03:58,806 it actually is a full Windows installation. 89 00:03:58,806 --> 00:04:01,544 It's actually just running the computer. 90 00:04:01,544 --> 00:04:04,785 And I can go down here to About, and you can see 91 00:04:04,785 --> 00:04:07,825 I've got Windows 10 Professional Edition here. 92 00:04:07,825 --> 00:04:11,225 I've got 8 gigabytes of RAM allocated to this Virtual Machine, 93 00:04:11,225 --> 00:04:14,337 and I'm running a 64 bit edition of Windows 10. 94 00:04:14,340 --> 00:04:16,459 The other thing I can do just very quickly, 95 00:04:16,459 --> 00:04:18,060 I won't save that change, 96 00:04:18,065 --> 00:04:19,457 is I can even put this into full screen mode. 97 00:04:19,457 --> 00:04:20,516 So I'm gonna do that briefly 98 00:04:20,516 --> 00:04:21,995 and then we will swap out of it again. 99 00:04:21,995 --> 00:04:24,005 Just so you can see what actually happens. 100 00:04:24,005 --> 00:04:26,004 So I can come up here to the software 101 00:04:26,004 --> 00:04:27,723 that is running this virtualization software 102 00:04:27,723 --> 00:04:30,706 called Parallels on my Mac, and I can change this 103 00:04:30,706 --> 00:04:35,373 to full screen so let's just have a go and look at that. 104 00:04:37,341 --> 00:04:39,343 And you can see it took a moment to adjust but now 105 00:04:39,343 --> 00:04:41,300 I'm actually running it full screen. 106 00:04:41,300 --> 00:04:42,900 And again, I've got the same options I had before. 107 00:04:42,900 --> 00:04:45,908 But I can still bring my mouse up to the top here 108 00:04:45,908 --> 00:04:46,953 and still get access to the Mac menu, 109 00:04:46,960 --> 00:04:51,540 and I can come back here and click on Exit Full screen. 110 00:04:52,840 --> 00:04:54,575 And finally one other thing I can do, 111 00:04:54,575 --> 00:04:57,475 Which is where VMs are starting to blend in 112 00:04:57,475 --> 00:05:01,706 with other operating systems, I can open my notepad again 113 00:05:01,706 --> 00:05:04,698 and I can come up here to Parallels and click on View, 114 00:05:04,698 --> 00:05:08,329 and this time I'm going to go into coherence Mode. 115 00:05:08,329 --> 00:05:10,561 I'll click on yes to that. 116 00:05:10,561 --> 00:05:13,487 Coherence Mode sort of merges the two operating systems 117 00:05:13,487 --> 00:05:15,780 in terms of the interface at least. 118 00:05:15,780 --> 00:05:18,150 What I can then do, is over here 119 00:05:18,150 --> 00:05:20,849 I've got my Windows application, I've got my window. 120 00:05:20,849 --> 00:05:24,281 This is test and I'm actually running it. 121 00:05:24,281 --> 00:05:26,212 It appears that I'm running it on the Mac 122 00:05:26,212 --> 00:05:27,612 and it's not actually in a separate window. 123 00:05:27,612 --> 00:05:29,942 And I can actually come over here get access to 124 00:05:29,942 --> 00:05:34,001 Windows Start menu, like so, and I can run different apps. 125 00:05:34,001 --> 00:05:38,319 Whatever I want to do there, I could run File Explore. 126 00:05:38,319 --> 00:05:39,572 And there's my File Explorer. 127 00:05:39,572 --> 00:05:41,441 And these windows they can be dragged around. 128 00:05:41,441 --> 00:05:43,332 So you're really getting the best of both worlds 129 00:05:43,332 --> 00:05:44,801 with two operating systems. 130 00:05:44,801 --> 00:05:46,030 Even though Windows is running, 131 00:05:46,030 --> 00:05:47,961 as a separate virtual machine. 132 00:05:47,961 --> 00:05:49,382 It enables me to sort of merge them, 133 00:05:49,382 --> 00:05:51,172 I don't have to have one separate window like I did 134 00:05:51,172 --> 00:05:52,782 when I went back to this mode. 135 00:05:52,782 --> 00:05:53,982 So just get out of that mode, just go back 136 00:05:53,982 --> 00:05:57,830 to the original mode I was in before we started. 137 00:05:57,830 --> 00:05:59,869 So that's what it looks like in a window. 138 00:05:59,869 --> 00:06:03,401 All right so that's virtualization running on a Mac. 139 00:06:03,401 --> 00:06:07,151 So when does hardware virtualization come in? 140 00:06:08,441 --> 00:06:12,052 So modern Intel and AMD CPUs have additional support 141 00:06:12,052 --> 00:06:14,292 for virtualization. 142 00:06:14,292 --> 00:06:18,062 Now Virtualization Extensions on Intel CPUs 143 00:06:18,062 --> 00:06:20,012 are called VT-x or VTX. 144 00:06:20,012 --> 00:06:22,595 On AMD CPUs, it's called AMD-V. 145 00:06:23,853 --> 00:06:27,093 Now VT-x may be disabled in the BIOS, 146 00:06:27,093 --> 00:06:29,673 AMD-V is always enabled 147 00:06:29,673 --> 00:06:32,191 Additional virtualization support may be provided 148 00:06:32,191 --> 00:06:36,774 by settings such as VT-d, GVT-d/s and IOMMU. 149 00:06:38,844 --> 00:06:42,273 So enable these settings if you find them in your BIOS, 150 00:06:42,273 --> 00:06:44,439 but make a note of everything you change just in case 151 00:06:44,440 --> 00:06:46,440 you need to put it back. 152 00:06:49,260 --> 00:06:52,040 Hardware virtualization on x86 processors 153 00:06:52,206 --> 00:06:54,100 uses additional instructions, 154 00:06:54,109 --> 00:06:56,288 called virtualization extensions 155 00:06:56,288 --> 00:06:58,727 that are built into the CPU. 156 00:06:58,727 --> 00:07:01,477 CPUs with these extensions can run guest operating systems 157 00:07:01,477 --> 00:07:04,526 much more efficiently because support for the VM is 158 00:07:04,526 --> 00:07:06,701 available in hardware rather than 159 00:07:06,701 --> 00:07:09,477 having to be emulated in software. 160 00:07:09,480 --> 00:07:11,368 And there is a wealth of information available 161 00:07:11,368 --> 00:07:12,560 with these various acronyms. 162 00:07:12,720 --> 00:07:14,660 Things like we talked about on the previous page. 163 00:07:14,660 --> 00:07:17,160 VT-x VT-d et cetera. 164 00:07:19,520 --> 00:07:21,978 Basically though when you're going to look at your BIOS 165 00:07:21,978 --> 00:07:25,869 if it starts with VT- or AMD- in your BIOS 166 00:07:25,869 --> 00:07:27,218 then enable it. 167 00:07:27,218 --> 00:07:29,637 Make a careful note though of everything you change, 168 00:07:29,637 --> 00:07:31,149 and if you get any problems 169 00:07:31,149 --> 00:07:33,237 then you can turn it all off again, and re-enable 170 00:07:33,237 --> 00:07:35,317 one thing at a time, until you identify 171 00:07:35,317 --> 00:07:37,728 the one that caused the problems. 172 00:07:37,728 --> 00:07:40,349 AMD-v can't be disabled in the BIOS, so if you have an 173 00:07:40,349 --> 00:07:43,589 AMD processor that supports virtualization 174 00:07:43,589 --> 00:07:46,149 then it will already be enabled. 175 00:07:46,149 --> 00:07:47,149 Having said that, 176 00:07:47,149 --> 00:07:48,837 there are some other supporting technologies 177 00:07:48,837 --> 00:07:52,991 such as IOMMU or AMD-vi that are worth checking 178 00:07:52,991 --> 00:07:57,324 and enabling if they're disabled, even with an AMD CPU. 179 00:07:58,709 --> 00:08:00,117 So enough of the theory. 180 00:08:00,117 --> 00:08:02,828 The practical applications of this are that you may 181 00:08:02,828 --> 00:08:05,497 have a machine that supports hardware virtualization, 182 00:08:05,497 --> 00:08:08,389 but it may be disabled in your BIOS. 183 00:08:08,389 --> 00:08:11,269 Now if Android Studio successfully installed HAXM 184 00:08:11,269 --> 00:08:14,248 on a Windows or Mac computer, then everything's set up fine 185 00:08:14,248 --> 00:08:16,058 and you don't need to do anything else. 186 00:08:16,058 --> 00:08:18,237 But if you got a error installing HAXM, 187 00:08:18,237 --> 00:08:20,018 then the rest of this video should help you 188 00:08:20,018 --> 00:08:21,457 to get it working. 189 00:08:21,457 --> 00:08:22,768 Provided your computer does support 190 00:08:22,768 --> 00:08:25,218 hardware virtualization of course. 191 00:08:25,218 --> 00:08:28,502 Now we're gonna start with a note here for Mac users, 192 00:08:28,502 --> 00:08:31,496 if you have a Mac then virtualization should be enabled 193 00:08:31,496 --> 00:08:33,085 if the hardware supports it. 194 00:08:33,085 --> 00:08:37,135 All recent Macs, as far as I am aware, do fully support it. 195 00:08:37,135 --> 00:08:39,176 And I've never had a problem getting HAXM to run 196 00:08:39,176 --> 00:08:42,025 on a variety of Macs that I've owned, 197 00:08:42,025 --> 00:08:43,477 over a period of years. 198 00:08:43,477 --> 00:08:46,045 So long as you have a intel CPU, which as of the date of 199 00:08:46,045 --> 00:08:49,525 this recording, all Macs created in probably 200 00:08:49,525 --> 00:08:53,033 the last seven or eight years, are Intel only. 201 00:08:53,033 --> 00:08:54,632 You'll be good to go, and you should find 202 00:08:54,632 --> 00:08:56,616 that you have no problem. 203 00:08:56,616 --> 00:08:58,063 But if for some reason you've got some issue 204 00:08:58,063 --> 00:09:00,696 and you think VT-x should be available but it isn't, 205 00:09:00,696 --> 00:09:02,683 then you might not have possibly uploaded 206 00:09:02,683 --> 00:09:04,197 the latest firmware updates. 207 00:09:04,197 --> 00:09:06,515 Check out this page and the link will be available 208 00:09:06,515 --> 00:09:07,818 in the resources section so you don't need 209 00:09:07,818 --> 00:09:09,835 to sort of write it down. 210 00:09:09,835 --> 00:09:11,018 So have a look on there, on that page. 211 00:09:11,018 --> 00:09:12,938 If there's any information you need to know. 212 00:09:12,938 --> 00:09:14,043 If you're not getting the results you think 213 00:09:14,043 --> 00:09:17,208 you should be getting on a Mac. 214 00:09:17,208 --> 00:09:19,352 But if you're running Windows or Linux, 215 00:09:19,352 --> 00:09:23,370 and VT-x or AMD's equivalent, AMD-v isn't available, 216 00:09:23,370 --> 00:09:25,090 the first thing you should do is check 217 00:09:25,090 --> 00:09:27,471 that your hardware does actually support it. 218 00:09:27,471 --> 00:09:29,312 Searching online for your computer model 219 00:09:29,312 --> 00:09:32,261 and the text, enable hardware virtualization, 220 00:09:32,261 --> 00:09:34,882 should provide the information you need. 221 00:09:34,882 --> 00:09:37,392 Now for nonstandard or self-built computers, 222 00:09:37,392 --> 00:09:39,890 check the manual for your motherboard or search online 223 00:09:39,890 --> 00:09:40,900 for your motherboard. 224 00:09:40,900 --> 00:09:42,639 Possibly including the model number of 225 00:09:42,639 --> 00:09:45,362 the motherboard as well, which would be quite handy, 226 00:09:45,362 --> 00:09:47,560 and help you to find it and also append the words 227 00:09:47,560 --> 00:09:50,856 enable hardware virtualization. 228 00:09:50,856 --> 00:09:53,386 Now if you have a system that should support virtualization, 229 00:09:53,386 --> 00:09:56,458 then reboot the computer and press the relevant key 230 00:09:56,458 --> 00:09:58,139 to get into your BIOS. 231 00:09:58,139 --> 00:10:01,488 On many Windows systems this is the delete button or f2. 232 00:10:01,488 --> 00:10:04,917 But your manual should tell you somewhere how to do this. 233 00:10:04,917 --> 00:10:07,819 If you don't press the appropriate key in time, 234 00:10:07,819 --> 00:10:11,059 the computer will actually boot into your operating system. 235 00:10:11,059 --> 00:10:13,066 So you will have to reboot and try again. 236 00:10:13,066 --> 00:10:14,796 Some systems may require you to power off 237 00:10:14,796 --> 00:10:16,097 rather than restart. 238 00:10:16,097 --> 00:10:18,224 So bear that in mind if you're struggling. 239 00:10:18,224 --> 00:10:20,777 It's not possible to run software to record the screen 240 00:10:20,777 --> 00:10:22,369 when in BIOS settings. 241 00:10:22,369 --> 00:10:23,440 But even if I could, I'd have to swing over 242 00:10:23,440 --> 00:10:27,122 to a Windows machine and show you that machine's BIOS, 243 00:10:27,122 --> 00:10:29,493 which still may be completely different to yours. 244 00:10:29,493 --> 00:10:31,264 So if you have a manual for your motherboard, 245 00:10:31,264 --> 00:10:33,273 then you'll find all the information you need in there. 246 00:10:33,273 --> 00:10:35,652 Otherwise just make a note of your BIOS details 247 00:10:35,652 --> 00:10:39,073 and reboot so you can search online for a manual. 248 00:10:39,073 --> 00:10:40,046 Word of caution here though. 249 00:10:40,046 --> 00:10:43,544 Be very very careful what you change. 250 00:10:43,544 --> 00:10:46,696 If you don't know what something does then leave it alone 251 00:10:46,696 --> 00:10:48,435 as it could actually damage your hardware 252 00:10:48,435 --> 00:10:50,816 if you make changes to clock settings et cetera. 253 00:10:50,816 --> 00:10:53,016 Overclocking for example, requires care 254 00:10:53,016 --> 00:10:54,856 so don't be tempted to play around with those settings 255 00:10:54,856 --> 00:10:57,176 unless you really know what you're doing. 256 00:10:57,176 --> 00:10:58,646 The other thing to keep in mind is 257 00:10:58,646 --> 00:11:01,424 You can always exit from the BIOS settings without saving, 258 00:11:01,424 --> 00:11:03,800 if you inadvertently change something. 259 00:11:03,800 --> 00:11:06,680 Also make a note of every setting that you do change 260 00:11:06,680 --> 00:11:09,955 including what menu it's on, so you can undo the change 261 00:11:09,955 --> 00:11:12,395 if you start getting problems afterwards. 262 00:11:12,395 --> 00:11:13,576 This is one of those times 263 00:11:13,576 --> 00:11:15,056 where there's no digital substitute 264 00:11:15,056 --> 00:11:16,904 for a pen and a piece of paper. 265 00:11:16,904 --> 00:11:18,536 Enabling hardware virtualization 266 00:11:18,536 --> 00:11:20,246 shouldn't cause any problems. 267 00:11:20,246 --> 00:11:22,616 But as there's so many different systems available 268 00:11:22,616 --> 00:11:24,863 I can't really tell you exactly what to change. 269 00:11:24,863 --> 00:11:26,936 So it's really best to play safe 270 00:11:26,936 --> 00:11:28,824 and keep a record of everything. 271 00:11:28,824 --> 00:11:30,856 What I'm going to do is just put a couple of links on 272 00:11:30,856 --> 00:11:33,015 the screen here now. 273 00:11:33,015 --> 00:11:35,616 All these things will be available in the resources section. 274 00:11:35,616 --> 00:11:37,303 This is just giving an idea of what some of 275 00:11:37,303 --> 00:11:39,445 the BIOSes may look like. 276 00:11:39,445 --> 00:11:41,681 You can see there's an option on there. 277 00:11:41,681 --> 00:11:42,931 That's for an Award BIOS. 278 00:11:42,931 --> 00:11:44,514 But for the Lenovo. 279 00:11:46,252 --> 00:11:48,612 You'll be able to check these as I mentioned 280 00:11:48,612 --> 00:11:50,384 at a later time, that looks a little bit different 281 00:11:50,384 --> 00:11:51,217 as you can see that menu. 282 00:11:51,217 --> 00:11:52,657 But this is sort of what the BIOS is looking like 283 00:11:52,657 --> 00:11:54,311 on various computers. 284 00:11:54,311 --> 00:11:57,282 The Phoenix BIOS, they're just created 285 00:11:57,282 --> 00:11:58,820 by different manufacturers but essentially 286 00:11:58,820 --> 00:12:00,572 do the same thing. 287 00:12:00,572 --> 00:12:02,509 BIOS stands for basic input output system 288 00:12:02,509 --> 00:12:04,389 in case you're wondering. 289 00:12:04,389 --> 00:12:08,889 That's the Phoenix, then the AMD version of EUFI BIOS. 290 00:12:11,239 --> 00:12:12,572 that's that one there. 291 00:12:12,572 --> 00:12:14,351 You can see that's the more modern version, 292 00:12:14,351 --> 00:12:16,817 and we got a AMD equivalent as well. 293 00:12:16,817 --> 00:12:19,482 And that in the intel virtualization cell, 294 00:12:19,482 --> 00:12:20,911 we're setting the enabling 295 00:12:20,911 --> 00:12:22,150 the intel virtualization on there 296 00:12:22,150 --> 00:12:23,372 and looking at some of the other options. 297 00:12:23,372 --> 00:12:24,511 You can't probably see that too well but 298 00:12:24,511 --> 00:12:26,902 there's an option there for virtualization technology. 299 00:12:26,902 --> 00:12:29,644 To enable intel Virtual Technology, 300 00:12:29,644 --> 00:12:31,455 so you would enable that. 301 00:12:31,455 --> 00:12:34,331 And Virtualization Technology enabled. 302 00:12:34,331 --> 00:12:37,057 So you're looking for something along those lines. 303 00:12:37,057 --> 00:12:41,224 The last one, VT-d which is actually on an AMD BIOS. 304 00:12:42,547 --> 00:12:44,859 So once you've enable VT-x and other settings 305 00:12:44,859 --> 00:12:48,168 such as AMD-vi, IOMMU et cetera, 306 00:12:48,168 --> 00:12:49,001 you should find after you do that 307 00:12:49,001 --> 00:12:52,046 and reboot back into Windows, that you should 308 00:12:52,046 --> 00:12:54,469 be able to instal HAXM on that machine. 309 00:12:54,469 --> 00:12:57,958 Your Linux machine will also run the emulators much faster. 310 00:12:57,958 --> 00:13:00,566 Keep in mind that HAXM isn't needed on Linux. 311 00:13:00,566 --> 00:13:02,448 Because KVM automatically uses 312 00:13:02,448 --> 00:13:05,457 hardware virtualization if it's available. 313 00:13:05,467 --> 00:13:07,675 And finally if you can't get emulators running or 314 00:13:07,680 --> 00:13:10,080 They're running so slow you're getting frustrated 315 00:13:10,080 --> 00:13:12,960 remember that you can always use a physical Android device 316 00:13:13,020 --> 00:13:14,200 to test your programmes. 317 00:13:14,460 --> 00:13:15,980 Obviously you'll only be able to test on 318 00:13:15,980 --> 00:13:18,240 the version of Android that your device is running 319 00:13:18,240 --> 00:13:20,500 but for doing this course a physical device is fine 320 00:13:20,500 --> 00:13:23,400 and you can manage without running an emulator. 321 00:13:23,400 --> 00:13:25,400 That might actually be a better solution 322 00:13:25,400 --> 00:13:28,100 if your computer has only got about 4 gigabytes of RAM. 323 00:13:28,100 --> 00:13:30,000 Because you have that issue of Android, 324 00:13:30,000 --> 00:13:33,700 the image needing RAM, and by the time you're loading 325 00:13:33,700 --> 00:13:35,800 Android Studio Java et cetera, 326 00:13:35,800 --> 00:13:37,000 you're gonna be running out of memory. 327 00:13:37,000 --> 00:13:38,300 So do consider doing that. 328 00:13:38,300 --> 00:13:40,600 Particularity these days with Android devices 329 00:13:40,600 --> 00:13:42,600 being available so cheaply that it might actually 330 00:13:42,600 --> 00:13:46,000 be a better option to just grab an Android physical device, 331 00:13:46,000 --> 00:13:47,000 rather than messing around with a emulator 332 00:13:47,000 --> 00:13:49,700 if you're having lots of problems with that. 333 00:13:49,700 --> 00:13:51,340 Alright so I'm gonna finish this video here now. 334 00:13:51,580 --> 00:13:54,100 I'll see you in the next video.