title: how to install Android virtual appliances (ova files) downloaded from Genymotion into VirtualBox on another machine that is not running Genymotion
body: <p>In theory, it should just work.</p>
  
  <ul>
  <li>Copy from machine #1: <code>%LOCALAPPDATA%\Genymobile\Genymotion\ova\xxx.ova</code></li>
  <li>Install into VirtualBox on machine #2: <code>File -&gt; Import Appliance..</code></li>
  <li>Change the Network settings:
  
  <ul>
  <li>Update "Adapter 1" => <code>Bridged, Intel PRO/1000 MT Desktop</code></li>
  <li>Disable "Adapter 2"</li>
  </ul></li>
  <li>start..</li>
  </ul>
  
  <p>In practice:</p>
  
  <ul>
  <li>early versions of Android do work, but anything more recent than KitKat just hangs at boot up</li>
  <li>some of the versions that hang appear to be running an init.d script that results in a loop that repeatedly creates and kills a new process</li>
  </ul>
  
  <p>Does anybody have any idea how to make these Android .ova virtual appliances run in VirtualBox completely standalone from any installation of Genymotion?</p>
  
  <p>To add context, my development environment is already inside a VirtualBox guest OS. To run Genymotion would require that I run VirtualBox from inside VirtualBox, which is (a) a bad idea and (b) won't work. If I could run the Android images from the VirualBox on my host, then I could easily use <code>adb connect &lt;IP of virtualized Android device&gt;:5555</code> from within my development environment to connect to the virtualized Android device and test/deploy native apps. I don't care at all about having Genymotion installed; I only want to be able to pick-and-choose from their wide selection of Android device images.</p>
  
  <p>Help?</p>
  
  <p><strong>Update</strong>:</p>
  
  <p>Here's a screenshot that shows the hanging boot screen while loading the image: <code>Custom Phone - 6.0.0 - API 23 - 768x1280</code></p>
  
  <p><a href="http://i.stack.imgur.com/nTs2a.png" rel="nofollow">screenshot.png</a></p>