从命令行启动仿真器,可以查看其输出。

Microsoft Windows [版本 10.0.18362.145]

(c) 2019 Microsoft Corporation。保留所有权利。

C:\Users\geffzhang>msinfo32

C:\Users\geffzhang>sc query intelhaxm

SERVICE_NAME: intelhaxm
         TYPE               : 1  KERNEL_DRIVER
         STATE              : 1  STOPPED
         WIN32_EXIT_CODE    : 31  (0x1f)
         SERVICE_EXIT_CODE  : 0  (0x0)
         CHECKPOINT         : 0x0
         WAIT_HINT          : 0x0

C:\Users\geffzhang>c:\Android\android-sdk\emulator\emulator.exe -list-avds

Android_Accelerated_x86_Oreo

C:\Users\geffzhang>c:\Android\android-sdk\emulator\emulator.exe -partition-size 512 -no-boot-anim -verbose -feature WindowsHyperversorPlatform -avd Android_Accelerated_x86_Oreo -prop monodroid.avdname=Android_Accelerated_x86_Oreo

emulator: Android emulator version 27.2.9.0 (build_id 4773671) (CL:18fc969f023e3b369b34b08db237dd9addfe100a)

emulator: Found AVD name 'Android_Accelerated_x86_Oreo'

emulator: Found AVD target architecture: x86

emulator: argv[0]: 'c:\Android\android-sdk\emulator\emulator.exe'; program directory: 'c:\Android\android-sdk\emulator'

emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: Probing for c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu: file exists

emulator: Auto-config: -engine qemu2 (based on configuration)

emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: emuDirName: 'c:\Android\android-sdk\emulator'

emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: Probing for c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu-64: file missing

emulator: try dir c:\Android\android-sdk\emulator

emulator: Trying emulator path 'c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe'

emulator: Found target-specific 64-bit emulator binary: c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe

emulator: Adding library search path: 'c:\Android\android-sdk\emulator/lib64'

emulator: Adding library search path: 'c:\Android\android-sdk\emulator/lib64/gles_swiftshader'

emulator: Adding library search path: 'c:\Android\android-sdk\emulator/lib64/gles_angle'

emulator: Adding library search path: 'c:\Android\android-sdk\emulator/lib64/gles_angle9'

emulator: Adding library search path: 'c:\Android\android-sdk\emulator/lib64/gles_angle11'

emulator: Adding library search path for Qt: 'c:\Android\android-sdk\emulator\lib64\qt\lib'

emulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=c:\Android\android-sdk\emulator\lib64\qt\plugins

emulator: Setting Qt to use software OpenGL: QT_OPENGL=software

emulator: Quoted param: [c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe]

emulator: Quoted param: [-partition-size]

emulator: Quoted param: [512]

emulator: Quoted param: [-no-boot-anim]

emulator: Quoted param: [-verbose]

emulator: Quoted param: [-feature]

emulator: Quoted param: [WindowsHyperversorPlatform]

emulator: Quoted param: [-avd]

emulator: Quoted param: [Android_Accelerated_x86_Oreo]

emulator: Quoted param: [-prop]

emulator: Quoted param: [monodroid.avdname=Android_Accelerated_x86_Oreo]

emulator: Running :c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe

emulator: qemu backend: argv[00] = "c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe"

emulator: qemu backend: argv[01] = "-partition-size"

emulator: qemu backend: argv[02] = "512"

emulator: qemu backend: argv[03] = "-no-boot-anim"

emulator: qemu backend: argv[04] = "-verbose"

emulator: qemu backend: argv[05] = "-feature"

emulator: qemu backend: argv[06] = "WindowsHyperversorPlatform"

emulator: qemu backend: argv[07] = "-avd"

emulator: qemu backend: argv[08] = "Android_Accelerated_x86_Oreo"

emulator: qemu backend: argv[09] = "-prop"

emulator: qemu backend: argv[10] = "monodroid.avdname=Android_Accelerated_x86_Oreo"

emulator: Concatenated backend parameters:
  c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe -partition-size 512 -no-boot-anim -verbose -feature WindowsHyperversorPlatform -avd Android_Accelerated_x86_Oreo -prop monodroid.avdname=Android_Accelerated_x86_Oreo

emulator: Android virtual device file at: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.ini

emulator: virtual device content at C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd

emulator: virtual device config file: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/config.ini

emulator: using core hw config path: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/hardware-qemu.ini

emulator: using snapshot lock path: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/snapshot.lock

emulator: Found AVD target API level: 27

emulator: Read property file at c:\Android\android-sdk/system-images\android-27\google_apis\x86\/build.prop

emulator: No boot.prop property file found.

emulator: 'magic' skin format detected: 768x1280

emulator: autoconfig: -skin 768x1280

emulator: autoconfig: -skindir (null)

emulator: autoconfig: -kernel c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu

emulator: Target arch = 'x86'

emulator: Auto-config: -qemu -cpu qemu32

emulator: Auto-detect: Kernel image requires new device naming scheme.

emulator: Auto-detect: Kernel does not support YAFFS2 partitions.

emulator: autoconfig: -ramdisk c:\Android\android-sdk/system-images\android-27\google_apis\x86\/ramdisk.img

emulator: Using initial system image: c:\Android\android-sdk/system-images\android-27\google_apis\x86\/system.img

emulator: Using initial vendor image: c:\Android\android-sdk/system-images\android-27\google_apis\x86\/vendor.img

emulator: autoconfig: -data C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata-qemu.img

emulator: autoconfig: -initdata C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata.img

emulator: autoconfig: -cache C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/cache.img

emulator: autoconfig: -sdcard C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/sdcard.img

emulator: Increasing RAM size to 1024MB

emulator: VM heap size 64MB is below hardware specified minimum of 256MB,setting it to that value

emulator: System image is read only

emulator: Found 4 DNS servers: 202.96.134.133 192.168.1.1 fec0:0:0:ffff::1 fec0:0:0:ffff::2

emulator: WARNING: [FeatureControl] Bad feature name: 'WindowsHyperversorPlatform'

emulator: found magic skin width=768 height=1280 bpp=16

emulator: CPU Acceleration: DISABLED

emulator: CPU Acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.

emulator: ERROR: x86 emulation currently requires hardware acceleration!

Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable.

CPU acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.

C:\Users\geffzhang>

上述说明需要如下操作才能使用仿真器:

emulator: CPU Acceleration: DISABLED
emulator: CPU Acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable.
CPU acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.

Android 仿真器 无法启动排查的更多相关文章

  1. Android应用程序启动时发生AndroidRuntime : ClassNotFoundException for Activity class的解决方法

    在android应用程序启动时抛出下面异常导致启动失败:07-09 17:12:35.709: ERROR/AndroidRuntime(3866): Uncaught handler: thread ...

  2. 【Android端 APP 启动时长获取】启动时长获取方案及具体实施

    一.什么是启动时长? 1.启动时长一般包括三种场景,分别是:新装包的首次启动时长,冷启动时长.热启动时长 冷启动 和 热启动 : (1)冷启动:当启动应用时,后台没有该程序的进程,此时启动的话系统会分 ...

  3. Android Studio 无法启动模拟器的一种可能是你装的是Ghost版的系统

    我遇到的问题是,打开模拟器,进度条走到最后,突然出现了emulator error,然后模拟器就无法启动(不好意思当时没有截图).我是在Ghost版 win7系统下运行Android Studio 的 ...

  4. android Activity的启动模式

    Android中Activity启动模式详解   在Android中每个界面都是一个Activity,切换界面操作其实是多个不同Activity之间的实例化操作.在Android中Activity的启 ...

  5. Android Activity的启动过程

    文章编辑的太长了,请移步我的csdn博客:http://blog.csdn.net/xyh269 Android Activity的启动过程原文链接:http://blog.csdn.net/xyh2 ...

  6. Android手机app启动的时候第一个Activity必须是MainActivity吗

    原文:Android手机app启动的时候第一个Activity必须是MainActivity吗 Android手机APP启动的第一个Activity是可以自己设置的,不是必须的MainActivity ...

  7. Android 4.2启动代码分析(一)

    Android系统启动过程分析 Android系统的框架架构图如下(来自网上):   Linux内核启动之后----->就到Android的Init进程 ----->进而启动Android ...

  8. Cocos2d-x3.3RC0的Android编译Activity启动流程分析

    本文将从引擎源代码Jni分析Cocos2d-x3.3RC0的Android Activity的启动流程,以下是具体分析. 1.引擎源代码Jni.部分Java层和C++层代码分析 watermark/2 ...

  9. Android开机动画启动流程

    android开机动画启动流程   从android的Surface Flinger服务启动分析知道,开机动画是在SurfaceFlinger实例通过调用startBootAnim()启动的. 下面我 ...

随机推荐

  1. 程序员的算法课(17)-常用的图算法:深度优先(DFS)

    版权声明:本文为博主原创文章,遵循CC 4.0 BY-SA版权协议,转载请附上原文出处链接和本声明. 本文链接:https://blog.csdn.net/m0_37609579/article/de ...

  2. sudo控制用户对系统命令的使用权限

    sudo控制用户对系统命令的使用权限 sudo相关概念 普通用户涉及到超级权限的运用,管理员如果想让该普通用户通过su来切换到root获得超级权限,就必须把root权限密码告诉用户.但是如果普通用户有 ...

  3. [ch04-05] 梯度下降的三种形式

    系列博客,原文在笔者所维护的github上:https://aka.ms/beginnerAI, 点击star加星不要吝啬,星越多笔者越努力. 4.5 梯度下降的三种形式 我们比较一下目前我们用三种方 ...

  4. 实战!轻松搭建图像分类 AI 服务

    人工智能技术(以下称 AI)是人类优秀的发现和创造之一,它代表着至少几十年的未来.在传统的编程中,工程师将自己的想法和业务变成代码,计算机会根据代码设定的逻辑运行.与之不同的是,AI 使计算机有了「属 ...

  5. 爬虫新宠requests_html 带你甄别2019虚假大学 #华为云·寻找黑马程序员#

    python模块学习建议 学习python模块,给大家个我自己不专业的建议: 养成习惯,遇到一个模块,先去github上看看开发者们关于它的说明,而不是直接百度看别人写了什么东西.也许后者可以让你很快 ...

  6. 使用Spring Data JPA的Specification构建数据库查询

    Spring Data JPA最为优秀的特性就是可以通过自定义方法名称生成查询来轻松创建查询SQL.Spring Data JPA提供了一个Repository编程模型,最简单的方式就是通过扩展Jpa ...

  7. java抽象类,接口(接口定义,实现接口,instanceof运算符,对象转换)

    抽象类 在面向对象的概念中,所有的对象都是通过类来表述的,但并不是所有的类都能够完整的描绘对象,如果一个类中没有包含足够的信息来描绘一类具体的对象,这样的类就是抽象类.抽象类往往用来表征对问题领域进行 ...

  8. KVM http网络加载镜像报错(mount: wrong fs type, bad option, bad superblock on /dev/loop0)

    curl: (23) Failed writing body (7818 != 16384)loop: module loadeddracut-initqueue[579]: mount: wrong ...

  9. Java修炼——FileInputStream和FileOutputStream

    文件字节流FileInputStream是读文件内容 有一下五个方法 1) abstract int read( ); 2) int read( byte b[ ] ); 3) int read( b ...

  10. Atoder-3620

    The season for Snuke Festival has come again this year. First of all, Ringo will perform a ritual to ...