Closed GoogleCodeExporter closed 8 years ago
Hi,
I have the same problem -> I can't see any VM!
virtualbox 3.2.6 + latest vboxweb running on ubuntu 10.4 32bits!
It is a general problem? Should I take an older version of virtualbox?
Original comment by bsan...@gmail.com
on 5 Jul 2010 at 7:08
Could it be that you are using the open source edition of virtualbox?
This version does not support RDP, so the web service code fails before
anything can be displayed.
Looking into the code, what fails is creating the internal "jsMachine" object
for display. The problem is in "jsVRDPServer". However, while I could hack
around this for a quick test, I would not recommend it in general.
Original comment by jb.d...@gmail.com
on 7 Jul 2010 at 12:36
no I'm not using open source edition.
I'm going to see into the code.
Original comment by nicolas....@gmail.com
on 7 Jul 2010 at 7:28
I'm running VirtualBox 3.2.4 (PUEL edition) on Opensolaris build 134, and have
installed version 98 of vboxweb. I'm able to log into vbox web, but I cannot
see any of my VM's. I've attached a screenshot of what this looks like in
Firefox 3.6.3 on Mac OS X 10.5.6.
Original comment by andrew.c...@gmail.com
on 12 Jul 2010 at 1:09
Attachments:
I found exact the same problem and realize that the Chrome browser having
problem (or may be I haven't installed a plugins required) The Firefox 3.6.6
shows the machine list and state correctly, but I cannot control the VMs nor
connect the console of running VM on vboxweb interface. The following is my
environment.
The VirtualBox version 3.2.0r61806 running on a 32 bit Ubuntu 10.04 for the
server. The exact same distribution for the laptop client with Firefox 3.6.6
and Chrome 5.0.375.99
Original comment by thama...@gmail.com
on 13 Jul 2010 at 3:31
i want to test if this behaviour belongs to the version of VB. i tried to
install 3.0 on ubuntu 10.04 x64 but had no luck so far with apt-get.
Original comment by werty...@gmail.com
on 13 Jul 2010 at 12:23
Original comment by achim.ha...@gmail.com
on 26 Aug 2010 at 2:18
Original issue reported on code.google.com by
nicolas....@gmail.com
on 5 Jul 2010 at 9:46