Bug 896457

Not sure it's related,  FYI
Bug 883654 - qemu crashes when rebooting the guest: SpiceWorker-ERROR **: red_worker.c:4797:qxl_process_cursor: invalid cursor command 235
Bug 887775 - qemu-kvm crashed on ../spice-common/common/ring.h:121:ring_next: assertion `pos->next != NULL && pos->prev != NULL' failed

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

FYI
From bt
very similar Bug 868807 - Qemu aborted when change the resolution of guest from 1024x768 to 2560x1600  

--snip of Bug 868807 bt--
Program received signal SIGABRT, Aborted.
0x00007ffff574c8a5 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff574c8a5 in raise () from /lib64/libc.so.6
#1  0x00007ffff574e085 in abort () from /lib64/libc.so.6
#2  0x00007ffff5fa5c35 in spice_logv (log_domain=0x7ffff6021d9c "SpiceWorker", log_level=SPICE_LOG_LEVEL_CRITICAL, strloc=0x7ffff60220bd "red_worker.c:10916", function=
    0x7ffff6023d90 "red_push_monitors_config", format=0x7ffff60220a7 "condition `%s' failed", args=0x7fffe5bfb970) at log.c:109
#3  0x00007ffff5fa5d6a in spice_log (log_domain=<value optimized out>, log_level=<value optimized out>, strloc=<value optimized out>, function=<value optimized out>, 
    format=<value optimized out>) at log.c:123
#4  0x00007ffff5f8390d in on_new_display_channel_client (opaque=<value optimized out>, payload=0x7ffec421d0b0) at red_worker.c:9489
#5  handle_new_display_channel (opaque=<value optimized out>, payload=0x7ffec421d0b0) at red_worker.c:10376
#6  handle_dev_display_connect (opaque=<value optimized out>, payload=0x7ffec421d0b0) at red_worker.c:11216
#7  0x00007ffff5f63cc7 in dispatcher_handle_single_read (dispatcher=0x7ffff8b86c78) at dispatcher.c:139
#8  dispatcher_handle_recv_read (dispatcher=0x7ffff8b86c78) at dispatcher.c:162
#9  0x00007ffff5f8488e in red_worker_main (arg=<value optimized out>) at red_worker.c:11782
#10 0x00007ffff7740851 in start_thread () from /lib64/libpthread.so.0
#11 0x00007ffff580167d in clone () from /lib64/libc.so.6
(gdb)

Hi, Xu

Would you please update the following 2 question?
1. How reproducible?
2. It is a regressional bug?

Best Regards & Thanks,
Junyi

(In reply to comment #4)
> FYI
> From bt
> very similar Bug 868807 - Qemu aborted when change the resolution of guest
> from 1024x768 to 2560x1600  
> 
> --snip of Bug 868807 bt--
> Program received signal SIGABRT, Aborted.
> 0x00007ffff574c8a5 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00007ffff574c8a5 in raise () from /lib64/libc.so.6
> #1  0x00007ffff574e085 in abort () from /lib64/libc.so.6
> #2  0x00007ffff5fa5c35 in spice_logv (log_domain=0x7ffff6021d9c
> "SpiceWorker", log_level=SPICE_LOG_LEVEL_CRITICAL, strloc=0x7ffff60220bd
> "red_worker.c:10916", function=
>     0x7ffff6023d90 "red_push_monitors_config", format=0x7ffff60220a7
> "condition `%s' failed", args=0x7fffe5bfb970) at log.c:109
> #3  0x00007ffff5fa5d6a in spice_log (log_domain=<value optimized out>,
> log_level=<value optimized out>, strloc=<value optimized out>,
> function=<value optimized out>, 
>     format=<value optimized out>) at log.c:123
> #4  0x00007ffff5f8390d in on_new_display_channel_client (opaque=<value
> optimized out>, payload=0x7ffec421d0b0) at red_worker.c:9489
> #5  handle_new_display_channel (opaque=<value optimized out>,
> payload=0x7ffec421d0b0) at red_worker.c:10376
> #6  handle_dev_display_connect (opaque=<value optimized out>,
> payload=0x7ffec421d0b0) at red_worker.c:11216
> #7  0x00007ffff5f63cc7 in dispatcher_handle_single_read
> (dispatcher=0x7ffff8b86c78) at dispatcher.c:139
> #8  dispatcher_handle_recv_read (dispatcher=0x7ffff8b86c78) at
> dispatcher.c:162
> #9  0x00007ffff5f8488e in red_worker_main (arg=<value optimized out>) at
> red_worker.c:11782
> #10 0x00007ffff7740851 in start_thread () from /lib64/libpthread.so.0
> #11 0x00007ffff580167d in clone () from /lib64/libc.so.6
> (gdb)
> 
> Hi, Xu
> 
> Would you please update the following 2 question?
> 1. How reproducible?
> 2. It is a regressional bug?
> 
> Best Regards & Thanks,
> Junyi

Hi, Junyi

This defeat found in anaysis autotest job reboot testcase, it just happend once and I have try to reporduce but no stable way to reporduce it;

thanks,
Xu

Since this bug only happened once and is not reproducible (comment #5),
I'm closing the bug (insufficient data).

Please reopen if a way to reproduce this bug is found.