At the risk of having too much box in one title, here’s a 5min hi-def screencast that walks you through the steps involved in making a JumpBox work on Sun’s virtualization product  VirtualBox.  This is a great win because it provides a free and open source solution for running JumpBoxes on an Intel Mac. The big disclaimer here is:

This is not an officially-supported virtualization technology of JumpBox at this time.

It will typically work (with occasional flakiness in grabbing an IP) but there are a few issues blocking our ability to officially support it.  We have it on good authority that these will be resolved in a future version so stay tuned for declaration of official support.  Here’s the tutorial: *Note: click the  button in the lower-right of the player for a fullscreen hi-res version.


Setup is a fairly intuitive process with a few caveats to watch for. Namely these are:

  1. If you’re hosting multiple JumpBoxes on the same machine you’ll have a list of disk images that all share the same name. The only way to tell which one to use when attaching disks to the VM is by hovering over the dropdown and looking at the path that appears in the tooltip. 2. Make sure you add the disks before you start configuring the VM.  The last step of configuration is to attach the disks and it presumes you’ve already added them via the Media Manager.3. If you’re on an Intel Mac you’ll want to enable the VTX instructions for faster performance. Failing to do so will mean it runs about 8x slower than it should.4. If you want to run it in bridged ethernet mode you have to remember to explicitly tell it the network interface to use (Parallels and Fusion silently do this for you behind the scenes).5. You need to remember to add all the hard disks.  Typically JumpBoxes use two- root.vmdk and data.vmdk though some like Knowledge Tree will use three disks.  All must be added.6. Most apps will require only 256MB of RAM so it’s generally a good idea to pick this setting as the default. Some of the Java-based application JumpBoxes (typically the bigger filesize ones) will require 528 or even 1GB of RAM.  You can always change this setting after the fact so picking 256 to start is generally the preferred approach.

Tell us what you think in the comments and let us know if you run into any issues in getting it to work on your system.