Virtual Desktop messes up Virtualbox

  • Thread starter Thread starter Warlord711
  • Start date Start date
W

Warlord711

After trying 2xVirtualDesktop in combination with Virtualbox, i am no more able to start any VM with a visable Window.

Virtualbox now starts every machine without a window. Even after deinstalling 2x, it still occurs.

I can still call the machines in this way: C:\PROGRA~1\Oracle\VIRTUA~1\VirtualBox.exe --comment Standard_PC_Büro --startvm d91eca52-595c-42fc-9e70-49f934136ebc

But from within Virtualbox, i cant.
 
Not sure what the version has to do with the problem 2x causes, but its Virtualbox 3.2.4.

I just want to know, at what point does 2X alter Virtualbox Settings and in which kind. Since the moment I configure 2X to use Virtualbox, Virtualbox stopped working the way it should. There is no more window if i start a machine from withing Virtualbox.

On a timeline it looked like this (maybe that shows clear what the problem is)



<morning>--------<vbox runs as intended>--------<install of 2X and configure to use vbox>--------<vbox runs without showing any window for VMs>------<deinstalling 2X and delete of any file, also installer>---------<vbox runs without showing any window for VMs>------<deinstalling and reinstalling VBox, also trying to remove any files left in directory>--------<vbox runs without showing any window for VMs>----------<evening>
 
Try disabling the vdi agent before uninstalling the 2x VDS.
See if that helps.
 
If you install VDS it automatically installs VDI agent.

from cmd run
Code: 
c:/>tasklist /svc

You should see an entry like this :

Code: 
2XVDSAgent.exe     3364 2X VDI Agent.

In your farm ( if you removed VDS try re-installing it )
Click the enable check under the farm -> VDI Hosts section near your local machine.
Click apply.

If it was disabled try enablilng --> apply disable --> apply to cycle the scripts.

See if this helps you.

I have the setup here and vbox does not appear to behave like yours.

Anyway I am running 3.0.8 64 bit your version has not been tested yet.

Vbox scripting is quite dynamic and they change quite some behaviors across versions.

Go for a supported version.


Hope this helps.
 
You must log in or register to reply here.
Back
Top