Ticket #6676 (new defect)
VirtualBox GUI hangs with x0vncserver running on CentOS 5
|Reported by:||commorancy||Owned by:|
|Version:||VirtualBox 3.1.8||Keywords:||hang hangs interference|
When I set up a session to automatically run x0vncserver on the CentOS 5 desktop, the VirtualBox GUI doesn't work properly. While x0vncserver is running, VirtualBox is extremely slow to start up and the GUI vacillates between responding and not responding (mostly not responding) so as to be unusable. If I kill x0vncserver, this behavior disappears. No other X GUI applications that I have found behave in this way. Because I need remote access to the console to operate the VirtualBox GUI, I need to have x0vncserver running to manage VirtualBox. Unfortunately, because they interfere with one another, this appears to be a one or the other situation right now and that makes VirtualBox unusable in this scenario.
Because this doesn't deal with running guests, the VBox.log file is not applicable to this bug report. If there is another log that deals with the GUI and its functionality, I'll be happy to attach that log file here.
As a feature request, instead of using VNC to control the console, I'd rather have the VBox GUI become a remote manager. Meaning, I would like to be able to use a single copy of the GUI installed on Windows to administer multiple remote installations of VirtualBox using a login and password. I'm really surprised that VBox doesn't offer this feature yet. If it does and I'm missing it, please let me know that too (and how to enable and use it).