search

xxtbg / vboxweb

Automatically exported from code.google.com/p/vboxweb
MIT License
0 stars 0 forks source link

Cannot connect to VM #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. $ VBoxManage showvminfo Debian|grep VRDP
VRDP:            enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, 
ReuseSingleConn: off, Authentication type: null)

2. start vm from web console
3. $ VBoxManage showvminfo Debian|grep VRDP
VRDP:            disabled
VRDP Connection:    not active

$ ps ax |grep VBox
ilya     20793 30.9  0.8 149016 16920 pts/15   Rl+  01:35:00 00:03:58 python 
VBoxWebSrv.py
ilya     20801  0.0  0.1  10988  3396 pts/15   S+   01:35:01 00:00:00 
/usr/lib/virtualbox/VBoxXPCOMIPCD
ilya     20808  0.0  0.2  17556  6092 ?        Sl   01:35:01 00:00:00 
/usr/lib/virtualbox/VBoxSVC --pipe 4 --auto-shutdown
ilya     22361 29.8  5.0 131400 105864 ?       Sl   01:43:49 00:01:12 
/usr/lib/virtualbox/VBoxHeadless --comment Debian --startvm 
6b46cd33-dd44-4901-af9b-defa238ba35e --vrdp off
ilya     23078  0.0  0.0   3016   776 pts/14   R+   01:47:53 00:00:00 grep VBox

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Ubuntu 8.04
Virtualbox 3.1.0
Vboxweb from svn

Please provide any additional information below.

Original issue reported on code.google.com by kabus1...@gmail.com on 19 Dec 2009 at 10:55

GoogleCodeExporter commented 9 years ago 
The vboxheadless process is being started with the --vrdp off
 parameter - effectively disabling any remote console access.

I think this might be the same issue as Issue #37. A source code fix is listed 
there
that works for me.

Original comment by mrsbon...@yahoo.com on 6 Apr 2010 at 2:47

GoogleCodeExporter commented 9 years ago

Original comment by achim.ha...@gmail.com on 26 Aug 2010 at 2:18