Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
-------------------------
Connect guest with spice under poor network speed, guest running slow.
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
qemu-kvm-1.5.3-19.el7.x86_64
How reproducible:
------------------
100%
Steps to Reproduce:
--------------------
1. boot guest with qxl and spice connection
2. connect guest on another host which has poor network speed to the host running the guest (suggest using wireless or vpn to reproduce).
3. reboot guest, booting log shows up one line by one line, comparing to vnc, booting log shows up tens of lines by tens of lines (for poor speed, when next frame refreshes, tens of lines have been generated, this is understandable, but with spice, it looks like guest runs really slow rather than only displaying, it takes far more time with spice to boot up)
4. run dmesg in guest, the situation is the same with step 3, with spice, the dmesg message shows up one line by one line, it takes very long time to display all log.
Expected results:
-------------------
spice should behavior like vnc when network is poor.
Additional info:
------------------
both guest and host are in level 3 during testing.
Comment 2RHEL Program Management
2014-03-22 06:26:32 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3Marc-Andre Lureau
2014-07-06 21:46:25 UTC
this is due to spice server design, which will "slow" rendering for the client connection to get all relevant drawing operations. imho, this is a bad design and it should be improved. However, given that it was done like this by design, it is not a bug and should be an like "RFE: do not slow rendering & guest if client is slow"
Comment 5Marc-Andre Lureau
2015-01-02 15:36:46 UTC
moving to 7.2
Comment 10Marc-Andre Lureau
2015-04-21 23:52:45 UTC
unlikely to happen in 7.2, it must first land upstream. imho, we should consider moving the bug there.