My x86 AVDs never load. I've searched all over for a solution but haven't seen a solution that has worked for me.
Configuration
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.
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
Stuff I've tried:
Any suggestions?
Seems to be an issue with the 7th gen processors on windows. Still trying to figure this one out.
UPDATE: Confirmed to be a HAXM issue on Kaby Lake, nothing we can do until we get an HAXM update from Intel. Either use the ARM image or ad the switch -accel off -verbose to the x86/x64 image....neither are desirable but will do the trick until we get a fix. You can also use an android device but that can be frustrating too.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With