blocks|key|301698|text|确保您没有运行任何虚拟机。在我的例子中，我运行了genymotion，这导致了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301699|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Make sure you don't have any virtual machines running. In my case, I had genymotion running which was causing this error.

blocks|key|84556|text|我运行了virtualbox。终止允许的VM允许模拟器运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84557|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had virtualbox running. Killing the VM allowed allowed the emulator to run.

blocks|key|302211|text|如果您运行的是Docker，则必须关闭虚拟机|type|unstyled|depth|inlineStyleRanges|entityRanges|data|302212|docker-machine+stop+default|offset|length|style|CODE|302213|这里假设您的停靠机器名为default。如果想要检查名称，请使用docker-machine+ls|302214|更简单的解决方案；打开virtuabox并停止虚拟机:-)|302215|entityMap^0|0|0|R|0|C|7|W|H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

If you are running Docker you would have to take the virtual machine down

<code>docker-machine stop default</code>

This assumes your docker machine is called <code>default</code>. If you want to check the name use
<code>docker-machine ls</code>

A simpler solution; open virtuabox and stop the vm :-)

blocks|key|84799|text|正如其他答案所提到的，确保在mac中没有使用以下命令运行VirtualBox和docker服务。(Linux中的systemctl)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|84800|$+launchctl+list+%7C+grep+'VirtualBox\%7Cdocker'
-+++++++0+++com.docker.helper
640+++++0+++com.docker.docker.2032
31736+++0+++org.virtualbox.app.VirtualBox.948|code-block|syntax|javascript|84801|如果是，则终止VBox和docker服务。|84802|launchctl+stop+org.virtualbox.app.VirtualBox.948
launchctl+stop+com.docker.docker.2032|84803|entityMap^0|1K|9|0|0|7|4|C|6|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

As mentioned by other answers, make sure no VirtualBox and docker service is running with following command in mac. (<code>systemctl</code> in Linux)

<pre><code>$ launchctl list | grep 'VirtualBox\|docker'
- 0 com.docker.helper
640 0 com.docker.docker.2032
31736 0 org.virtualbox.app.VirtualBox.948
</code></pre>

If so, kill the <code>VBox</code> and <code>docker</code> service.

<pre><code>launchctl stop org.virtualbox.app.VirtualBox.948
launchctl stop com.docker.docker.2032
</code></pre>

blocks|key|84309|text|"vcpu“是存在于许多处理器上的”虚拟CPU“，这些处理器具有多核、超线程或其他特性，这些特性使高层相信存在多个REGisters，而实际上并不存在--例如今天的x86s。没有理由详述细节--您可以想象，对于HAX提供的那种硬件虚拟化来说，获得一个连贯的、单一的“虚拟CPU上下文”是必要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84310|通常，同时运行多个不同类型的虚拟机是不成问题的。但是，如果它们中的一个崩溃，或者行为不检，或者只是决定成为一只猪，HAX可能会发现它无法构建一个连贯的虚拟机，因为它不能为自己同步虚拟CPU上下文。这就像是试图在没有CPU的情况下运行一台真正的机器。|84311|底线是打开任务管理器，杀死你不需要的东西，看起来它们可能持有虚拟机资源。在最坏的情况下，重新启动几乎肯定能解决问题。|84312|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

"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.

blocks|key|302308|text|当我试图在一台MacOS机器上同时运行VirtualBox和安卓模拟器时，也发生了这种情况。正如其他人在上面提到的，目前不可能在MacOS中同时运行(即基于VirtualBox和X86+-Intel的仿真器)，并且不确定其他平台。如果我们需要同时运行两者，我们可以选择基于ARM的仿真器。(基于arm的仿真器通常很慢)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|302309|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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)

blocks|key|301682|text|我也收到了同样的错误。我猜这个错误有多种原因，但在我的例子中，它是由一个名为".NCG“的服务引起的。该服务是Inka+Entworks的Network+Content+Guard，似乎是某种类型的DRM解决方案。卸载后，模拟器使用HAX即可正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301683|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|301725|text|在我的例子中，这个问题是由于在AVD的设置中选择了一个网络摄像头作为“前置摄像头”造成的。将其设置为"Emulated“为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301726|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|302089|text|我之所以面对这个问题，是因为我在我的虚拟机器上运行了Ubuntu。当我关闭我的虚拟机器时，我没有遇到这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|302090|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|84481|text|这一直失败，直到我将它改为x使用主机GPU，如图所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84482|​|84483|📷|atomic|offset|length|84484|84485|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0d0709b30d2b8b7a0e59c3d0604b695b.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

This kept failing until I changed it to [x] Use Host GPU as shown in pic.

<img src="https://i.stack.imgur.com/K4Aer.png" alt="AVD Set up">

blocks|key|302355|text|我运行的是boot2docker+vm，它解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|302356|boot2docker+down|offset|length|style|CODE|302357|entityMap^0|0|0|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I'm running boot2docker vm, just down it solved the issue.

<code>boot2docker down</code>

blocks|key|84342|text|确保您没有运行任何虚拟机。在我的例子中，我运行了genymotion，这导致了这个错误。当我杀死genymotion的进程并杀死所有与Oracle+VM+VirtualBox相关的进程时，它就能正常工作了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84343|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|84419|text|是的，我已经运行了虚拟机器并且得到了这个错误，关闭它修复了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84420|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Ya, i had virtual box running and was getting this error, shutting it down fixed the error.

blocks|key|84441|text|我在mac上遇到了这个问题。我不认为我在运行VM+(我有vbox，但它没有运行)。我重新启动了我的计算机，在启动任何其他应用程序之前，我尝试了模拟器，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84442|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|84636|text|这是https://www.virtualbox.org/ticket/14294的VirtualBox票证|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|84637|entityMap|0|LINK|mutability|MUTABLE|url|https://www.virtualbox.org/ticket/14294^0|2|13|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This is the VirtualBox ticket - <a href="https://www.virtualbox.org/ticket/14294" rel="nofollow">https://www.virtualbox.org/ticket/14294</a>

blocks|key|84725|text|通过将Windows中当前版本的Java从Java+8+x64更改为Java+7+x86，修复了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84726|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Fixed the problem by changing current version of Java within Windows from Java 8 x64 to Java 7 x86.

blocks|key|84761|text|是的，必须停止VirtualBox+VM。我还不得不停止Docker+for+Mac。错误消息只提到了VirtualBox，这让我有点困惑，直到我意识到Docker+for+Mac正在运行xhyve。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84762|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|84169|text|如果你的中央处理器支持节流(如英特尔的SpeedStep)，试着在你的基本输入输出系统中禁用这个功能。这是一种快速修复，但至少它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|84170|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/SpeedStep^0|J|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If your CPU supports throttling (like Intel's <a href="http://en.wikipedia.org/wiki/SpeedStep" rel="nofollow">SpeedStep</a>) try to disable that feature in your BIOS. It's kind of a quickfix but at least it worked.

blocks|key|301758|text|我认为这一定是多种原因造成的。在我的例子中，由于我安装了谷歌输入法软件，出现了“无法同步vcpu+reg”。在正常工作之前，这是唯一的变化。所以，在卸载谷歌输入软件后，它是recovered.just的一个小参考，尽管我在很长一段时间内也不敢相信这个解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301759|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|302004|text|我试图启动一个姜饼2.3.3+x86模拟器，但它不能启动。将x86更改为arm可以解决此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|302005|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|84606|text|对我来说，在MacOs+Yosemite上使用adv唯一有效的方法是将处理器设置为ARM+(设备标准4“Nexus的原生CPU+)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|84607|entityMap^0|15|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

For me, the only thing that worked using adv on MacOs Yosemite, is setting the processor to <code>ARM</code> (native CPU of the device - standard 4" Nexus).

blocks|key|84658|text|如果您正在运行任何虚拟机，请挂起它们，然后重试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84659|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are having any virtual machines running, suspend them and try again.

blocks|key|302151|text|对我来说，答案是在虚拟设备的高级设置下将Enable+keyboard+input设置为true。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|302152|这是我在设备上更改的第一个选项，因此，根据上面广泛的答案，更改选项的操作也可能修复错误。|302153|注意:我之前已经确认没有VM正在运行。|302154|entityMap^0|K|L|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

For me the answer was to set <code>Enable keyboard input</code> 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.

blocks|key|301852|text|对我来说，它是在本地运行的google+appengine。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301853|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me it was google appengine running locally.

blocks|key|84498|text|对于那些本地环境使用VM+(例如Homestead)的开发人员，只需在启动Android模拟器之前停止VM即可。之后重新启动它将允许两者并行运行，但您可能会遇到严重的性能问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|84499|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those developers whose local environment leverages a VM (e.g. Homestead), simply halt the VM before launching the Android emulator. Restarting it after will allow both to run in parallel, but you're likely going to run into severe performance issues.

blocks|key|301884|text|我减少了分配的VM内存的大小，它似乎已经修复了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|301885|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I reduced the size of the VM memory allocated and it seems to have fixed it.

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:

<pre><code>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
</code></pre>

and the emulator won't run. The significant part of this error <code>(Failed to sync vcpu reg)</code> is not mentioned ANYWHERE online, except in the <a href="http://mirror.yongbok.net/pub/linux/android/repository/external/qemu/target-i386/hax-all.c">source code for the HAX itself</a>, 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.

How do I fix "Failed to sync vcpu reg" error?

虚拟化

虚拟机

Android

Windows

Docker

Ubuntu

Linux

MacOS

Java

我正在尝试使用用于Windows的Intel HAX x86仿真器(8，如果有关系的话)。我安装了所有东西，并为android版本创建了AVD，一切看起来都是正确的，但当我运行它时，我得到了以下输出：Starting emulator for AVD 'x86_QVGA_Level10'emulator: device fd:1044HAX is working and emulator runs

问如何修复“同步vcpu reg失败”错误？
EN

回答 26

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复“同步vcpu reg失败”错误？EN

回答 26

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复“同步vcpu reg失败”错误？
EN