Red Hat Bugzilla – Bug 1011645
Can not copy file from client to guest with vdagent-win-3.3-1.
Last modified: 2015-09-22 09:10 EDT
Description of problem:
I installed a Windows XP and Windows 7x86 VM on RHEL 6.5 and installed rhev-guest-tools-iso-3.3-5.noarch.rpm on both VMs.
I then copied the vdagent_x86.zip files from vdagent-win-3.3-1 located https://brewweb.devel.redhat.com/buildinfo?buildID=280963 onto both VMs to replace the existing files and then restarted the RHEV Spice Agent service.
I could not copy & paste or drag & drop any files from guest to client or client to guest after I restarted the service or restarting the VM.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Thanks for the bug report. We will need some extra info to futher debug this.
Please note that file drag and drop is only supported from client to guest, and only 1 file at a time (for now). In order for this to work you need the latest vdagent in the guest, as well as the latest remote-viewer + spice-gtk on the client side.
Are you using a windows or a linux client to view the vm?
Can you please try again using a fully up2date RHEL-6.5 as client, then open a nautilus window, select a file there and drag it from the nautilus window to the remote-viewer window.
Then the file should show up on your desktop in the windows machine (if I remember the location where it gets saved correctly for windows).
I looked at https://bugzilla.redhat.com/show_bug.cgi?id=956146 and the "Fixed in version" is vdagent-win-3.3-1. I have that installed. There is no mention of what version of remote-viewer + spice-gtk that I should use. There is also no mention of using Nautilus as the client start point of where to get files from. I would also suggest that we would need to document the minimal versions and the fact that Nautilus is needed as the place to take files from.
If I could get the minimal versions of packages I should be using, I will build the environment and test it a.s.a.p.
Closing as duplicate of original RFE bug as that is re-opened and it will contain information about how this is going to be fixed.
*** This bug has been marked as a duplicate of bug 956146 ***