Opened 13 years ago
Closed 8 years ago
#9505 closed defect (obsolete)
IGuest::copyToGuest method doesn't work properly on VB 4.1.2
| Reported by: | man-in | Owned by: | |
|---|---|---|---|
| Component: | guest control | Version: | VirtualBox 4.1.2 |
| Keywords: | copyToGuest, copy, IGuest | Cc: | |
| Guest type: | other | Host type: | Windows |
Description (last modified by )
Hello We've experienced problems while using IGuest::copyToGuest method with python v.2.7 When calling it from system with VirtualBox 4.1.2 & VB Additions 4.1.2 on Windows (tried XP,2k8r2) guest, - the resulting file is maximum 64KB in size and no any exceptions raised. Files under 64KB in size copied from host correctly.
The SAME python code works properly with VirtualBox 4.1.0 & VB Additions 4.1.0 installed, copying files larger than 64KB correctly
though, set with VirtualBox 4.1.2 & VB Additions 4.1.0 not works either
Attachments (6)
Change History (11)
by , 13 years ago
by , 13 years ago
| Attachment: | VBox.2.log added |
|---|
by , 13 years ago
| Attachment: | VBox.3.log added |
|---|
by , 13 years ago
| Attachment: | VBox.4.log added |
|---|
by , 13 years ago
| Attachment: | VBox.5.log added |
|---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Experiencing the same with VBoxManage guestcontrol copyto. Fedora 15 host, Windows XP guest
Failure seems to be in the vbox_cat guest process.
comment:3 by , 13 years ago
I have this error while copying files via vboxmanage guestcontrol copyto on Win7 hosts, WinXP guests:
0%... Progress state: VBOX_E_IPRT_ERROR VBoxManage.exe: error: Client error 2281748126 while processing input data. VBoxManage.exe: error: Error processing "D:\test.txt", rc=VERR_GENERAL_FAILURE
If file has less than 64 kb data it copies correctly. Please fix this issue as soon as possible.
comment:4 by , 12 years ago
| Component: | guest additions → guest control |
|---|---|
| Description: | modified (diff) |
comment:5 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
please see VBox.5.log