Opened 10 years ago
Closed 9 years ago
#14408 closed defect (fixed)
VBoxManage raises Error getting stdout handle: VERR_NOT_IMPLEMENTED when piping
Reported by: | tmassarini | Owned by: | |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 5.0.0 |
Keywords: | guest control VERR_NOT_IMPLEMENTED | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
When running the following command I get the following error:
Command: VBoxManage guestcontrol vm_name run --exe /bin/ls --timeout 10000 --verbose --wait-stdout -- | grep -i 'home'
Error: VBoxManage: warning: Error getting stdout handle: VERR_NOT_IMPLEMENTED
When not piping everything seems to work fine. I can also redirect output to a file.
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Here's some sample output:
Macbook$ VBoxManage --version 5.0.2r102096 Macbook$ VBoxManage guestcontrol 3c23fa24-a33d-4d27-a899-63ee2c89bf91 run --username developer --password P@SsW0rD --exe /bin/ls --timeout 10000 --verbose --wait-stdout -- bin boot dev etc home lib lib64 lost+found media mnt opt proc root sbin selinux srv sys tmp u01 usr var Macbook$ VBoxManage guestcontrol 3c23fa24-a33d-4d27-a899-63ee2c89bf91 run --username developer --password P@SsW0rD --exe /bin/ls --timeout 10000 --verbose --wait-stdout -- | grep -i 'home' VBoxManage: warning: Error getting stdout handle: VERR_NOT_IMPLEMENTED Macbook$ VBoxManage guestcontrol 3c23fa24-a33d-4d27-a899-63ee2c89bf91 run --username developer --password P@SsW0rD --exe /bin/ls --timeout 10000 --verbose --wait-stdout -- > out Macbook$ cat out bin boot dev etc home lib lib64 lost+found media mnt opt proc root sbin selinux srv sys tmp u01 usr var Macbook$
comment:3 by , 10 years ago
Same applies to standard error.
Workaround (for some cases) is to send stdout to a file and stderr to another file.
comment:4 by , 10 years ago
The issue should be fixed with VirtualBox 5.0.4. Does this work for you now?
comment:5 by , 10 years ago
No, not fixed with VirtualBox 5.0.4 on OS X 10.10.4. For me, it only happens when I run VBoxManage from a Python or Haskell program. When I run it from the terminal, it works fine.
comment:6 by , 10 years ago
declassified, are you sure that you are using the 5.0.4 Guest Additions?
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Same here. Can reproduce on VirtualBox 5.0.0 and 5.0.2 on OS X 10.10.5.