Red Hat Bugzilla – Bug 734816
qemu should be compiled with --enable-vnc-png flag
Last modified: 2013-01-09 19:16:10 EST
Description of problem:
Qemu does not use tightPNG encoding
Version-Release number of selected component (if applicable):
In order to correctly use noVNC with the maximal speed (http://github.com/kanaka/novnc), qemu needs to be compiled with --enable-vnc-png.
Is it possible to enable this ? (maybe it is on Fedora 16, in that case, my bad)
anyone on this?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I don't want to enable a new code path for F15 since we are EOL in a month. Moving to F16.
Dan, I know you're familiar with the qemu VNC code, any reason we shouldn't --enable-vnc-png and/or --enable-vnc-jpeg?
I've had both of these options enabled (and --enable-vnc-thread) in my own build for months, and haven't noticed any issues. Now that we have NoVNC as part of Openstack, could we at least enable this in Rawhide?
I see no problem with setting --enable-vnc-png and --enable-vnc-jpeg.
I'm not so sure about --enable-vnc-thread - we should probably ask upstream about this. If the VNC thread is stable & "better", then I think we should probably just suggest that upstream enable it permanently & remove the configure option. If it isn't stable or better, then we shouldn't enable it in Fedora.
Actually, it looks like qemu is already built with vnc png and jpeg support.
The addition of libpng-devel and libjpeg-devel as BuildRequires in qemu 2:1.0-6 took care of this.
I agree with asking upstream to make the threaded VNC server the default.
I guess this bug can be closed?
Closing per comment #6