Bug 1869216 - QEMU fails to start any display using either gtk or sdl
Summary: QEMU fails to start any display using either gtk or sdl
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1869090 1869339 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 10:17 UTC by Jacques YE
Modified: 2020-09-28 11:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-18 17:17:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jacques YE 2020-08-17 10:17:58 UTC
Description of problem:
When launching QEMU on the command line, it fails to output any window display using either SDL or GTK.

It works fine when using VNC.

Version-Release number of selected component (if applicable):
QEMU emulator version 5.1.0 (qemu-5.1.0-1.fc34)

How reproducible:
100%

Steps to Reproduce:
1. Try to start QEMU using CLI with "qemu-kvm -display gtk" or "qemu-kvm -display sdl"
2. QEMU fails to start any display

Actual results:
outputs of "qemu-kvm -display gtk"
```
Failed to open module: /usr/lib64/qemu/ui-gtk.so: undefined symbol: qemu_xkeymap_keycodes_semaphore
qemu-system-x86_64: Display 'gtk' is not available.
```

outputs of "qemu-kvm -display sdl"
``` 
Failed to open module: /usr/lib64/qemu/ui-sdl.so: undefined symbol: qemu_xkeymap_keycodes_semaphore
qemu-system-x86_64: Display 'sdl' is not available.
 
```

Expected results:
QEMU starts with a display using either SDL or GTK

Additional info:
QEMU will not fail when no options/argument is provided but instead fallback to VNC

Comment 1 Cole Robinson 2020-08-17 22:23:58 UTC
*** Bug 1869090 has been marked as a duplicate of this bug. ***

Comment 2 Cole Robinson 2020-08-17 22:24:19 UTC
*** Bug 1869339 has been marked as a duplicate of this bug. ***

Comment 3 Cole Robinson 2020-08-17 22:25:40 UTC
I put some findings here but I still don't know what the root issue is: https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg03726.html

Builds are currently running that disable dtrace tracing output which will work around this problem

Comment 4 Daniel Berrangé 2020-08-18 12:31:48 UTC
The root cause is a change in systemtap behaviour https://bugzilla.redhat.com/show_bug.cgi?id=1869642  but arguably this is a long standing QEMU bug we've just been lucky not to hit before.

Comment 5 Cole Robinson 2020-08-18 17:17:23 UTC
Awesome thanks for digging into it Dan!

I filed this qemu bug to track re-enabling dtrace backend when we have a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1869807

The issue reported in this bug is fixed in qemu-5.1.0-2 though, so closing

Comment 6 Richard W.M. Jones 2020-09-28 11:53:33 UTC
For anyone searching for this bug who thinks it might not be fixed, you
have to also install qemu-ui-gtk.


Note You need to log in before you can comment on or make changes to this bug.