|
| 1 | +# Check Tool for Intel Hardware Accelerated Execution Manager |
| 2 | + |
| 3 | +It is required that the host operating system to meet the environmental |
| 4 | +requirements to install HAXM. These requirements include Intel CPU verdor, |
| 5 | +enabling VMX, disabling Hyper-V, etc. Only when all the requirements are met, |
| 6 | +HAXM can be installed and executed properly. These wiki pages (installation |
| 7 | +instructions on [Windows][install-on-windows] and [macOS][install-on-macos]) |
| 8 | +describe the configuration methods of HAXM installation prerequisites. |
| 9 | + |
| 10 | +This utility is a command line tool for system checking for HAXM. It is used to |
| 11 | +help user to check the status of each condition in the current system |
| 12 | +environment, so as to determine whether the hardware configuration meets the |
| 13 | +requirements or which system settings need to be changed. This software |
| 14 | +currently supports running on Windows and macOS. |
| 15 | + |
| 16 | +## Downloads |
| 17 | + |
| 18 | +The latest release of HAXM **Check Tool** for Windows and macOS hosts are |
| 19 | +available [here][checktool-release]. |
| 20 | + |
| 21 | +## Windows |
| 22 | + |
| 23 | +### Usage |
| 24 | + |
| 25 | +1. `cd X:\path\to\CheckTool` |
| 26 | +1. `checktool.exe --verbose` |
| 27 | + |
| 28 | +The output will be as below. |
| 29 | + |
| 30 | + CPU vendor * GenuineIntel |
| 31 | + Intel64 supported * Yes |
| 32 | + VMX supported * Yes |
| 33 | + VMX enabled * Yes |
| 34 | + EPT supported * Yes |
| 35 | + NX supported * Yes |
| 36 | + NX enabled * Yes |
| 37 | + Hyper-V disabled - No |
| 38 | + OS version * Windows 10.0.18363 |
| 39 | + OS architecture * x86_64 |
| 40 | + Guest unoccupied * Yes. 0 guest(s) |
| 41 | + |
| 42 | +"*" represents the item is passed, while "-" represents the item is failed. |
| 43 | + |
| 44 | +### Build |
| 45 | + |
| 46 | +#### Prerequisites |
| 47 | + |
| 48 | +[Visual Studio][visualstudio] 2017 or later |
| 49 | + |
| 50 | +Install the following components: **Desktop development with C++** (**C++ CMake |
| 51 | +tools for Windows** is included) |
| 52 | + |
| 53 | +#### Build steps |
| 54 | + |
| 55 | +**Option A (Visual Studio)** |
| 56 | + |
| 57 | +1. Open _CheckTool_ project in Visual Studio. |
| 58 | + |
| 59 | + **File** > **Open** > **Folder...** > **Select Folder** "CheckTool" |
| 60 | + (containing _CMakeLists.txt_) |
| 61 | +1. Select proper configuration, e.g., "x86-Debug". |
| 62 | +1. Build project. |
| 63 | + |
| 64 | + **Build** > **Build All** |
| 65 | + |
| 66 | +The executable program (_checktool.exe_) will be generated in |
| 67 | +_X:\path\to\CheckTool\build\x86-Debug\\_. The 32-bit executable can run on both |
| 68 | +32-bit and 64-bit Windows, while the 64-bit executable can run on 64-bit Windows |
| 69 | +only. |
| 70 | + |
| 71 | +**Option B (CMake)** |
| 72 | + |
| 73 | +1. `set PATH=C:\Program Files (x86)\Microsoft Visual ` |
| 74 | +`Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;%PATH%` |
| 75 | +1. `cd X:\path\to\CheckTool` |
| 76 | +1. `mkdir build && cd build && cmake .. && cmake --build .` |
| 77 | + |
| 78 | +The executable program (_checktool.exe_) will be generated in |
| 79 | +_X:\path\to\CheckTool\build\Debug\\_. It is easy to clean the build just by |
| 80 | +removing the _build_ folder manually. |
| 81 | + |
| 82 | +The full matrix for building 32-bit/64-bit Windows with Debug/Release |
| 83 | +configuration can be referred as below. |
| 84 | + |
| 85 | +| | 32-bit Build | 64-bit Build |
| 86 | +----------- | -------------------------------------------- | ------------------------------------------ |
| 87 | +| | `cmake -A Win32 -B build\Win32` | `cmake -A x64 -B build\x64` |
| 88 | +**Debug** | `cmake --build build\Win32 --config Debug` | `cmake --build build\x64 --config Debug` |
| 89 | +**Release** | `cmake --build build\Win32 --config Release` | `cmake --build build\x64 --config Release` |
| 90 | + |
| 91 | +The path in the first step is the CMake default extension path installed in |
| 92 | +Visual Studio 2019. If [CMake][cmake] (3.17 or later) has been installed |
| 93 | +independently and added to the system path, the first step of setting path can |
| 94 | +be omitted. |
| 95 | + |
| 96 | +## macOS |
| 97 | + |
| 98 | +### Usage |
| 99 | + |
| 100 | +1. `cd /path/to/CheckTool` |
| 101 | +1. `./checktool --verbose` |
| 102 | + |
| 103 | +### Build |
| 104 | + |
| 105 | +#### Prerequisites |
| 106 | + |
| 107 | +* [Xcode][xcode] 7.2.1 or later |
| 108 | +* [CMake][cmake] 3.17 or later |
| 109 | + |
| 110 | +#### Build steps |
| 111 | + |
| 112 | +1. `cd /path/to/CheckTool` |
| 113 | +1. `mkdir build && cd build && cmake .. && make` |
| 114 | + |
| 115 | +The binary (_checktool_) will be generated in _/path/to/CheckTool/build/_. It is |
| 116 | +easy to clean the build just by removing the _build_ folder manually. |
| 117 | + |
| 118 | +The full list for building Debug/Release configuration can be referred as |
| 119 | +below. |
| 120 | + |
| 121 | +| Debug |
| 122 | +| :-------------------------------------------------- |
| 123 | +| `cmake -DCMAKE_BUILD_TYPE=Debug -B build/Debug` |
| 124 | +| `make -C build/Debug` |
| 125 | +| **Release** |
| 126 | +| `cmake -DCMAKE_BUILD_TYPE=Release -B build/Release` |
| 127 | +| `make -C build/Release` |
| 128 | + |
| 129 | +[checktool-release]: https://github.com/intel/haxm/releases/tag/checktool-v1.0.0 |
| 130 | +[cmake]: https://cmake.org/download/ |
| 131 | +[install-on-macos]: |
| 132 | +https://github.com/intel/haxm/wiki/Installation-Instructions-on-macOS |
| 133 | +[install-on-windows]: |
| 134 | +https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows |
| 135 | +[visualstudio]: https://www.visualstudio.com/downloads/ |
| 136 | +[xcode]: https://developer.apple.com/xcode/ |
0 commit comments