Custom Query (16363 matches)
Results (2113 - 2115 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10437 | obsolete | Running shell script on guest cause <defunct> process | ||
| Description |
When run shell script on the guest Linux using the following command will cause the shell process to crash into <defunct> state: VBoxManage.exe guestcontrol Debian exec --username root --password xxx --verbose --wait-stdout --image "/bin/sh" -- -c "export" Problem is experienced with both Guest Addition 4.1.10 & 4.1.12. Downgrading Guest Addition to 4.1.8 will fix the issue. Running VBoxService manually will generate the following logs: root@Debian:~#VBoxService -f -v VBoxService 4.1.12 r77245 (verbosity: 1) linux.x86 (Apr 3 2012 14:40:20) release log 00:00:00.001 main Log opened 2012-04-13T20:29:59.509047000Z 00:00:00.002 main OS Product: Linux 00:00:00.002 main OS Release: 2.6.32-5-686 00:00:00.002 main OS Version: #1 SMP Mon Jan 16 16:04:25 UTC 2012 00:00:00.002 main OS Service Pack: #1 SMP Mon Jan 16 16:04:25 UTC 2012 00:00:00.002 main Executable: /opt/VBoxGuestAdditions-4.1.12/sbin/VBoxService 00:00:00.002 main Process ID: 8537 00:00:00.002 main Package type: LINUX_32BITS_GENERIC 00:00:00.014 main 4.1.12 r77245 started. Verbose level = 1 00:00:00.025 timesync VBoxServiceTimeSyncAdjust: adjtime by 551 305 000 ns 00:00:00.040 main All services started. 00:00:07.628 gctl1 Error: IPC request is invalid Process list: UID PID PPID C STIME TTY TIME CMD root 8554 2060 0 16:31 pts/0 00:00:00 VBoxService -f -v root 8565 8554 0 16:31 pts/0 00:00:00 [sh] <defunct> |
|||
| #10439 | obsolete | Keyboard doesn't work in NetOp Remote Control OS/2-eCS clients | ||
| Description |
Keyboard doesn't work in virtual OS/2-eCS clients remotely controlled through NetOp Remote Control. Since NetOp Remote Control is probably the only available remote control solution for OS/2 and eCS hosts, it should get a high priority to get this fixed. I REALLY need a remote control for virtual OS/2 clients and all other solutions have serious bugs (mostly mouse issues). I'm not sure if they still have OS/2 Host code (installed on the controlled host) available (I have it from the old days when I was an OS/2 engineer for a major financial company) and there is no more OS/2 Guest (installed on controlling host) available, so Windows Guest needs to be used for remote control. I can provide the OS/2 Host code for testing and the Windows serial numbers should work for it, or I can provide that too. BTW, these lines from VBox.log are wrong: 00:00:05.397 File system of 'D:\VirtualBox\RRSOAS01VM\RRSOAS01VM_1.vdi' is ntfs 00:00:05.400 File system of 'D:\VirtualBox\RRSOAS01VM\RRSOAS01VM_2.vdi' is ntfs The file system if JFS, not NTFS. |
|||
| #10440 | obsolete | Mouse unsuable in Remote Display for virtual OS/2-eCS clients | ||
| Description |
When I connect through RDP to Remote Display port on virtual OS/2-eCS clients the mouse is practically unusable. There are 2 mouse cursors, remote and local. The remote cursor hardly follows the local mouse cursor. It usually moves MUCH slower than local cursor, so the distance between them grows quickly and remote cursor sometimes jumps around. |
|||

