NKXLAB / phpvirtualbox

Automatically exported from code.google.com/p/phpvirtualbox
Other
1 stars 0 forks source link

Console connect button is grayed out/disabled. #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Just run phpvirtualbox
2.
3.

What is the expected output? 

I guess the ability to connect to console :)

What do you see instead?

Console button is disabled/grayed out.

What version of phpVirtualBox, VirtualBox, and PHP are you using? On what
operating system?

PHPVirtualBox - 4.1
Virtualbox - 4.0
PHP -5.2
OS - Solaris 11

Please provide any additional information below.

tried different browsers,same issue.

GREAT PROJECT !!! GOOD LUCK AND KEEP UP EXCELLENT WORK !!!

Original issue reported on code.google.com by fory...@gmail.com on 11 Jan 2011 at 3:56

GoogleCodeExporter commented 9 years ago
To enable screen shots and the Console tab, please install a VirtualBox 
extension pack that supports VRDE such as the Oracle VM VirtualBox Extension 
Pack found in the Downloads section of http://www.virtualbox.org

Original comment by imooreya...@gmail.com on 11 Jan 2011 at 2:19

GoogleCodeExporter commented 9 years ago
How install VirtualBox extension pack with commandline ?!

Original comment by obookl...@gmail.com on 15 Jan 2011 at 5:15

GoogleCodeExporter commented 9 years ago
VBoxManage extpack          install <tarball> |
                            uninstall [--force] <name> |
                            cleanup

Original comment by phiphi.g...@gmail.com on 15 Jan 2011 at 5:48

GoogleCodeExporter commented 9 years ago
Hello,

I have a problem equivalent console in gray.
I have the variables:

/ / Default host / ip to use for console
var $ consoleHost = '127 .0.0.1 ';
var $ rdphost = '127 .0.0.1 ';

and install extension pack:

vboxmanage extpack install 
Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack 

Thank you for your help.

Regards,

fred

Original comment by frederic...@gmail.com on 16 Jan 2011 at 1:34

GoogleCodeExporter commented 9 years ago
screen

Original comment by frederic...@gmail.com on 16 Jan 2011 at 1:34

Attachments:

GoogleCodeExporter commented 9 years ago
Fred - in phpVirtualBox, highlight the VM and click on Machine (at the top 
menu) then on Refresh. Let me know if this doesn't resolve it.

Original comment by imooreya...@gmail.com on 17 Jan 2011 at 12:47

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Please see http://code.google.com/p/phpvirtualbox/issues/detail?id=134#c8

Original comment by nerij...@gmail.com on 20 Jan 2011 at 1:23

GoogleCodeExporter commented 9 years ago
I'm guessing that fixed it.

Original comment by imooreya...@gmail.com on 27 Jan 2011 at 2:02

GoogleCodeExporter commented 9 years ago
It is grey even for me and "ighlight the VM and click on Machine (at the top 
menu) then on Refresh." does not work out :-(

Original comment by iso...@gmail.com on 16 Aug 2011 at 1:10

GoogleCodeExporter commented 9 years ago
I saw that my VM is starting in Headless mode, How to start it in GUI mode ?

Original comment by iso...@gmail.com on 16 Aug 2011 at 2:24

GoogleCodeExporter commented 9 years ago
Here is the screen shot for the same,  How to start the VM in GUI mode ?

Original comment by iso...@gmail.com on 16 Aug 2011 at 3:22

Attachments:

GoogleCodeExporter commented 9 years ago
I've had this problem today from an imported VM from OVF. Running:

VBoxManage modifyvm <name> --vrdeport 3389-4000
VBoxManage modifyvm <name> --vrde on
VBoxManage controlvm <name> vrde on

solved it.

Original comment by jum.reyn...@gmail.com on 18 Aug 2011 at 8:27

GoogleCodeExporter commented 9 years ago
My Console disabled problem is still not resolved :-(

Original comment by bala150...@gmail.com on 24 Aug 2011 at 7:05

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Follow this and the console will get fixed.

Set up var console as per the link below
http://code.google.com/p/phpvirtualbox/issues/detail?id=134#c8

Check if the extensions are properly installed as per the link below
http://forums.virtualbox.org/viewtopic.php?f=1&t=38530

Original comment by bala150...@gmail.com on 27 Aug 2011 at 7:56

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
>su vbox
>VBoxManage modifyvm <myvms> --vrdeport 9000-9100
(from config.php)
>VBoxManage modifyvm <myvms> --vrde on

It's help me. Thanks all!

Original comment by sdm1r...@gmail.com on 23 Nov 2012 at 5:55

GoogleCodeExporter commented 9 years ago
Thanks. solution #14 above solved it for me.

(this was a vbox that was created/initialized via 'Vagrant', 
http://vagrantup.com/v1/docs/getting-started/index.html 
 - it may have done things differently

Original comment by d...@sparksinteractive.co.nz on 24 Nov 2012 at 6:04

GoogleCodeExporter commented 9 years ago
How about installing the extension pack as non-root?  No dice here. I have 
vboxwebsrv running as vbox.

sudo -u vbox -i VBoxManage extpack install 
Oracle_VM_VirtualBox_Extension_Pack-4.3.6-91406.vbox-extpack 
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install 
"/home/vbox/Oracle_VM_VirtualBox_Extension_Pack-4.3.6-91406.vbox-extpack"
VBoxManage: error: Extension pack 'Oracle VM VirtualBox Extension Pack' is 
already installed. In case of a reinstallation, please uninstall it first
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
ExtPackManager, interface IExtPackManager
VBoxManage: error: Context: "int handleExtPack(HandlerArg*)" at line 1143 of 
file VBoxManageMisc.cpp

Original comment by gmag...@gmail.com on 17 Feb 2014 at 6:42

GoogleCodeExporter commented 9 years ago
Try use this one after installation of VirtualBox:

sudo /etc/init.d/vboxdrv setup

This will start a second attempt to build the module. If a suitable kernel 
module was found in the package or the module was successfully built, the 
installation script will attempt to load that module, and then the console 
should work :-)

Original comment by ary...@gmail.com on 23 Feb 2014 at 6:25