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 1017300 - Spice Vdagent: Large File Transfer: Leaves the Guest unusable for ~1min
Summary: Spice Vdagent: Large File Transfer: Leaves the Guest unusable for ~1min
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-vdagent
Version: 6.5
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-09 15:16 UTC by Vimal Patel
Modified: 2023-09-14 01:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 14:57:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vimal Patel 2013-10-09 15:16:05 UTC
Description of problem:
I tried to transfer a large video (450MB) from the client (Win7) to the guest (RHEL6.5), and the guest was unusable for around a minute while the file was being transferred, trying to type in a terminal in the guest, pixels refreshing can be seen very clearly as it updates the whole terminal window, which takes seconds.

Version-Release number of selected component (if applicable):
Client Windows 7:
mingw-virt-viewer-0.5.6-6.el6_4

Host: 
RHEL6.5Snap1(RHEL6.5-20130925.2)
spice-server-0.12.4-3.el6.x86_64
qemu-kvm-0.12.1.2-2.406.el6.x86_64
libvirt-0.10.2-27.el6.x86_64

Guest:
RHEL6.5Snap1(RHEL6.5-20130925.2)
spice-vdagent-0.14.0-2.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Transfer a large file from client to guest
2.
3.

Actual results:
Transfer is successfully but guest is unusable for 1min.

Expected results:
Transfer is successful and guest is usable during the transfer process.

Additional info:

Comment 2 RHEL Program Management 2013-10-14 01:41:53 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 3 Christophe Fergeau 2014-04-09 13:44:10 UTC
Just tried this with a 3GB file, and the VM was responsive. Transfer took 10+ minutes but was successful (md5sum matches). This was over a LAN. Could it be that the file transfer saturated the link between client and host? Are you still seeing this issue?

Comment 4 David Blechter 2014-06-13 14:57:06 UTC
close based on Comment #3

Comment 5 Red Hat Bugzilla 2023-09-14 01:51:51 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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