I have this issue trying to run a virtual android device on my computer which runs Hyper-V because I use docker containers. The host s.o. is Windows 10 Pro. Android Studio installed, and its updates.
When I try to run a virtual device a blue screen shows and system restarts.
I want to start learning Flutter but I'm stuck in this.
Any solution / Work around?
From the Android developer's blog, you'll want to ensure your hardware and software are supported and versions are current.
Blue screen errors can be happened because of a hardware or driver errors. Please take a picture of the error and send it to us. But a general solution is to open device manager (devmgmt.msc) then check if there is a yellow sign on a driver or not. Please check if all of the drivers has been installed properly. After that, You should check if Intel virtualization technology is turned on in BIOS system
I am using Android Studio emulator, but it keeps crashing upon opening. I get failed to sync vcpu reg error multiple times in the output and nothing else.
I have tried the solutions to similar questions posted on here to no avail. I tried: reinstalling HAXM, I don't have the docker application, I used BIOS to check that VT-x and VT-d are both enabled. I don't get any logcat from Android Studio.
Attached is picture of the output from running the emulator from cmd
This question is different from apparent duplicates because my emulator worked the day before. I don't have any virtual machines running. The only difference is that my laptop auto updated last night.
I solved this problem on my HP laptop by uninstalling HP SureClick.
I am using Windows 10 and tried almost everything the internet had to offer to fix this issue (the Virtual Machine in Android Studio loaded but then closed almost immediately)
The fix I found was to enable "Virtual Machine Platform" on Windows features.
Instructions:
Right click on the Windows button and select 'Apps and Features'
Select Programs and Features on the right under related settings
Select the checkbox below
CHECKBOX TO CLICK
You then get prompted to restart - after that, everything worked for me ! ...hope it does for you !
I had this same problem and all the solutions here did not appear to fix it. Strangely enough I managed to fix it by turning windows virtual machine platform ON, even though it very specifically says here that this is something that should be turned OFF.
I tried what paulsm4 said and the emulator works now. I was looking around in my anti virus settings and found something that uses virtualization. I just turned it on rebooted and then back off and rebooted. The emulator runs!
Guys I've installed genymotion on virtual box provided with setup . now every time i want to start the virtual device I've to restart my laptop & sometimes even that doesn't help . So I've decided to install that on VMWare 11 . Can anyone help me please on this issue.
If anyone can solve this error which says can't connect to virtualbox ,That would be helpful also. But I still prefer solution with VMWare .
I've tried solution like DHCP server address solution which is suggested by official support site of genymotion , but that doesn't help also.
I've tried glew solution also but their support center doesn't accept log file(text) or image of error.
Snapshot of error :
I had the same issue, Genymotion can't be launched on a virtual machine!
This is quoted from their faq:
Why doesn't Genymotion start from a virtual machine? Genymotion cannot
be run from a virtual machine. Indeed, Genymotion needs a direct
access to the hardware in order to provide OpenGL acceleration.
Running Genymotion from a virtual machine prevents it to directly
access the hardware components. Therefore, Genymotion is incompatible
when installed from VMWare, Parallels, Hyper-V or VirtualPC.
About the problem with virtual box try the following steps:
1. Open Virtual box. Go to preferences.
2. Click on networks option.
3. Click on Host-only networks tab
4. Delete all host adapters.
5. Start Genymotion. It will automatically create a new network adapter with required settings.
The above worked for me.
I'm trying to use the Intel HAX x86 emulator for Windows (8, if that matters). I installed everything and created an AVD for the android version, and everything appears correct, but when I run it, I get this output:
Starting emulator for AVD 'x86_QVGA_Level10'
emulator: device fd:1044
HAX is working and emulator runs in fast virt mode
emulator: Failed to sync vcpu reg
emulator: Failed to sync HAX vcpu context
and the emulator won't run. The significant part of this error (Failed to sync vcpu reg) is not mentioned ANYWHERE online, except in the source code for the HAX itself, but I can't figure out how to make any sense of this.
Can anyone advise about how to get past this error? I really need to get this working, because debugging on device and in the default emulators is painfully slow.
Make sure you don't have any virtual machines running. In my case, I had genymotion running which was causing this error.
I had virtualbox running. Killing the VM allowed allowed the emulator to run.
If you are running Docker you would have to take the virtual machine down
docker-machine stop default
This assumes your docker machine is called default. If you want to check the name use
docker-machine ls
A simpler solution; open virtuabox and stop the vm :-)
I had this problem. For me it was the HAXM version.
When you get a new version of HAMX through the SDK Manager, it tells you that it is installed. It is not. You must go to this folder:
<Android SDK>\extras\intel\Hardware_Accelerated_Execution_Manager\
and run intelhaxm-android.exe manually. In my case, I had 1.0.6 and upgraded to 1.1.
I think that what caused the error in the first place was that some other part of the SDK that I had updated needed 1.1.
As mentioned by other answers, make sure no VirtualBox and docker service is running with following command in mac. (systemctl in Linux)
$ launchctl list | grep 'VirtualBox\|docker'
- 0 com.docker.helper
640 0 com.docker.docker.2032
31736 0 org.virtualbox.app.VirtualBox.948
If so, kill the VBox and docker service.
launchctl stop org.virtualbox.app.VirtualBox.948
launchctl stop com.docker.docker.2032
Do you have HP SureClick running? I had the same problem on the HP laptop until I disabled it.
HP SureClick is a security protection program which runs "unsafe" programs in micro-VMs. It may also be called HP Wolf Security on your machine, which is the new name for it, although under the hood (e.g. folders, dialogs etc) it's still called SureClick. It may have some processes visible in Task Manager with a prefix of "Br", which stands for Bromium.
Similarly to other answers, it cannot be running at the same time as Android Emulator, as it is basically a virtual machine.
Here are some steps to disable it (not all may be required but this worked for me):
Right click on "HP SureClick" or "HP Wolf" in your system tray and select "Disable Threat Containment". It will pop up a dialog asking for the reason (optional), so just click OK
Right click on the icon again and select "Disable Malware Protection"
Click Start, type "services", open the Services window and set all "HP SureClick" services to disabled by right-clicking on each -> Properties -> change startup type to Disabled (for me there were 3 such services)
Restart the computer
After doing this, I was able to use Android Emulator again :)
Stop GENYMOTION (open VirtualBox instance if any instance is running, stop it).
Open AndroidStudio -> Run AVD Manager-> run AndroidStudio virtual device.
Latest Android Emulators are not able to run in parallel with GENYMOTION
"vcpu reg" are "Virtual CPU REGisters" that exist on many processors that have things like multiple cores, hyperthreading, or other features that enable higher layers to believe that there is more than one CPU present when there isn't -- such as today's x86s. No reason to go in to detail -- you can imagine that getting a coherent, single "virtual CPU context" is necessary for the kind of hardware virtualization that HAX offers.
Normally, it's not a problem to run multiple virtual machines of various sorts simultaneously. But if one of them crashes, or misbehaves, or just decides to be a hog, HAX might find that it just can't put together a coherent virtual machine, because it can't sync a virtual CPU context for itself. It'd be like trying to run a real machine with no CPU.
Bottom line is open task manager and kill things that you don't need and that look like they might be holding virtual machine resources. In the worst case, a reboot is almost certain to fix the problem.
Quick steps:
Stop all VirtualBox Virtual Machines (i.e. vagrant halt), quit VirtualBox.
All docker-machines should be stopped, too. Quit Docker.
This happened to me also when I was trying to run both VirtualBox and Android emulator in a MacOS machine. As others have mentioned above currently it is not possible to run both (i.e. VirtualBox and X86 -Intel based emulator) in MacOS and not sure about the other platforms.
If we need to run both we can choose ARM based emulator. (arm based emulators are normally slow)
I was getting the same error. I'm guessing there are various reasons for this error, but in my case it was because of a service named ".NCG". The service is Network Content Guard by Inka Entworks, and seems to be some type of DRM solution. Once uninstalled, the emulator worked fine using HAX.
In my case, it turned out this problem was caused by having a webcam selected as "Front Camera" in the settings for the AVD. Setting it to "Emulated" fixed this problem for me.
I faced this issue because I had my virtual box running with Ubuntu on it. When I shut down my virtual box I did not face this issue.
I got the same error on my windows 8 install.
Things you could try:
lower the amount of memory for the emulated device (and/or close other applications)
disable GPU emulation
remove the pass-through webcam
For me, the error occurs when I try to attach a physical webcam to the emulated android instance.
This kept failing until I changed it to [x] Use Host GPU as shown in pic.
I'm running boot2docker vm, just down it solved the issue.
boot2docker down
Make sure you don't have any virtual machines running. In my case, I had genymotion running which was causing this error. when i kill genymotion's Process and kill all Oracle VM VirtualBox related process then it work
by wangshiming
don't thankyou me
Ya, i had virtual box running and was getting this error, shutting it down fixed the error.
I was on a mac and had this problem. I did not think I was running a VM (I have vbox but it isn't running). I restarted my computer and before starting any other apps I tried the emulator and it works fine.
This is the VirtualBox ticket - https://www.virtualbox.org/ticket/14294
Fixed the problem by changing current version of Java within Windows from Java 8 x64 to Java 7 x86.
Yes, VirtualBox VMs have to be stopped. I also had to stop Docker for Mac. The error message only mentions VirtualBox, which confused me a little until I realized Docker for Mac is running xhyve.
If your CPU supports throttling (like Intel's SpeedStep) try to disable that feature in your BIOS. It's kind of a quickfix but at least it worked.
I think it must be a variety of reasons cause this failure. In my case, since I installed the Google input method software, "Failed to sync vcpu reg" appeared. This was the one and only change before normal working. So, after uninstall the Google Input software, it was recovered.just a little reference, although I can't believe this solution for long time either.
I had the Windows Virtual PC running (on Windows of course). Once I turned off, the emulator went fine.
Hope this helps.
I was trying to launch a Gingerbread 2.3.3 x86 emulator and it would not launch. Changing from x86 to arm made the problem go away.
For me, the only thing that worked using adv on MacOs Yosemite, is setting the processor to ARM (native CPU of the device - standard 4" Nexus).
If you are having any virtual machines running, suspend them and try again.
For me the answer was to set Enable keyboard input to true under the advanced settings of the virtual device.
This was the first option I changed on the device, so it is possible that the act of changed an option fixes the error as well based on the wide array of answers above.
Note: I've confirmed previously that no VM's are running.
Finally, I found the anwer for this question.
I had exactly the same problem and it was completely solved.
Virtual device or webcam is rarely the cause of your problem.
Just install mainboard chipset driver.
I recommend you to use 3DP chipset autoinstaller.
Good luck!