Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1195889 - [RFE] Spice Wan Optimization for Linux Guests [NEEDINFO]
[RFE] Spice Wan Optimization for Linux Guests
Status: NEW
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.2.0
Unspecified All
medium Severity high
: ovirt-4.3.0
: ---
Assigned To: Martin Tessun
meital avital
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-02-24 14:37 EST by Chris Reynolds
Modified: 2018-07-18 10:35 EDT (History)
19 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Spice
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mtessun: needinfo? (cschalle)
mtessun: needinfo? (dblechte)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 284013 None None None Never

  None (edit)
Description Chris Reynolds 2015-02-24 14:37:05 EST
Description of problem:	

Customer is looking to bring on 50+ remote users to aide in development.  They will be connecting from a Window 7 x86_64 workstation through a VPN and pulling back RHEL 6.4+ x86_64 workstations with KDE 4 as their desktop.  

Spice  "WAN Optimization features" are only applicable to windows guests.  Is there any known procedure for optimizing Linux guests?  

* separate Display network
* make sure latency is less than 150ms
* keep resolution down if possible
* disable desktop effects in Windows
* only enable the # of monitors you really need
* bond mode 4 or something for performance
* Enable "WAN Optimizations" under Console Options if latency is high or performance is bad
* Make sure rhev-tools is updated (Windows) or x11-qxl drivers (RHEL) with rhev-agent running

Version-Release number of selected component (if applicable):
3.2

How reproducible:

very

Steps to Reproduce:
1. install rhev
2. install gues
3. have lots of users

Actual results:
high bandwidth usage

Expected results:
low bandwidth usage via spice optimization

Additional info:
01022634 - SFDC
Comment 15 spower 2018-07-03 06:44:22 EDT
We agreed to remove RFEs component from Bugzilla, if you feel the component has been renamed incorrectly please reach out.
Comment 16 Robert McSwain 2018-07-03 16:44:36 EDT
(In reply to spower from comment #15)
> We agreed to remove RFEs component from Bugzilla, if you feel the component
> has been renamed incorrectly please reach out.

Hello, What does this mean for this RFE? How should this be moved forward, considering this is still an important issue for the customer?
Comment 17 Gary Lamb 2018-07-06 11:28:53 EDT
Hi,
To follow-up on Robert's question. We need clarity on the customer impact here. Is this moving forward? What expectations should we set for the customer?

Thanks,
Gary
Comment 18 Martin Tessun 2018-07-06 13:02:01 EDT
It simply means that the RFE component is no longer available and instead the keyword FutureFeature should be used (best in conjunction with [RFE] keyword in the subject).

Besides this nothing does change.

@Christian: Can we get some feeback on c#13, please.

Note You need to log in before you can comment on or make changes to this bug.