Windows 10上的Android虚拟设备-无休止的"VCPU关闭请求" -不启动 [英] Android Virtual Device on Windows 10 - Endless "VCPU shutdown request" - doesn't launch

查看:499
本文介绍了Windows 10上的Android虚拟设备-无休止的"VCPU关闭请求" -不启动的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的x86 AVD从未加载.我一直在寻找解决方案,但没有找到适合我的解决方案.

My x86 AVDs never load. I've searched all over for a solution but haven't seen a solution that has worked for me.

配置

  • 操作系统:Windows 10 Home
  • RAM:12 GB
  • CPU:英特尔酷睿i5-7200
  • CPU支持HAXM要求的VT-x,EM64T和XD位(根据Intel规范)
  • HAXM版本:6.0.4
  • Android Studio版本:2.2
  • Bios:Insyde F.21
  • BIOS配置:启用了虚拟化技术.

步骤
1.在Android Studio中,启动Android虚拟设备管理器.
2.使用所有默认设置创建Nexus 5 API 24 AVD.
3.启动AVD.

Steps
1. In Android Studio, launch Android Virtual Device Manager.
2. Create Nexus 5 API 24 AVD with all default settings.
3. Launch the AVD.

结果:
显示AVD窗口.
没有出现"Android"文本.
Android运行屏幕最初显示看起来不错的日志条目,但随后显示"VCPU关闭请求"的许多实例.
如果我离开,它会无限期地持续几个小时.
虚拟设备永远保持黑色".

Results:
AVD window displays.
No "Android" text appears.
Android Run screen initially displays log entries that look positive, but then shows many instances of "VCPU shutdown request".
This goes on indefinitely, for hours if I leave it.
Virtual device stays "black" forever.

开始一些日志条目:

Starting few log entries:

C:\Users\username\AppData\Local\Android\Sdk\tools\emulator.exe -netdelay none -netspeed full -avd Nexus_5_API_24
Creating filesystem with parameters:
    Size: 69206016
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 4224
    Inode size: 256
    Journal blocks: 1024
    Label: 
    Blocks: 16896
    Block groups: 1
    Reserved block group size: 7
Created filesystem with 11/4224 inodes and 1302/16896 blocks
Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
VCPU shutdown request
EAX=00748cea EBX=5ffadb60 ECX=00000000 EDX=00000000
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00006d38
EIP=5ffb6921 EFL=00010082 [--S----] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
VCPU shutdown request
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
VCPU shutdown request
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
VCPU shutdown request
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
VCPU shutdown request
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy

我尝试过的东西:

  1. 听说安装了防病毒软件可能会阻止HAXM安装工作:暂时禁用AV,重新安装HAXM,并尝试在禁用AV的情况下运行AVD-无效.
  2. 使用基于ARM的AVD可以工作,但是我已经读到x86 AVD的运行速度要快得多,所以我试图让x86正常工作.
  3. 尝试x86和x86_64 AVD无效.
  4. 尝试将2GB RAM的默认HAXM设置更改为4GB和1GB.结果相同.
  5. 使用具有较低API级别(例如21)的AVD进行了尝试.
  6. Windows事件查看器未显示任何错误.

有什么建议吗?

Any suggestions?

推荐答案

这确实是当前HAXM版本中的错误.

It is indeed a bug in current versions of HAXM.

新的HAXM 6.0.5修复了此问题: https://code.google.com/p/android/issues/detail?id = 226174#c51

The new HAXM 6.0.5 fixes this: https://code.google.com/p/android/issues/detail?id=226174#c51

这篇关于Windows 10上的Android虚拟设备-无休止的"VCPU关闭请求" -不启动的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆