Hello Christian, I should have pointed that the log is from the Android system, not Qemu or my host system !
I got the failure message running the following command in an Android shell : logcat '*:F' (which means display log entries from all facilities (*), with the Fatal (F) severity) It seems indeed that Fosshub has a hosting problem with the Android-x86 images, I'll have to report this to the project maintainer. You seem to experience the same crash as I do. Bootloader OK, the GUI is responsive at the beginning, and it crashes after a variable amount of time. You're right, the bug #1898490 looks like it could be related, I don't see the virgl=on option, but I suppose it's on by default. I normally have those messages on my Qemu instance : gl_version 45 - core profile enabled GLSL feature level 430 virtio_input_hid_handle_status: unknown type 20 virtio_input_hid_handle_status: unknown type 20 The virtio_input_hid messages don't seem to be a problem, and certainly unrelated to the Android 9.0 crashing problem since at the time I tried with other, non-virtio input devices, I didn't have that message but it was still crashing the same way. It happens that I have that "stale GL error" from time to time, that almost always corresponds to an app not displaying properly in Android. Generally, quitting and restarting the app solves the problem, but not always, there are cases and Android apps that never worked correctly with virglrenderer, such as Armello. So, virglrenderer seems less stable with Android (or is it virtio-vga ?). In particular, switching from the surfaceflinger OpenGL display to a VGA, non-OpenGL console display (Alt+F1) never worked correctly (Alt+F7 to go back to the surfaceflinger display). However, as I said before, it seems to me it shouldn't behave differently depending on which display, GTK or SDL, is used. Concerning other frontends, I'm not familiar with those since my setup isn't headless : I'm not a server guy, I run the emulator on my laptop, so apart from GTK and SDL, it's not clear to me if I could run something else that would give me 3D acceleration. Moreover, my hardware is more than 6 years old now, and lacks some virtualisation capabilities that could serve as an alternative to virglrenderer. Anyway virglrenderer is still pre 1.0 so I guess it's the prime suspect after all. I will upgrade to Groovy next month, I'll keep you informed on that (I may even try Qemu 5.0 before upgrading). -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1898490 Title: gtk with virtio and opengl black screen Status in QEMU: New Bug description: qemu-system-x86_64 -name manjaro -enable-kvm -cpu host -smp cores=4,threads=1 -M q35 -m 8G -cdrom /mnt/Storage/ISO/manjaro- gnome-20.0.3-minimal-200606-linux56.iso -machine type=pc,accel=kvm -vga virtio -display sdl,gl=on Boots properly and has working 3d acceleration with virgl. Running qemu-system-x86_64 -name manjaro -enable-kvm -cpu host -smp cores=4,threads=1 -M q35 -m 8G -cdrom /mnt/Storage/ISO/manjaro- gnome-20.0.3-minimal-200606-linux56.iso -machine type=pc,accel=kvm -vga virtio -display gtk,gl=on however, (difference being gtk instead of sdl), the screen is black, and the vm still starts. System Specs Gentoo Linux 64bit Gentoo-Sources 5.8.13 Kernel Qemu 5.10.0-r1 compiled with USE="aio bzip2 caps curl fdt filecaps gtk jpeg ncurses nls opengl oss pin-upstream-blobs png pulseaudio sdl seccomp slirp spice usb usbredir vhost-net virgl vnc xattr xkb" PYTHON_TARGETS="python3_7" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64" Ryzen 7 2700x Nvidia 1070ti GPU I can confirm the same issue when using libvirt with opengl. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1898490/+subscriptions
