A hang can occur while taking qemu screendumps and a spice client is connected: Thread 2 (Thread 0x7f46aa7fd700 (LWP 23002)): #0 0x000000373a0ab6ad in nanosleep () at ../sysdeps/unix/syscall-template.S:82 #1 0x000000373a0d9954 in usleep (useconds=<optimized out>) at ../sysdeps/unix/sysv/linux/usleep.c:33 #2 0x00007f46b1c39bc8 in flush_display_commands (worker=0x7f46aa6255e0) at red_worker.c:8932 #3 0x00007f46b1c3a1b9 in handle_dev_update (worker=0x7f46aa6255e0) at red_worker.c:10149 #4 handle_dev_input (listener=0x7f46aa6255e0, events=<optimized out>) at red_worker.c:10416 #5 0x00007f46b1c3c582 in red_worker_main (arg=<optimized out>) at red_worker.c:10803 #6 0x000000373a807b31 in start_thread (arg=0x7f46aa7fd700) at pthread_create.c:305 #7 0x000000373a0dfd2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
So this is the usual bug that was fixed by introducing handle_dev_update_async, and requires an update guest driver. Do you still get it if you use the fc17 driver that you build (xorg-x11-drv-qxl-0.0.21-13.fc17 or newer), or the latest windows qxl driver from http://spice-space.org/download/binaries/qxl-win-0.1012-20111107-ff93ec988c.zip ?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.