IssueTracker

+ Devki
the cls should also go to stable release.

The log:

INFO    | Android emulator version 31.2.6.0 (build_id ) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO    | added library vulkan-1.dll
INFO    | configAndStartRenderer: setting vsync to 60 hz
ERROR   | Failed to open /qemu.conf, err: 2
HAX is working and emulator runs in fast virt mode.
INFO    | Started GRPC server at 127.0.0.1:8554, security: Local
INFO    | Advertising in: C:\Users\tonys\AppData\Local\Temp\avd\running\pid_16232.ini
INFO    | Critical: UpdateLayeredWindowIndirect failed for ptDst=(566, 218), size=(308x21), dirty=(308x96 0, 0) (A device attached to the system is not functioning.) ((null):0, (null))

INFO    | Critical: UpdateLayeredWindowIndirect failed for ptDst=(566, 218), size=(308x21), dirty=(308x21 0, 0) (A device attached to the system is not functioning.) ((null):0, (null))

INFO    | boot completed
INFO    | Increasing screen off timeout, logcat buffer size to 2M.
INFO    | Revoking microphone permissions for Google App.    
                                                                                             <------------------------ "adb reboot" here
VCPU shutdown request
WARNING | Not saving state: RAM not mapped as shared
VCPU shutdown request
INFO    | Shutting down gRPC endpoint
INFO    | Shutting down gRPC endpoint

Hi, Wenchao,

The CL that triggers this "vcpu shutdown" also disables "-show-kernel" (by accident). So you won't be able to see kernel log in commandline when you reproduce the issue.

Thanks for the quick response. Maybe this only happened on my Intel PC, which has a 7980XE CPU?
Mine has the emulator 31.2.5 and "HAXM version 7.6.5(4) is installed and usable".   Emulator binary showed build ID 8053530. Let me attach the binary package here.

The CL removed super io from the qemu virtual machine configuration. https://android-review.googlesource.com/c/platform/external/qemu/+/1924718
I guess virtual serial might also be removed as well as part of superio chip. If so, that was probably the reason why "-show-kernel" would not show anything.
And the same CL on my Intel PC had this "vcpu shutdown" issue. So I cannot use "show-kernel" to provide more useful information. To be clear. "-show-kernel" option is still there. But the CL mentioned above breaks it.

And I also tried to check out and build emulator. Mine has top of the tree f5acf44a1641338a. I re-apply the above CL (since the CL was reverted by me recently) and am able to reproduce the issue.

Hope the information could be of help to you.

Hi Haitao,
I just reproduced this issue with your attached emulator v31.2.5 on my SKL+Win10&TGL+Win 11.  I also compared it with the latest released emulator v31.1.4, the issue only happened with v31.2.5. Meanwhile, the '-show-kernel' parameter did not work as expected. So I assume this is an emulator v31.2.5 specific issue.

========== Log==============

C:\Users\sdkot\AppData\Local\Android\sdk\sdk-repo-windows-emulator-8053530\emulator>emulator @Pixel_2_API_R -wipe-data -show-kernel
INFO | Android emulator version 31.2.5.0 (build_id 8053530) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO | added library vulkan-1.dll
ERROR | Failed to create Vulkan instance.
INFO | configAndStartRenderer: setting vsync to 60 hz
ERROR | Failed to open /qemu.conf, err: 2
HAX is working and emulator runs in fast virt mode.
INFO | Warning: Unable to open default EUDC font: "EUDC.TTE" ((null):0, (null))

dsound: Could not initialize DirectSoundCapture
dsound: Reason: No sound driver is available for use, or the given GUID is not a valid DirectSound device ID
Attempt to initialize voice without DirectSoundCapture object
Attempt to initialize voice without DirectSoundCapture object
Failed to create voice `goldfish_audio_in'
C:\Users\sdkot\AppData\Local\Android\sdk\sdk-repo-windows-emulator-8053530\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: warning: opening audio input failed
INFO | Started GRPC server at 127.0.0.1:8554, security: Local
INFO | Advertising in: C:\Users\sdkot\AppData\Local\Temp\avd\running\pid_8732.ini
Attempt to initialize voice without DirectSoundCapture object
Attempt to initialize voice without DirectSoundCapture object
Failed to create voice `adc'
WARNING | UpdateCheck: Failure: Couldn't connect to server
WARNING | UpdateCheck: failed to get the latest version, skipping check (current version '31.2.5-8053530')
INFO | boot completed
INFO | Increasing screen off timeout, logcat buffer size to 2M.
INFO | Revoking microphone permissions for Google App.
VCPU shutdown request
VCPU shutdown request
INFO | Shutting down gRPC endpoint
INFO | Shutting down gRPC endpoint

Hi, Yongwei,

Thanks for the update. As I said in #7, that CL brought all the problems. 31.2.5 has the problem simply because it has the CL. Any newer releases fix the issue simply because I reverted the CL.
However, you should decide whether a "vcpu shutdown request" is a potential bug. If it is not a bug, that means HAXM assumes the existence of virtual Super IO chip in QEMU. In that case, let me know and I will close the bug. Thanks!

Below are the steps to verify the bug:
1. Launch the AVD from terminal with below command
emulator -avd <AVDName>  -verbose
2. Make sure you see below in logs :
..."HAXM 7.6.5 is  installed usable" or something similar
3. From another terminal, run:
<SDKLocation>/platform-tools/adb reboot

Expected behavior:
There is no avd crash with "vcpu shutdown request" error message in the terminal .

Tried with comment#10 steps emulator is using HAX and not observed any avd crash while booting the emulator .
Emulator Version:31.2.8

Hi Haitao,
Discussed with our developer team, HAXM relies on the QEMU super  I/O initialization. From the HAXM perspective, it is not a block bug. If this issue would not block your side, maybe you can close it here. For sure thing, we will monitor and dig more when we have resource.

Suri

Güncelleme yapamıyorum

20 May 2022 Cum 20:43 tarihinde peripr08 <buganizer-system@google.com> şunu
yazdı:

https://developer.android.com/studio/releases/emulator#31-3-11

Just filing a bug 🐛 and the details of the activity is very disturbing for the reason that I am not going to be able to get much accomplished with the obstruction and redirection of the implications of the activity of the reprogrammed Android.