RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1460198 - RFE: enable LZ4 compression in spice-gtk
Summary: RFE: enable LZ4 compression in spice-gtk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.5
Assignee: Victor Toso
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On: 1432958
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-09 11:02 UTC by David Jaša
Modified: 2018-04-10 08:51 UTC (History)
9 users (show)

Fixed In Version: spice-gtk-0.34-2.el7
Doc Type: Enhancement
Doc Text:
Clone Of: 1460191
Environment:
Last Closed: 2018-04-10 08:50:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0672 0 None None None 2018-04-10 08:51:23 UTC

Description David Jaša 2017-06-09 11:02:12 UTC 
Description of problem:
LZ4 is good algorithm in both low CPU utilization and high compression ratio so it would be nice to have it as a RHEL default.
This bug depends on lz4 library inclusion in el7.

Version-Release number of selected component (if applicable):
RHEL 7.4 / spice-server-0.12.8-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Victor Toso 2017-06-09 11:07:55 UTC 
Yes, Not much to be done in the codebase, we just need lz4 lib in.
Comment 5 Radek Duda 2017-12-19 15:07:22 UTC 
could you give me a hint how to verify this one?
I see liblz4.so.1()(64bit) among required (rpm -qR spice-gtk3), but no mention of lz4 in spice-debug log nor debug log..
So how to detect that data are actually compressed?
Comment 6 Victor Toso 2017-12-19 16:16:19 UTC 
(In reply to Radek Duda from comment #5)
> could you give me a hint how to verify this one?
> I see liblz4.so.1()(64bit) among required (rpm -qR spice-gtk3), but no
> mention of lz4 in spice-debug log nor debug log..
> So how to detect that data are actually compressed?

$ ldd /usr/lib64/libspice-client-gtk-3.0.so | grep -i lz4
        liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007fec70915000)

$ ldd /usr/lib64/libspice-client-glib-2.0.so | grep -i lz4
        liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007fba8bedc000)

$ remote-viewer --help-spice | grep -i lz4
  --spice-preferred-compression=<auto-glz,auto-lz,quic,glz,lz,lz4,off>  Preferred image compression algorithm

and you should have no problems while using lz4 compression.
Comment 10 errata-xmlrpc 2018-04-10 08:50:15 UTC 
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.

https://access.redhat.com/errata/RHBA-2018:0672
Note You need to log in before you can comment on or make changes to this bug.