Couldn\'t use x86 emulators, AVD manager shows warning \"/dev/kvm is not found\" and telling me to edit BIOS security setting to enable VT-x.
You just need to "start" the HAXM. You can do this following this steps:
sc query intelhaxm
, click enter and check the STATE.sc start intelhaxm
and click enter to start the HAXM.Alternatively, when you want to stop the HAXM you should type sc stop intelhaxm
.
Hope this helps y'all.
For MacOS users running Android Studio, when you get this error then try these steps to open up your privacy settings.
You can also follow the answer from Divakar on this post here - /dev/kvm not found on mac
Thank you Apple for pushing me with your dumb*** app review rules from iOS to android development
I couldn't install mine because I had HyperV enabled on my machine. Removed it and I was able to install the HAXM from the following link:
https://github.com/intel/haxm
Reinstalling and restarting did not work for me. Instead, I had to start my Mac in Recovery Mode (restart & press ⌘+R until Apple logo appears). Then open terminal from Utilities drop down menu. Type and run:
csrutil enable --without kext
You will get some warnings and instruction to restart for the changes to take effect. Restart and the emulator will run this time.
Reference: https://blog.celogeek.com/201708/672/android-studio-emulator-haxm-on-mac-os-high-serria-10-13/
Just go to terminal and type
sudo chown 777 -R /dev/kvm,
then type
sudo chmod 777 -R /dev/kvm.
And restart android studio
And that's it..
In some case it may happened that for every start of android studio you need to type this commands First and then start android studio.
I had a similar message in the emulators area in Android Studio 2.1.
My emulator for a certain API (think 21) worked initially fine and was fully accelerated, then installed a couple of other images (Nougat x86/64 etc) and suddenly started seeing /dev/kvm not found and NO emulator would boot up.
In My Case, re-installing HAXM sadly did not help, but rebooting my MAC did (go figure).
But, I also noted that if you have installed an emulator image but not the related SDK for the API (which makes sense), then you get a similar pop-up when starting the emulator, which makes you think it may be a HAXM / KVM issue, which its not.
Hope this helps someone.