Bug 1730315

Created attachment 1591041 [details]
this is /var/log

This is the guest's /var/log , please check the dmesg information.

This is pretty odd.  It looks like a problem in the graphics rendering pipeline.  That does seem POWER specific - in that the shader compilation has ppc specific components.  However, that seems very *unlikely* to be related to qemu or KVM at all.

zhenzya,

Have you verified if the problem occurs if you leave out the SCSI hotplug operations, but otherwise do the same steps?

(In reply to David Gibson from comment #3)
> This is pretty odd.  It looks like a problem in the graphics rendering
> pipeline.  That does seem POWER specific - in that the shader compilation
> has ppc specific components.  However, that seems very *unlikely* to be
> related to qemu or KVM at all.
> 
> zhenzya,
> 
> Have you verified if the problem occurs if you leave out the SCSI hotplug
> operations, but otherwise do the same steps?

Additional info:

I leave out the SCSI hotplug operations and  do the same steps，but not hit the bug.

Tested with same steps on x86 host, not hit this issue.


Versions:

Host:
kernl-4.18.0-112.el8.x86_64
qemu-kvm-4.0.0-5.module+el8.1.0+3622+5812d9bf


Guest:
kernl-4.18.0-112.el8.x86_64

Additional info:
Find key points
1.boot guest with cli,Hotplug,reboot,hit the bug,the VNC will hang
-monitor stdio \

2.boot guest with cli,Hotplug,reboot,not hit the bug，the VNC is normal
-serial stdio \

Hotplug a lisiscsi ,hit this issue too.

{
    "execute": "blockdev-add",
        "arguments": {
            "node-name": "drive2",
            "driver": "qcow2",
            "file": {
                "driver":"iscsi",
                "transport":"tcp",
                "portal":"0.0.0.0",
                "initiator-name":"iqn.1994-05.com.redhat:b860749ffc6",
                "target":"iqn.2019-06.com.kvmqe:target0",
                "lun":1
            }
        }
}
{
    "execute":"device_add",
        "arguments":{
            "driver":"scsi-hd",
            "drive":"drive2",
            "id":"zhenyzha-hd"
                    }
}


Jul 25 15:46:21 dhcp19-129-84 kernel: llvmpipe-15[2802]: unhandled signal 11 at 0000800026de0000 nip 00007fffae73000c lr 00007fffacd9c984 code 1
Jul 25 15:46:21 dhcp19-129-84 kernel: llvmpipe-5[2792]: unhandled signal 11 at 0000800026de0000 nip 00007fffae73000c lr 00007fffacd9eb00 code 1
Jul 25 15:46:21 dhcp19-129-84 kernel: llvmpipe-3[2790]: unhandled signal 11 at 0000800026de0000 nip 00007fffae73000c lr 00007fffacd9c984 code 1
Jul 25 15:46:21 dhcp19-129-84 kernel: llvmpipe-2[2789]: unhandled signal 11 at 0000800026de0000 nip 00007fffae73000c lr 00007fffacd9c984 code 1
Jul 25 15:46:21 dhcp19-129-84 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jul 25 15:46:21 dhcp19-129-84 systemd[1]: Started Process Core Dump (PID 3895/UID 0).
Jul 25 15:46:23 dhcp19-129-84 journal[3193]: Error reading events from display: Broken pipe
Jul 25 15:46:23 dhcp19-129-84 gnome-session[2726]: gnome-session-binary[2726]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jul 25 15:46:23 dhcp19-129-84 gnome-session-binary[2726]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jul 25 15:46:23 dhcp19-129-84 org.gnome.Shell.desktop[2780]: (EE) failed to read Wayland events: Broken pipe
Jul 25 15:46:23 dhcp19-129-84 journal[3899]: g_hash_table_destroy: assertion 'hash_table != NULL' failed
Jul 25 15:46:23 dhcp19-129-84 gnome-session[2726]: gnome-session-binary[2726]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 25 15:46:23 dhcp19-129-84 gnome-session-binary[2726]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jul 25 15:46:23 dhcp19-129-84 gnome-session-binary[2726]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 25 15:46:23 dhcp19-129-84 journal[3222]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[3228]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[3204]: gsd-subman: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 at-spi-bus-launcher[2844]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 25 15:46:23 dhcp19-129-84 at-spi-bus-launcher[2844]:      after 21 requests (21 known processed) with 0 events remaining.
Jul 25 15:46:23 dhcp19-129-84 org.gnome.SettingsDaemon.Wacom.desktop[3899]: Unable to init server: Could not connect: Connection refused
Jul 25 15:46:23 dhcp19-129-84 org.gnome.SettingsDaemon.Wacom.desktop[3899]: Cannot open display:
Jul 25 15:46:23 dhcp19-129-84 journal[3220]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[3176]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[3190]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[3227]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul 25 15:46:23 dhcp19-129-84 journal[2938]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
Jul 25 15:46:23 dhcp19-129-84 systemd-logind[2347]: Session 1 logged out. Waiting for processes to exit.
Jul 25 15:46:23 dhcp19-129-84 systemd[1]: Created slice User Slice of UID 42.
Jul 25 15:46:23 dhcp19-129-84 systemd[1]: Started /run/user/42 mount wrapper.
Jul 25 15:46:23 dhcp19-129-84 systemd[1]: Starting User Manager for UID 42...
Jul 25 15:46:23 dhcp19-129-84 systemd-logind[2347]: New session c1 of user gdm.
Jul 25 15:46:23 dhcp19-129-84 systemd[1]: Started Session c1 of user gdm.
Jul 25 15:46:23 dhcp19-129-84 systemd-logind[2347]: Removed session 1.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Listening on Sound System.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Reached target Paths.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Reached target Timers.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Starting D-Bus User Message Bus Socket.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Listening on Multimedia System.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Listening on D-Bus User Message Bus Socket.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Reached target Sockets.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Reached target Basic System.
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Starting Sound Service...
Jul 25 15:46:23 dhcp19-129-84 systemd[1]: Started User Manager for UID 42.
Jul 25 15:46:23 dhcp19-129-84 systemd-coredump[3896]: Process 2780 (gnome-shell) of user 0 dumped core.#012#012Stack trace of thread 2790:#012#0  0x00007fffae73000c n/a (n/a)#012#1  0x00007fffacd9c984 lp_rast_shade_quads_mask (kms_swrast_dri.so)#012#2  0x00007fffacd9e8c4 lp_rast_triangle_2 (kms_swrast_dri.so)#012#3  0x00007fffacd9bc14 rasterize_scene (kms_swrast_dri.so)#012#4  0x00007fffacd9c5e0 thread_function (kms_swrast_dri.so)#012#5  0x00007fffacd9c330 impl_thrd_routine (kms_swrast_dri.so)#012#6  0x00007fffb45e8ae0 start_thread (libpthread.so.0)#012#7  0x00007fffb599eda8 __clone (libc.so.6)
Jul 25 15:46:23 dhcp19-129-84 systemd[3914]: Started D-Bus User Message Bus.
Jul 25 15:46:24 dhcp19-129-84 org.gnome.Shell.desktop[3954]: pci id for fd 11: 1234:1111, driver (null)
Jul 25 15:46:24 dhcp19-129-84 journal[3954]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 8.0, 128 bits)), falling back to CPU copy path
Jul 25 15:46:24 dhcp19-129-84 pulseaudio[3926]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Jul 25 15:46:24 dhcp19-129-84 pulseaudio[3926]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Jul 25 15:46:24 dhcp19-129-84 pulseaudio[3926]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.pulse-cookie': No such file or directory
Jul 25 15:46:24 dhcp19-129-84 pulseaudio[3926]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.pulse-cookie': No such file or directory

Created attachment 1593382 [details]
Boot up snapshot img log

Additional info:
Another scene test
1.Create snapshot with iscsi backend,Boot up snapshot hit the bug too .
And found other problems ，If it's not the same symptoms please tell me
 
This kind of scene is used ‘-serial stdio‘

Serial port printing garbled
        [-1;-1f[-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 40:f2:e9:5d:9c:07  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [-1;-1f■ ■ ■ [  OK  ] Created slice system-user\x2druntime\x2ddir.slice.
[  OK  ] Started /run/user/0 mount wrapper.
[  OK  ] Created slice User Slice of UID 0.
         Starting User Manager for UID 0...
[  OK  ] Started Session 1 of user root.

#vim /var/log/message
Jul 25 18:44:55 dhcp19-129-84 smartd[2298]: Device: /dev/sda, opened
Jul 25 18:44:55 dhcp19-129-84 smartd[2298]: Device: /dev/sda, [QEMU     QEMU HARDDISK    2.5+], lu id: error: bad structure, 21.4 GB
Jul 25 18:44:55 dhcp19-129-84 smartd[2298]: Device: /dev/sda, IE (SMART) not enabled, skip device
Jul 25 18:44:55 dhcp19-129-84 smartd[2298]: Try 'smartctl -s on /dev/sda' to turn on SMART features
Jul 25 18:44:55 dhcp19-129-84 chronyd[2323]: Frequency 41.609 +/- 0.111 ppm read from /var/lib/chrony/drift
Jul 25 18:44:55 dhcp19-129-84 smartd[2298]: Monitoring 0 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Jul 25 18:44:55 dhcp19-129-84 chronyd[2323]: Using right/UTC timezone to obtain leap second data
Jul 25 18:44:55 dhcp19-129-84 systemd[1]: Started ppc64-diag rtas_errd (platform error handling) Service.
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        ether 40:f2:e9:5d:9c:07  txqueuelen 1000  (Ethernet)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        RX packets 0  bytes 0 (0.0 B)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        RX errors 0  dropped 0  overruns 0  frame 0
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        TX packets 0  bytes 0 (0.0 B)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]: lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        inet 127.0.0.1  netmask 255.0.0.0
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        inet6 ::1  prefixlen 128  scopeid 0x10<host>
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        loop  txqueuelen 1000  (Local Loopback)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        RX packets 0  bytes 0 (0.0 B)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        RX errors 0  dropped 0  overruns 0  frame 0
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        TX packets 0  bytes 0 (0.0 B)
Jul 25 18:44:56 dhcp19-129-84 rc.local[2505]:        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Jul 25 18:44:57 dhcp19-129-84 org.gnome.Shell.desktop[2802]: pci id for fd 11: 1234:1111, driver (null)
Jul 25 18:44:57 dhcp19-129-84 journal[2802]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 8.0, 128 bits)), falling back to CPU copy path

Jul 25 18:44:58 dhcp19-129-84 org.gnome.Shell.desktop[2802]: Failed to initialize glamor, falling back to sw

Jul 25 18:45:00 dhcp19-129-84 journal[3417]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
Jul 25 18:45:00 dhcp19-129-84 journal[3417]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jul 25 18:45:00 dhcp19-129-84 journal[2802]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jul 25 18:45:00 dhcp19-129-84 journal[3465]: failed to get edid: unable to get EDID for output
Jul 25 18:45:00 dhcp19-129-84 dbus-daemon[2741]: [session uid=0 pid=2741] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9'
Jul 25 18:45:00 dhcp19-129-84 systemd[2568]: Started Evolution address book service.
Jul 25 18:45:00 dhcp19-129-84 journal[3465]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
Jul 25 18:45:01 dhcp19-129-84 org.gnome.Shell.desktop[2802]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 25 18:45:01 dhcp19-129-84 org.gnome.Shell.desktop[2802]: > Warning:          Unsupported maximum keycode 374, clipping.
Jul 25 18:45:01 dhcp19-129-84 org.gnome.Shell.desktop[2802]: >                   X11 cannot support keycodes above 255.
Jul 25 18:45:01 dhcp19-129-84 org.gnome.Shell.desktop[2802]: Errors from xkbcomp are not fatal to the X server


Jul 25 18:45:21 dhcp19-129-84 dbus-daemon[2302]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jul 25 18:45:21 dhcp19-129-84 pulseaudio[2678]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jul 25 18:45:28 dhcp19-129-84 systemd-logind[2414]: New session 3 of user root.
Jul 25 18:45:28 dhcp19-129-84 systemd[1]: Started Session 3 of user root.
Jul 25 18:46:11 dhcp19-129-84 chronyd[2323]: Selected source 10.5.26.10
Jul 25 18:50:13 dhcp19-129-84 kernel: llvmpipe-6[2824]: unhandled signal 11 at 0000800028370000 nip 00007fffa8bd0018 lr 00007fff9b0cc984 code 1
Jul 25 18:50:13 dhcp19-129-84 systemd[1]: Starting system activity accounting tool...
Jul 25 18:50:13 dhcp19-129-84 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jul 25 18:50:13 dhcp19-129-84 systemd[1]: Started Process Core Dump (PID 3874/UID 0).
Jul 25 18:50:13 dhcp19-129-84 systemd[1]: Started system activity accounting tool.
Jul 25 18:50:15 dhcp19-129-84 journal[3436]: Error reading events from display: Broken pipe
Jul 25 18:50:15 dhcp19-129-84 gnome-session[2747]: gnome-session-binary[2747]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jul 25 18:50:15 dhcp19-129-84 gnome-session-binary[2747]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Jul 25 18:50:15 dhcp19-129-84 org.gnome.Shell.desktop[2802]: (EE) failed to read Wayland events: Broken pipe
Jul 25 18:50:15 dhcp19-129-84 journal[3878]: g_hash_table_destroy: assertion 'hash_table != NULL' failed

(In reply to zhenyzha from comment #9)
> Created attachment 1593382 [details]
> Boot up snapshot img log
> 
> Additional info:
> Another scene test
> 1.Create snapshot with iscsi backend,Boot up snapshot hit the bug too .
> And found other problems ，If it's not the same symptoms please tell me
>  
This iscsi backend cli 
Create snapshot with iscsi backend:
#qemu-img create -f qcow2 -b 'json:{"driver": "qcow2", "file": {"lun": "0", "portal": "0.0.0.0", "driver": "iscsi", "transport": "tcp", "target": "iqn.2019-06.com.kvmqe:target0"}}' iscsi://0.0.0.0:3260/iqn.2019-06.com.kvmqe:target0/1

boot snapshot guest:
#/usr/libexec/qemu-kvm \
-name zhenyzha-RHEL8.1 \
-sandbox off \
-m 32G \
-nodefaults \
-machine pseries \
-vga std \
-device nec-usb-xhci,id=xhci \
-device usb-tablet,id=usb-tablet0 \
-device usb-kbd,id=usb-kbd0 \
-smp 64,cores=32,threads=1,sockets=2 \
-vnc :30 \
-serial stdio \
-rtc base=utc,clock=host \
-boot order=cd,menu=off,strict=off \
-enable-kvm \
-qmp unix:/var/tmp/qmp-monitor-zhenyzha,server,nowait \
-qmp tcp:0:3001,server,nowait \
-device virtio-scsi-pci,bus=pci.0,addr=0x06,id=scsi-pci-0 \
-netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=40:f2:e9:5d:9c:07 \
-blockdev driver=iscsi,cache.direct=off,cache.no-flush=on,node-name=my_file2,transport=tcp,portal=0.0.0.0,\
target=iqn.2019-06.com.kvmqe:target0,lun=1 \
-blockdev driver=qcow2,node-name=my2,file=my_file2 \
-device scsi-hd,drive=my2,id=virtio0-0-3 \

Update information:
Reproduce this issue on ppc64le platform with latest qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93

1.boot guest with cli：
/usr/libexec/qemu-kvm \
-name 'zhenyzha' \
-machine pseries \
-device VGA,bus=pci.0,addr=0x2  \
-nodefaults \
-chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/monitor-qmpmonitor1,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control  \
-chardev socket,nowait,path=/var/tmp/serial-serial0,id=chardev_serial0,server \
-device spapr-vty,id=serial0,reg=0x30000000,chardev=chardev_serial0 \
-device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 \
-drive id=drive_image1,format=qcow2,if=none,aio=native,media=disk,cache=none,werror=stop,rerror=stop,file=os.qcow2 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pci.0,addr=0x4 \
-device virtio-net-pci,mac=8a:43:4c:8b:de:21,id=id46J4ui,netdev=idizNzdA,bus=pci.0,addr=0x5  \
-netdev tap,id=idizNzdA,vhost=on \
-m 100G  \
-vnc :30  \
-smp 64,maxcpus=64,cores=32,threads=1,sockets=2 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-rtc base=utc,clock=host  \
-boot order=cdn,once=c,menu=off,strict=off \
-enable-kvm \
-monitor stdio 

2.Hotplug a virtio-scsi disk with virtio-scsi-pci.
{"execute": "blockdev-add","arguments": {"node-name":"data_disk1","driver":"file","filename":"/home/kvm_autotest_root/images/stg1.qcow2"}}
{"execute": "blockdev-add","arguments": {"node-name": "disk1","driver":"qcow2","file":"data_disk1"}}
{"execute":"device_add","arguments":{"driver":"virtio-scsi-pci","id":"scsi1","bus":"pci.0","addr":"0x8"}} 
{"execute":"device_add","arguments":{"driver":"scsi-hd","drive":"disk1","id":"data-disk1","bus":"scsi1.0"}}

3.Format the disk and mount it
 # lsblk
 # mkfs.ext4 /dev/sda 
 # mount /dev/sda /mnt/

4.Connect to TigerVNC
dmesg display:
[   11.005016] XFS (vda2): Mounting V5 Filesystem
[   11.114567] XFS (vda2): Ending clean mount
[   18.451190] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   23.698197] fuse init (API version 7.27)
[   38.353269] llvmpipe-9[4750]: unhandled signal 11 at 00007fffe93f0000 nip 00007fff78080010 lr 00007fff7143ca24 code 1
[   38.353312] llvmpipe-6[4747]: unhandled signal 11 at 00007fffe93f0000 nip 00007fff78080010 lr 00007fff7143ca24 code 1

5.View the guest /var/log/messages: 
Aug 28 13:51:52 dhcp19-129-175 kernel: llvmpipe-9[4750]: unhandled signal 11 at 00007fffe93f0000 nip 00007fff78080010 lr 00007fff7143ca24 code 1
Aug 28 13:51:52 dhcp19-129-175 kernel: llvmpipe-6[4747]: unhandled signal 11 at 00007fffe93f0000 nip 00007fff78080010 lr 00007fff7143ca24 code 1
Aug 28 13:51:52 dhcp19-129-175 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Aug 28 13:51:52 dhcp19-129-175 systemd[1]: Started Process Core Dump (PID 5271/UID 0).
Aug 28 13:51:53 dhcp19-129-175 journal[5022]: Error reading events from display: Broken pipe
Aug 28 13:51:53 dhcp19-129-175 gnome-session[4289]: gnome-session-binary[4289]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Aug 28 13:51:53 dhcp19-129-175 gnome-session-binary[4289]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Aug 28 13:51:53 dhcp19-129-175 org.gnome.Shell.desktop[4451]: (EE) failed to read Wayland events: Broken pipe
Aug 28 13:51:53 dhcp19-129-175 gnome-session[4289]: gnome-session-binary[4289]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Aug 28 13:51:53 dhcp19-129-175 at-spi-bus-launcher[4876]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Aug 28 13:51:53 dhcp19-129-175 at-spi-bus-launcher[4876]:      after 21 requests (21 known processed) with 0 events remaining.
Aug 28 13:51:53 dhcp19-129-175 gnome-session-binary[4289]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 28 13:51:53 dhcp19-129-175 gnome-session-binary[4289]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Aug 28 13:51:53 dhcp19-129-175 journal[5059]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5052]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5046]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5020]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5004]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5049]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 28 13:51:53 dhcp19-129-175 journal[5278]: g_hash_table_destroy: assertion 'hash_table != NULL' failed
Aug 28 13:51:53 dhcp19-129-175 org.gnome.SettingsDaemon.Wacom.desktop[5278]: Unable to init server: Could not connect: Connection refused
Aug 28 13:51:53 dhcp19-129-175 org.gnome.SettingsDaemon.Wacom.desktop[5278]: Cannot open display:
........

ug 28 13:51:54 dhcp19-129-175 systemd[1]: Stopped /run/user/0 mount wrapper.
Aug 28 13:51:54 dhcp19-129-175 systemd[1]: Startup finished in 1.223s (kernel) + 3.981s (initrd) + 34.896s (userspace) = 40.101s.
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: pci id for fd 11: 1234:1111, driver (null)
Aug 28 13:51:54 dhcp19-129-175 systemd-coredump[5273]: Process 4451 (gnome-shell) of user 0 dumped core.#012#012Stack trace of thread 4750:#012#0  0x00007fff78080010 n/a (n/a)#012#1  0x00007fff7143ca24 lp_rast_shade_quads_mask (kms_swrast_dri.so)#012#2  0x00007fff7143d828 lp_rast_triangle_32_3_16 (kms_swrast_dri.so)#012#3  0x00007fff7143bcb4 rasterize_scene (kms_swrast_dri.so)#012#4  0x00007fff7143c680 thread_function (kms_swrast_dri.so)#012#5  0x00007fff7143c3d0 impl_thrd_routine (kms_swrast_dri.so)#012#6  0x00007fff7cc98ae0 start_thread (libpthread.so.0)#012#7  0x00007fff7e04e8f8 __clone (libc.so.6)
Aug 28 13:51:54 dhcp19-129-175 journal[5362]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 8.0, 128 bits)), falling back to CPU copy path
Aug 28 13:51:54 dhcp19-129-175 pulseaudio[5318]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Aug 28 13:51:54 dhcp19-129-175 pulseaudio[5318]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.config/pulse/cookie': No such file or directory
Aug 28 13:51:54 dhcp19-129-175 pulseaudio[5318]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.pulse-cookie': No such file or directory
Aug 28 13:51:54 dhcp19-129-175 pulseaudio[5318]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.pulse-cookie': No such file or directory
Aug 28 13:51:54 dhcp19-129-175 systemd[5289]: Started Sound Service.
Aug 28 13:51:54 dhcp19-129-175 systemd[5289]: Reached target Default.
Aug 28 13:51:54 dhcp19-129-175 systemd[5289]: Startup finished in 892ms.
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: glamor: No eglstream capable devices found
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: glamor: 'wl_drm' not supported
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: Missing Wayland requirements for glamor GBM backend
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: Missing Wayland requirements for glamor EGLStream backend
Aug 28 13:51:54 dhcp19-129-175 org.gnome.Shell.desktop[5362]: Failed to initialize glamor, falling back to sw
Aug 28 13:51:55 dhcp19-129-175 dbus-daemon[5322]: [session uid=42 pid=5322] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.15' (uid=42 pid=5362 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")

Actual results:
systemd-coredump

Expected results:
the guest without systemd-coredump

Tested with same steps on x86 host, not hit systemd-coredump

this x86_64 guest messages:
 kdumpctl[2532]: Rebuilding /boot/initramfs-4.18.0-135.el8.x86_64kdump.img
 journal[2428]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 8.0, 256 bits)), falling back to CPU copy path
 org.gnome.Shell.desktop[2428]: glamor: No eglstream capable devices found
 org.gnome.Shell.desktop[2428]: glamor: 'wl_drm' not supported
 org.gnome.Shell.desktop[2428]: Missing Wayland requirements for glamor GBM backend
 org.gnome.Shell.desktop[2428]: Missing Wayland requirements for glamor EGLStream backend
 org.gnome.Shell.desktop[2428]: Failed to initialize glamor, falling back to sw
 kdumpctl[2532]: Warning: There might not be enough space to save a vmcore.
 kdumpctl[2532]:         The size of /dev/mapper/rhel_bootp--73--199--15-root should be greater than 15222944 kilo bytes.
......
 journal[4831]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
 dracut[3032]: *** Including module: prefixdevname ***
 journal[4831]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
 dracut[3032]: *** Including module: dm ***
 systemd[1]: Starting Manage, Install and Generate Color Profiles...
 systemd[1]: Starting Locale Service...
 journal[4982]: failed to get edid data: EDID length is too small
 dbus-daemon[1725]: [system] Successfully activated service 'org.freedesktop.ColorManager'
 systemd[1]: Started Manage, Install and Generate Color Profiles.

 systemd[2016]: Started Evolution address book service.
 journal[2428]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
 journal[4884]: failed to get edid: unable to get EDID for output
 dbus-daemon[2236]: [session uid=0 pid=2236] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.59' (uid=0 pid=5036 comm="/usr/libexec/evolution-calendar-factory-subprocess" label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
 systemd[2016]: Starting Virtual filesystem metadata service...
 dbus-daemon[2236]: [session uid=0 pid=2236] Successfully activated service 'org.gtk.vfs.Metadata'
 systemd[2016]: Started Virtual filesystem metadata service.
 journal[4884]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
 org.gnome.Shell.desktop[2428]: The XKEYBOARD keymap compiler (xkbcomp) reports:
 org.gnome.Shell.desktop[2428]: > Warning:          Unsupported maximum keycode 374, clipping.
 org.gnome.Shell.desktop[2428]: >                   X11 cannot support keycodes above 255.
 org.gnome.Shell.desktop[2428]: Errors from xkbcomp are not fatal to the X server

Update information:
Tested with same steps on ppc64le host with latest qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282, not hit systemd-coredump.

[root@dhcp19-129-51 ~]# dmesg | grep llvmpipe
[root@dhcp19-129-51 ~]# 

check the guest /var/log/messages: 
Sep  9 09:09:51 dhcp19-129-51 kdumpctl[4543]: Modified cmdline:BOOT_IMAGE=/vmlinuz-4.18.0-141.el8.ppc64le ro console=ttyS0,115200 biosdevname=0 net.ifnames=0 rhgb console=tty0 irqpoll maxcpus=1 noirqdistrib reset_devices cgroup_disable=memory numa=off udev.children-max=2 ehea.use_mcs=0 panic=10 rootflags=nofail kvm_cma_resv_ratio=0 transparent_hugepage=never novmcoredd elfcorehdr=158336K
Sep  9 09:09:51 dhcp19-129-51 journal[4538]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 8.0, 128 bits)), falling back to CPU copy path
Sep  9 09:09:51 dhcp19-129-51 kdumpctl[4543]: kexec: loaded kdump kernel
Sep  9 09:09:51 dhcp19-129-51 kdumpctl[4543]: Starting kdump: [OK]
Sep  9 09:09:51 dhcp19-129-51 systemd[1]: Started Crash recovery kernel arming.


host:4.18.0-141.el8.ppc64le
     qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282
CPU Model:2.3 (pvr 004e 1203)

guest:4.18.0-141.el8.ppc64le

So close this bug.

It's very interesting you can no longer reproduce this.

This bug is nasty enough I'd like to be more confident about exactly what fixed it.

Can you please test the intermediate downstream qemu versions to see which versions show the problem and which don't.  If I understand the above:

qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93    => reproduces
qemu-kvm-4.1.0-5.module+el8.1.0+4076+b5e41ebc    => ?
qemu-kvm-4.1.0-6.module+el8.1.0+4164+854d66f5    => ?
qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282    => does not reproduce

(In reply to David Gibson from comment #14)
> It's very interesting you can no longer reproduce this.
> 
> This bug is nasty enough I'd like to be more confident about exactly what
> fixed it.
> 
> Can you please test the intermediate downstream qemu versions to see which
> versions show the problem and which don't.  If I understand the above:
> 
> qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93    => reproduces
> qemu-kvm-4.1.0-5.module+el8.1.0+4076+b5e41ebc    => ?
> qemu-kvm-4.1.0-6.module+el8.1.0+4164+854d66f5    => ?
> qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282    => does not reproduce

Ok, I will further verify,then update results later.

(In reply to David Gibson from comment #14)

Hi David:
I think the problem has two points, 1.host kernel and 2.qemu-kvm.
Because when I use qemu-kvm-4.1.0-4 and 4.18.0-141.el8.ppc64le, I can't reproduce this bug.
    But when I use qemu-kvm-4.1.0-4 and 4.18.0-135.el8.ppc64le, I reproduce this bug.
Below are my test results, I tested only twice for each test. So it may not be comprehensive enough, please let me know if I am mistaken.
the guest guest 4.18.0-141.el8.ppc64le

1.different kernel
> qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93 + host kernel:4.18.0-135.el8.ppc64le  => reproduces
> qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93 + host kernel:4.18.0-141.el8.ppc64le  => does not reproduce

2.different qemu-kvm
> qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93 + host kernel:4.18.0-135.el8.ppc64le  => reproduces
> qemu-kvm-4.1.0-5.module+el8.1.0+4076+b5e41ebc + host kernel:4.18.0-135.el8.ppc64le  => does not reproduce
> qemu-kvm-4.1.0-6.module+el8.1.0+4164+854d66f5 + host kernel:4.18.0-135.el8.ppc64le  => does not reproduce
> qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282 + host kernel:4.18.0-135.el8.ppc64le  => does not reproduce


=============================================================================================================The following is the details
when I use Comment 13 host,
host kernel:4.18.0-135.el8.ppc64le 
guest kernel:4.18.0-141.el8.ppc64le
qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93
hit this issue.
Sep  9 18:21:21 dhcp19-129-51 kernel: llvmpipe-15[4795]: unhandled signal 11 at 00007ffff4e00000 nip 00007fff7c000010 lr 00007fff74deca24 code 1
Sep  9 18:21:21 dhcp19-129-51 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Sep  9 18:21:21 dhcp19-129-51 systemd[1]: Started Process Core Dump (PID 5323/UID 0).
Sep  9 18:21:22 dhcp19-129-51 pulseaudio[4211]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Sep  9 18:21:22 dhcp19-129-51 dbus-daemon[3782]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Sep  9 18:21:22 dhcp19-129-51 journal[4980]: Error reading events from display: Broken pipe
Sep  9 18:21:22 dhcp19-129-51 journal[5154]: Error reading events from display: Broken pipe
Sep  9 18:21:22 dhcp19-129-51 gnome-session[4306]: gnome-session-binary[4306]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Sep  9 18:21:22 dhcp19-129-51 gnome-session-binary[4306]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Sep  9 18:21:22 dhcp19-129-51 org.gnome.Shell.desktop[4612]: (EE) failed to read Wayland events: Broken pipe
Sep  9 18:21:22 dhcp19-129-51 journal[5328]: g_hash_table_destroy: assertion 'hash_table != NULL' failed
Sep  9 18:21:22 dhcp19-129-51 gnome-session-binary[4306]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep  9 18:21:22 dhcp19-129-51 gnome-session-binary[4306]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Sep  9 18:21:22 dhcp19-129-51 gnome-session[4306]: gnome-session-binary[4306]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Sep  9 18:21:22 dhcp19-129-51 org.gnome.SettingsDaemon.Wacom.desktop[5328]: Unable to init server: Could not connect: Connection refused
Sep  9 18:21:22 dhcp19-129-51 org.gnome.SettingsDaemon.Wacom.desktop[5328]: Cannot open display:
Sep  9 18:21:22 dhcp19-129-51 journal[5014]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:22 dhcp19-129-51 at-spi-bus-launcher[4837]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Sep  9 18:21:22 dhcp19-129-51 at-spi-bus-launcher[4837]:      after 21 requests (21 known processed) with 0 events remaining.
Sep  9 18:21:22 dhcp19-129-51 journal[4964]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:22 dhcp19-129-51 journal[5007]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:22 dhcp19-129-51 journal[4979]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:22 dhcp19-129-51 journal[5013]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:22 dhcp19-129-51 journal[5003]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep  9 18:21:23 dhcp19-129-51 systemd-logind[3857]: Session 1 logged out. Waiting for processes to exit.


host kernel:4.18.0-135.el8.ppc64le 
guest kernel:4.18.0-141.el8.ppc64le
qemu-kvm-4.1.0-5.module+el8.1.0+4076+b5e41ebc
no hit this issue.

host kernel:4.18.0-135.el8.ppc64le 
guest kernel:4.18.0-141.el8.ppc64le
qemu-kvm-4.1.0-6.module+el8.1.0+4162+847d444a
no hit this issue.

host kernel:4.18.0-135.el8.ppc64le 
guest kernel:4.18.0-141.el8.ppc64le
qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282
no hit this issue.

host kernel:4.18.0-141.el8.ppc64le
guest kernel:4.18.0-141.el8.ppc64le
qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93
no hit this issue.