Hide Forgot
Description of problem: When switching youtube video to full-screen mode Xorg does crash because of running out of memory drawing images. If I do increase available memory using qemu switch -global qxl-vga.vram_size=268435456 then I am able to switch to full-screen without the crash, that's why I believe we should increase default amount of memory available to qxl device, which is known issue. This bug hopefully pushes it forward. Version-Release number of selected component (if applicable): spice-client-0.8.0-2.el6.x86_64 spice-protocol-0.8.0-1.el6.noarch spice-server-0.8.0-1.el6.x86_6 xorg-x11-drv-qxl-0.0.12-9.el6 qemu-kvm-0.12.1.2-2.159.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Run qemu instance with spice support and RHEL guest with qxl device installed and used. 2. Open youtube website and try to open any video in full-screen mode. Actual results: Xorg's crash: Out of memory allocating 8294420 bytes Out of mem - stats Expected results: No crash, video in full-screen Additional info: Increase vram size with adding option to qemu instance i.e. -global qxl-vga.vram_size=268435456 when using one qxl device and no crash appears.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
It does not happen with older qxl - xorg-x11-drv-qxl-0.0.12-2.1 -> marking as regression.
Devel ack, though it would be useful to also open a bug against libvirt to make it set vram to 256MB by default.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2011-1621.html