I have a laptop that I mainly use for android development on android studio, today all of the sudden got this error message (or an outdated version of it) when i ran my emulator
我有一台笔记本电脑，主要用于android studio上的android开发，今天当我运行模拟器时，突然收到了这个错误消息(或它的一个过时版本)
Your GPU driver information:
GPU #1
Make: 8086
Model: Intel(R) HD Graphics Family
Device ID: 0a16
Driver version: 10.18.10.3945
GPU #2
Make: 10de
Model: NVIDIA GeForce 820M
Device ID: 1140
Driver version: 22.21.13.8476
Some users have experienced emulator stability issues with this driver version. As a result, were selecting a compatibility renderer. Please check with your manufacturer to see if there is an updated driver available.
Updated the geforce driver, but no use, tried to update the intel one but failed, is there a way to disable this? bypass the compatibility renderer and work as I used to, the emulator is awful now. Any explanation why that occurred all of the sudden?
更新了geforce驱动程序，但是没有使用，试图更新intel one但是失败了，有没有办法禁用它?绕过兼容性渲染器和我以前的工作，模拟器现在很糟糕。为什么会突然发生?
Also I'm using windows 7 64-bit if that will help with anything, had an update few days ago.
另外，我还在使用windows 7 64位系统，如果这对我有帮助的话，几天前我已经更新过了。
9 个解决方案
#1
39
I am using Win10 but have the same problem. Emulator started crashing my app after last emulator update. In my case, problem is that emulator does not run on hardware even though I never had a problem with my GPUs. Also, the "GPU driver issue" window that pops up doesn't even label WHICH one of the GPUs it thinks is the problem.
我正在使用Win10，但是有同样的问题。在上一个模拟器更新之后，模拟器开始破坏我的应用程序。在我的例子中，问题是模拟器不会在硬件上运行，即使我从来没有遇到过我的gpu问题。此外，弹出的“GPU驱动程序问题”窗口甚至没有标记它认为是问题的哪个GPU。
For me the solution that worked is to run emulator from terminal, forcing it to run using hardware graphics (instead of letting emulator decide on which) using command
对我来说，有效的解决方案是从终端运行仿真器，迫使它使用硬件图形(而不是让仿真器决定使用哪个命令)运行
emulator -avd avd_name -gpu mode
where mode is host so that it will run with hardware.
其中的模式是主机，以便与硬件一起运行。
For example:
例如:
Using Android Studio terminal move to folder where the emulator is located. Default on Win10 is: C:\Users\userName\AppData\Local\Android\sdk\emulator
使用Android Studio终端移动到模拟器所在的文件夹。违约Win10是:C:\Users\userName\AppData\Local\Android\sdk\emulator
Find emulator to run by listing available ones: emulator -list-avds
通过列出可用的模拟器来找到要运行的模拟器:模拟器-列表-avds
Run emulator with -gpu host option: emulator -avd avd_name -gpu host
使用-gpu主机选项运行仿真器:仿真器-avd avd_name -gpu主机
More info on this link
更多关于这个链接的信息
#2
18
A comment in the on the bug report pertaining to this issue by a Google employee is illuminating.
谷歌员工关于这个问题的bug报告的评论很有启发性。
If your system doesn't have a discrete GPU, we intended this change in order to make the emulator more reliably run on Intel GPU drivers. At your own risk, you may switch back to using the Intel GPU by going to settings page, then changing the OpenGL ES renderer to "ANGLE (D3D11)", "ANGLE (D3D9)", or "Desktop native OpenGL".
如果您的系统没有一个离散的GPU，我们打算进行这种更改，以便使模拟器在Intel GPU驱动上运行更可靠。您可以通过进入settings页面，然后将OpenGL ES渲染器更改为“ANGLE (D3D11)”来切换回使用Intel GPU。,“角(d3d 9)”，或“桌面本机OpenGL”。
It appears that this message is being displayed for all systems using Intel GPUs, not just systems running specific versions of a graphics driver.
这条消息显示给所有使用Intel gpu的系统，而不仅仅是运行特定版本的图形驱动程序的系统。
The solution is to, if possible, switch to using an external GPU for running the emulator.
解决方案是，如果可能的话，切换到使用外部GPU来运行模拟器。
If an Intel GPU is the only GPU available on system it is possible to re-enable accelerated rendering of OpenGL ES, by overriding the default OpenGL ES renderer in settings (see below). Options are OpenGL, ANGLE and SwiftShader. SwiftShader is CPU based OpenGL ES emulation, so this setting will not provide a speedup. ANGLE is Direct3d based OpenGL emulation.
如果一个Intel GPU是系统上唯一可用的GPU，那么可以通过在设置中覆盖默认的OpenGL ES渲染器来重新启用OpenGL ES的加速渲染(见下面)。选项是OpenGL，角度和SwiftShader。SwiftShader是基于CPU的OpenGL ES模拟，所以这个设置不会提供加速。角是基于Direct3d的OpenGL仿真。
As per the comment this is not guaranteed to work, indeed I am able to re-enable hardware acceleration for Android 7 emulators, but with hardware acceleration enabled, all I receive is a black screen for Android 8 emulators.
根据评论，这并不能保证工作，我确实能够为Android 7模拟器重新启用硬件加速，但是在启用硬件加速的情况下，我所收到的全部是Android 8仿真器的黑色屏幕。
Open settings with Ctrl-Shift-S then Settings -> General -> OpenGL ES renderer 
打开设置，按Ctrl-Shift-S然后设置->通用-> OpenGL ES渲染器
Update #1: Another comment on the bug report provides further illumination on this issue:
更新#1:关于bug报告的另一个评论提供了关于这个问题的进一步说明:
If you have just a Intel HD 4xxx running the emulator, it's intended that a compatibility renderer be used. I'm sorry about it, but we need to be able to switch to better-supported Intel GPU drivers especially when running high API levels (25+) of system images. Intel iGPUs of that generation (and older) have many issues with OpenGL compatibility.
如果您只有一个运行模拟器的Intel HD 4xxx，那么应该使用兼容渲染器。我很抱歉，但是我们需要能够切换到支持更好的Intel GPU驱动程序，特别是在运行高API级别(25+)的系统映像时。这一代(以及更老的一代)的Intel iGPUs在OpenGL兼容性上有很多问题。
It appears that Intel iGPU drivers for Haswell (4th gen) processor and older don't support OpenGL well enough for Android 7.1+ devices. So they are purposely falling back to using software emulation which better supports the new Android emulators.
看来，Haswell(第四代)处理器和更老的英特尔iGPU驱动程序对Android 7.1+设备的OpenGL支持不够好。因此，他们有意回归到使用软件仿真来更好地支持新的Android模拟器。
This matches my experience. Using the Intel iGPU works great on Android 7, but is flaky on Android 7.1 and doesn't work at all on Android 8.
这个比赛我的经验。使用英特尔的iGPU在Android 7上运行良好，但在Android 7.1上却不稳定，在Android 8上根本不工作。
My suggestion, stick with Android 7 emulators when using hardware acceleration for Intel Haswell and older iGPUs.
我的建议是，在为Intel Haswell和旧的igpu使用硬件加速时使用Android 7模拟器。
Update #2: Official communication on this issue was finally provided in the form of comments in the release notes for Emulator 26.1.3:
更新#2:关于这个问题的官方沟通最终以模拟器26.1.3的发布说明中的评论形式提供:
Which GPUs will be switched to use ANGLE or Swiftshader rendering is determined as follows:
将哪个gpu切换到使用角度或Swiftshader渲染如下:
- Older Intel iGPUs have driver issues on both OpenGL and ANGLE D3D drivers. Users with Intel HD Graphics 3xxx and older will use Swiftshader.
- 较老的英特尔iGPUs在OpenGL和角度D3D驱动上都有驱动问题。使用英特尔HD图形3xxx及以上的用户将使用Swiftshader。
- Some users reported the inability to use API level 25 images because of a bug in which "Pixel Launcher keeps stopping." This seems to be a driver issue in some Intel HD 4xxx models. So they will be switched to use ANGLE automatically.
- 一些用户报告说，由于一个“像素启动器”不断停止的错误，无法使用API级别25的图像。这似乎是一些英特尔HD 4xxx机型的驱动问题。所以它们会自动转换成角度。
For best results with GPU emulation, we recommend either to use a discrete NVIDIA or AMD GPU, or a newer Intel GPU (Iris, HD 5xxx, HD 5xx/6xx).
为了获得GPU仿真的最佳结果，我们建议使用离散的NVIDIA或AMD GPU，或者更新的Intel GPU (Iris, HD 5xxx, HD 5xx/6xx)。
#3
5
I ran into this problem today. Per the suggestion from the Google emulator issue tracker, I installed the beta emulator 26.1.3. Problem fixed.
我今天遇到了这个问题。根据谷歌仿真器问题跟踪器的建议，我安装了测试版模拟器26.1.3。固定的问题。
#4
2
I did the same thing as @Api, but I did it from the Virtual Device Manager. In the device edit window, in the Graphics dropdown list, I selected "Hardware - GLES 2.0". I believe the default is Automatic. I still get the erroneous GPU Driver popup window, but the emulator does not crash anymore. It is back to normal reliability.
我做了与@Api相同的事情，但是我是在虚拟设备管理器中做的。在设备编辑窗口，在图形下拉列表中，我选择了“硬件- GLES 2.0”。我认为违约是自动的。我仍然得到错误的GPU驱动弹出窗口，但模拟器不再崩溃。它恢复了正常的可靠性。
#5
2
As other suggested, go to Settings -> Appearance & Behaviour -> System settings -> Updates. Change "Automatically check updates for" to "Beta channel". Update emulator to latest beta. Driver issue should be gone. I had problems running fragment with google maps (app chrash) that was solved after update of emulator to latest beta.
如其他建议，去设置->外观和行为->系统设置->更新。将“自动检查更新”更改为“Beta频道”。更新模拟器到最新的测试版。司机问题应该解决了。我在运行谷歌映射(app chrash)时遇到了一些问题，这些问题是在模拟器更新到最新beta之后解决的。
#6
1
For linux users, go to Android Folder which in my case is under ~/Android. Then proceed to /sdk/emulator. "emulator" is a local command. So, you can run the command as local "./emulator".
对于linux用户，请访问Android文件夹，在我的例子中是在~/Android下。然后继续/ sdk /模拟器。“仿真器”是一个本地命令。因此，可以将该命令作为“./仿真器”运行。
The rest is done as the user "Api" stated.
其余部分按照用户“Api”的说明进行。
$ ./emulator -avd -avd_name -gpu mode
$ ./仿真器-avd -avd_name -gpu模式
$ ./emulator -avd Nexus_5X_API_26 -gpu host (#IN MY CASE)
$ ./仿真器-avd Nexus_5X_API_26 -gpu主机(在我的例子中)
Note: I didn't download SDK, instead copy and pasted it under /home dir. That's why the command was not valid on a global scale. If you setup sdk avd from ground-up, it should work just fine.
注意:我没有下载SDK，而是在/home dir下复制粘贴。这就是为什么该命令在全球范围内无效。如果您从头开始安装sdk，那么它应该可以正常工作。
#7
0
I'm having the exact same issue from precisely 4 days ago. I've tried both above answers but none of it work. PS. The emulator works, but just crashes seemingly at random. I prior to this error, the emulator worked fine and i could test certain features, i can also debug completely with no crashes via USB with a few android devices so im almost certain its a problem with the emulator.
4天前我也有同样的问题。我试过以上两个答案，但都没有成功。仿真器可以工作，但只是随机崩溃。在此错误发生之前，仿真器工作得很好，我可以测试某些特性，我也可以通过USB完全调试而不崩溃，使用一些android设备，所以我几乎可以确定这是仿真器的问题。
Edit: Not sure what eactly the problem was, but was solved by forcing Android Studio to run with nVidia GPU.
编辑:不知道是什么问题，但是通过强制Android Studio使用nVidia GPU解决了这个问题。
#8
0
I managed to workaround this problem by disabling the use of the GPU so that the AVD uses Software acceleration. It won't be as fast as GPU though, but at least it has better chances to work properly.
我通过禁用GPU的使用来解决这个问题，以便AVD使用软件加速。它不会像GPU那样快，但至少它有更好的机会正常工作。
I tried other options above but sadly none of them was working.
我尝试了上面提到的其他选项，但遗憾的是没有一个有效。
If you want to try this option, go to the AVD Manager (in Android Studio : Tools -> Android -> AVD Manager), then edit your virtual Device and in the Graphics field, you can set "Software - GLES 1.1" instead if "Hardware - GLES 2.0".
如果您想尝试此选项，请访问AVD管理器(在Android Studio: Tools -> Android -> AVD Manager)，然后编辑您的虚拟设备，在图形领域，您可以设置“Software - GLES 1.1”，而不是“Hardware - GLES 2.0”。
This is not the perfect fix for this problem but it can help.
这并不是这个问题的完美解决方案，但它可以有所帮助。
#9
0
none of that worked for me on my windows laptop with intel hd4000
在我使用英特尔hd4000的windows笔记本电脑上，没有一款适合我
what worked is ubuntu linux after i run emulator on linux i was shocked of its speed :)
当我在linux上运行模拟器后，我对它的速度感到震惊:)
so it seems the problem with intel and windows won't be resolved soon
因此，英特尔和windows的问题似乎不会很快得到解决
#1
39
I am using Win10 but have the same problem. Emulator started crashing my app after last emulator update. In my case, problem is that emulator does not run on hardware even though I never had a problem with my GPUs. Also, the "GPU driver issue" window that pops up doesn't even label WHICH one of the GPUs it thinks is the problem.
我正在使用Win10，但是有同样的问题。在上一个模拟器更新之后，模拟器开始破坏我的应用程序。在我的例子中，问题是模拟器不会在硬件上运行，即使我从来没有遇到过我的gpu问题。此外，弹出的“GPU驱动程序问题”窗口甚至没有标记它认为是问题的哪个GPU。
For me the solution that worked is to run emulator from terminal, forcing it to run using hardware graphics (instead of letting emulator decide on which) using command
对我来说，有效的解决方案是从终端运行仿真器，迫使它使用硬件图形(而不是让仿真器决定使用哪个命令)运行
emulator -avd avd_name -gpu mode
where mode is host so that it will run with hardware.
其中的模式是主机，以便与硬件一起运行。
For example:
例如:
Using Android Studio terminal move to folder where the emulator is located. Default on Win10 is: C:\Users\userName\AppData\Local\Android\sdk\emulator
使用Android Studio终端移动到模拟器所在的文件夹。违约Win10是:C:\Users\userName\AppData\Local\Android\sdk\emulator
Find emulator to run by listing available ones: emulator -list-avds
通过列出可用的模拟器来找到要运行的模拟器:模拟器-列表-avds
Run emulator with -gpu host option: emulator -avd avd_name -gpu host
使用-gpu主机选项运行仿真器:仿真器-avd avd_name -gpu主机
More info on this link
更多关于这个链接的信息
#2
18
A comment in the on the bug report pertaining to this issue by a Google employee is illuminating.
谷歌员工关于这个问题的bug报告的评论很有启发性。
If your system doesn't have a discrete GPU, we intended this change in order to make the emulator more reliably run on Intel GPU drivers. At your own risk, you may switch back to using the Intel GPU by going to settings page, then changing the OpenGL ES renderer to "ANGLE (D3D11)", "ANGLE (D3D9)", or "Desktop native OpenGL".
如果您的系统没有一个离散的GPU，我们打算进行这种更改，以便使模拟器在Intel GPU驱动上运行更可靠。您可以通过进入settings页面，然后将OpenGL ES渲染器更改为“ANGLE (D3D11)”来切换回使用Intel GPU。,“角(d3d 9)”，或“桌面本机OpenGL”。
It appears that this message is being displayed for all systems using Intel GPUs, not just systems running specific versions of a graphics driver.
这条消息显示给所有使用Intel gpu的系统，而不仅仅是运行特定版本的图形驱动程序的系统。
The solution is to, if possible, switch to using an external GPU for running the emulator.
解决方案是，如果可能的话，切换到使用外部GPU来运行模拟器。
If an Intel GPU is the only GPU available on system it is possible to re-enable accelerated rendering of OpenGL ES, by overriding the default OpenGL ES renderer in settings (see below). Options are OpenGL, ANGLE and SwiftShader. SwiftShader is CPU based OpenGL ES emulation, so this setting will not provide a speedup. ANGLE is Direct3d based OpenGL emulation.
如果一个Intel GPU是系统上唯一可用的GPU，那么可以通过在设置中覆盖默认的OpenGL ES渲染器来重新启用OpenGL ES的加速渲染(见下面)。选项是OpenGL，角度和SwiftShader。SwiftShader是基于CPU的OpenGL ES模拟，所以这个设置不会提供加速。角是基于Direct3d的OpenGL仿真。
As per the comment this is not guaranteed to work, indeed I am able to re-enable hardware acceleration for Android 7 emulators, but with hardware acceleration enabled, all I receive is a black screen for Android 8 emulators.
根据评论，这并不能保证工作，我确实能够为Android 7模拟器重新启用硬件加速，但是在启用硬件加速的情况下，我所收到的全部是Android 8仿真器的黑色屏幕。
Open settings with Ctrl-Shift-S then Settings -> General -> OpenGL ES renderer
打开设置，按Ctrl-Shift-S然后设置->通用-> OpenGL ES渲染器
Update #1: Another comment on the bug report provides further illumination on this issue:
更新#1:关于bug报告的另一个评论提供了关于这个问题的进一步说明:
If you have just a Intel HD 4xxx running the emulator, it's intended that a compatibility renderer be used. I'm sorry about it, but we need to be able to switch to better-supported Intel GPU drivers especially when running high API levels (25+) of system images. Intel iGPUs of that generation (and older) have many issues with OpenGL compatibility.
如果您只有一个运行模拟器的Intel HD 4xxx，那么应该使用兼容渲染器。我很抱歉，但是我们需要能够切换到支持更好的Intel GPU驱动程序，特别是在运行高API级别(25+)的系统映像时。这一代(以及更老的一代)的Intel iGPUs在OpenGL兼容性上有很多问题。
It appears that Intel iGPU drivers for Haswell (4th gen) processor and older don't support OpenGL well enough for Android 7.1+ devices. So they are purposely falling back to using software emulation which better supports the new Android emulators.
看来，Haswell(第四代)处理器和更老的英特尔iGPU驱动程序对Android 7.1+设备的OpenGL支持不够好。因此，他们有意回归到使用软件仿真来更好地支持新的Android模拟器。
This matches my experience. Using the Intel iGPU works great on Android 7, but is flaky on Android 7.1 and doesn't work at all on Android 8.
这个比赛我的经验。使用英特尔的iGPU在Android 7上运行良好，但在Android 7.1上却不稳定，在Android 8上根本不工作。
My suggestion, stick with Android 7 emulators when using hardware acceleration for Intel Haswell and older iGPUs.
我的建议是，在为Intel Haswell和旧的igpu使用硬件加速时使用Android 7模拟器。
Update #2: Official communication on this issue was finally provided in the form of comments in the release notes for Emulator 26.1.3:
更新#2:关于这个问题的官方沟通最终以模拟器26.1.3的发布说明中的评论形式提供:
Which GPUs will be switched to use ANGLE or Swiftshader rendering is determined as follows:
将哪个gpu切换到使用角度或Swiftshader渲染如下:
- Older Intel iGPUs have driver issues on both OpenGL and ANGLE D3D drivers. Users with Intel HD Graphics 3xxx and older will use Swiftshader.
- 较老的英特尔iGPUs在OpenGL和角度D3D驱动上都有驱动问题。使用英特尔HD图形3xxx及以上的用户将使用Swiftshader。
- Some users reported the inability to use API level 25 images because of a bug in which "Pixel Launcher keeps stopping." This seems to be a driver issue in some Intel HD 4xxx models. So they will be switched to use ANGLE automatically.
- 一些用户报告说，由于一个“像素启动器”不断停止的错误，无法使用API级别25的图像。这似乎是一些英特尔HD 4xxx机型的驱动问题。所以它们会自动转换成角度。
For best results with GPU emulation, we recommend either to use a discrete NVIDIA or AMD GPU, or a newer Intel GPU (Iris, HD 5xxx, HD 5xx/6xx).
为了获得GPU仿真的最佳结果，我们建议使用离散的NVIDIA或AMD GPU，或者更新的Intel GPU (Iris, HD 5xxx, HD 5xx/6xx)。
#3
5
I ran into this problem today. Per the suggestion from the Google emulator issue tracker, I installed the beta emulator 26.1.3. Problem fixed.
我今天遇到了这个问题。根据谷歌仿真器问题跟踪器的建议，我安装了测试版模拟器26.1.3。固定的问题。
#4
2
I did the same thing as @Api, but I did it from the Virtual Device Manager. In the device edit window, in the Graphics dropdown list, I selected "Hardware - GLES 2.0". I believe the default is Automatic. I still get the erroneous GPU Driver popup window, but the emulator does not crash anymore. It is back to normal reliability.
我做了与@Api相同的事情，但是我是在虚拟设备管理器中做的。在设备编辑窗口，在图形下拉列表中，我选择了“硬件- GLES 2.0”。我认为违约是自动的。我仍然得到错误的GPU驱动弹出窗口，但模拟器不再崩溃。它恢复了正常的可靠性。
#5
2
As other suggested, go to Settings -> Appearance & Behaviour -> System settings -> Updates. Change "Automatically check updates for" to "Beta channel". Update emulator to latest beta. Driver issue should be gone. I had problems running fragment with google maps (app chrash) that was solved after update of emulator to latest beta.
如其他建议，去设置->外观和行为->系统设置->更新。将“自动检查更新”更改为“Beta频道”。更新模拟器到最新的测试版。司机问题应该解决了。我在运行谷歌映射(app chrash)时遇到了一些问题，这些问题是在模拟器更新到最新beta之后解决的。
#6
1
For linux users, go to Android Folder which in my case is under ~/Android. Then proceed to /sdk/emulator. "emulator" is a local command. So, you can run the command as local "./emulator".
对于linux用户，请访问Android文件夹，在我的例子中是在~/Android下。然后继续/ sdk /模拟器。“仿真器”是一个本地命令。因此，可以将该命令作为“./仿真器”运行。
The rest is done as the user "Api" stated.
其余部分按照用户“Api”的说明进行。
$ ./emulator -avd -avd_name -gpu mode
$ ./仿真器-avd -avd_name -gpu模式
$ ./emulator -avd Nexus_5X_API_26 -gpu host (#IN MY CASE)
$ ./仿真器-avd Nexus_5X_API_26 -gpu主机(在我的例子中)
Note: I didn't download SDK, instead copy and pasted it under /home dir. That's why the command was not valid on a global scale. If you setup sdk avd from ground-up, it should work just fine.
注意:我没有下载SDK，而是在/home dir下复制粘贴。这就是为什么该命令在全球范围内无效。如果您从头开始安装sdk，那么它应该可以正常工作。
#7
0
I'm having the exact same issue from precisely 4 days ago. I've tried both above answers but none of it work. PS. The emulator works, but just crashes seemingly at random. I prior to this error, the emulator worked fine and i could test certain features, i can also debug completely with no crashes via USB with a few android devices so im almost certain its a problem with the emulator.
4天前我也有同样的问题。我试过以上两个答案，但都没有成功。仿真器可以工作，但只是随机崩溃。在此错误发生之前，仿真器工作得很好，我可以测试某些特性，我也可以通过USB完全调试而不崩溃，使用一些android设备，所以我几乎可以确定这是仿真器的问题。
Edit: Not sure what eactly the problem was, but was solved by forcing Android Studio to run with nVidia GPU.
编辑:不知道是什么问题，但是通过强制Android Studio使用nVidia GPU解决了这个问题。
#8
0
I managed to workaround this problem by disabling the use of the GPU so that the AVD uses Software acceleration. It won't be as fast as GPU though, but at least it has better chances to work properly.
我通过禁用GPU的使用来解决这个问题，以便AVD使用软件加速。它不会像GPU那样快，但至少它有更好的机会正常工作。
I tried other options above but sadly none of them was working.
我尝试了上面提到的其他选项，但遗憾的是没有一个有效。
If you want to try this option, go to the AVD Manager (in Android Studio : Tools -> Android -> AVD Manager), then edit your virtual Device and in the Graphics field, you can set "Software - GLES 1.1" instead if "Hardware - GLES 2.0".
如果您想尝试此选项，请访问AVD管理器(在Android Studio: Tools -> Android -> AVD Manager)，然后编辑您的虚拟设备，在图形领域，您可以设置“Software - GLES 1.1”，而不是“Hardware - GLES 2.0”。
This is not the perfect fix for this problem but it can help.
这并不是这个问题的完美解决方案，但它可以有所帮助。
#9
0
none of that worked for me on my windows laptop with intel hd4000
在我使用英特尔hd4000的windows笔记本电脑上，没有一款适合我
what worked is ubuntu linux after i run emulator on linux i was shocked of its speed :)
当我在linux上运行模拟器后，我对它的速度感到震惊:)
so it seems the problem with intel and windows won't be resolved soon
因此，英特尔和windows的问题似乎不会很快得到解决