Service Virtualization

Tech Tips: DEVTEST - Resolve extra VBOXMANAGE Processes from Starting 

06-14-2016 01:40 PM

This article explains how to prevent extra "/bin/bash -i -c which VBoxManage”  processes from spawning when the Simulator is started

 

Issue:

Extra "/bin/bash -i -c which VBoxManage" processes being started

 

Environment: 

All supported DevTest Windows, UNIX and Linux platforms

 

Cause:

The Simulator is spawning off extra VBoxManage processes when the Simulator is started regardless if you are doing Mobile testing or not.

 

Resolution:

  1. 1. Stop your Simulator (or reboot and don’t start it to begin with)


2. You will have to kill all of the $VBoxManage processes (More than One?)


3. Update the local.properties file and add this property:


VBOXMANAGE_CMD=" "


4. Start the Simulator.


5. Verify no extra VBoxManage processes start.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

02-28-2017 03:58 PM

I need to find out how to remove any of those processes from starting.

02-28-2017 02:31 PM

Extra processes are indeed removed.

However, the initial process remains

    PID USER   PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND 
   5939 lisa      20   0  105m 1248 1068 R    100.0     0.0    40:36.59   /bin/bash -i -c which VBoxManage   <<<<

Looks like there is  a basic assumption that mobile is involved even when it's not?

Would be OK were it not for taking up a whole CPU to itself.

 

Interestingly enough the same process can show up as:

  PID USER   PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+    COMMAND                              
 5939 lisa      20   0  105m 1248 1068    R 100.0     0.0       49:07.27   bash          <<<<<                        
 7038 lisa      20   0 7231m 1.8g  53m    S  0.7        11.3     100:22.91  java                                  
14048 lisa      20   0 5464m 272m  31m S  0.3          1.7      0:12.87     java                

 

 

in a different window :-(                  

Related Entries and Links

No Related Resource entered.