copyto issue

[kjonca]

Can anyone confirm having working "copyto" on Virtualbox 5.1.18 ?

Code: Select all

VBoxManage guestcontrol fluor copyto --verbose --username kjonca --password x --target-directory c:/xxx.txt ~/tmp/tmp.LGPhE58TPI                                  
Creating guest session as user 'kjonca'...
Waiting for guest session to start...
Successfully started guest session (ID 1)
Copying from host to guest ...
Directory "c:" already exists
Source: /home/kjonca/tmp/tmp.LGPhE58TPI
Copying "/home/kjonca/tmp/tmp.LGPhE58TPI" to "c:/xxx.txt" ...
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: The specified file was not found on guest.
VBoxManage: error: Error processing "/home/kjonca/tmp/tmp.LGPhE58TPI", rc=VERR_GENERAL_FAILURE
Closing guest session ...

Guest is a xp machine with guest addition 5.1.18 installed

[socratis]

What's your host?
Follow a "start from cold-boot"/"observe error"/"shutdown" cycle. With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log". Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

Also, if you're coming from a ticket (like you are now) it's better if you reference that ticket, so that others can see that this bug was originally opened in 5.0.0 (20 months ago), fixed and reopened in 5.0.18 and re-fixed in 5.0.20 (11 months ago), reopened with 5.1.2 (7 months ago) and verified as semi-fixed by you (7 months ago), and finally re-"opened" 5 hours ago.

Ticket #14336.

[kjonca]

What's your host?

"Virtualbox on Linux Hosts"
More precisely:

Code: Select all

Linux bambus 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 (2016-11-13) x86_64 GNU/Linux

Follow a "start from cold-boot"/"observe error"/"shutdown" cycle. With the VM shut down completely (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log". Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

Added.

Also, if you're coming from a ticket (like you are now) it's better if you reference that ticket, so that others can see that this bug was originally opened in 5.0.0 (20 months ago), fixed and reopened in 5.0.18 and re-fixed in 5.0.20 (11 months ago), reopened with 5.1.2 (7 months ago) and verified as semi-fixed by you (7 months ago), and finally re-"opened" 5 hours ago.

And?

Ticket #14336.[/quote]