« HoneyDrive 3 Royal Jelly edition

Getting started with honeyd »

Aug 02 2014

HoneyDrive 3 VMware guide

I’ve recently become a happy owner of VMware Fusion and my first goal was to see how can HoneyDrive be imported to it and used with the same features as those of VirtualBox (which I mainly use to develop HoneyDrive in the first place). The first step I took was to build a virtual environment and host a live website within the Linux kernel that was created.

So, here is a step by step guide for converting the HoneyDrive 3 OVA file to a VMware-compatible virtual machine. I am using OS X Mavericks, VMware Fusion 6.0.4, OVF Tool 3.5.2 and VMware Tools 9.6.2.

The procedure should be the same for all the other VMware products as well (Workstation, ESXi, etc).

Instructions:

  1. Download OVF Tool 3.5.2 (needs a free account registration) from: https://my.vmware.com/web/vmware/details?downloadGroup=OVFTOOL352&productId=352
  2. Convert HoneyDrive OVA to VMX:
    $ cd /Applications/VMware\ OVF\ Tool/
    $ ./ovftool --lax -st=ova ~/HoneyDrive_3_Royal_Jelly.ova ~/HoneyDrive_3_Royal_Jelly.vmx
    Opening OVA source: /Users//HoneyDrive_3_Royal_Jelly.ova
    Opening VMX target: /Users//HoneyDrive_3_Royal_Jelly.vmx
    Warning:
    - Line 386: Unsupported hardware family 'virtualbox-2.2'.
    - Line 427: OVF hardware element 'ResourceType' with instance ID '5': No support for the virtual hardware device type '20'.
    - Line 444: OVF hardware element 'ResourceType' with instance ID '7': No support for the virtual hardware device type '35'.
    Writing VMX file: /Users//HoneyDrive_3_Royal_Jelly.vmx
    Progress: XX%
    

    This might take 5-15 minutes depending on your machine. After a while you will see:

    Transfer Completed
    Warning:
    - No manifest entry found for: 'HoneyDrive_3_Royal_Jelly-disk1.vmdk'.
    - No manifest file found.
    Completed successfully
    
  3. These two new files should have been created: HoneyDrive_3_Royal_Jelly-disk1.vmdk (around 9.5 GB) and HoneyDrive_3_Royal_Jelly.vmx. Import/open the new virtual machine by double clicking the .vmx file. You might see an error message in VMware Fusion saying: “Cannot connect the virtual device ide1:0 because no corresponding device is available on the host. Do you want to to try to connect this virtual device every time you power on the virtual machine?” Press “No” and it won’t be shown again.
  4. Inside the HoneyDrive virtual machine, open Terminator (on the desktop) and type the following to uninstall the VirtualBox Guest Additions:
    $ sudo aptitude purge -P virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
    $ sudo reboot
    
  5. Once HoneyDrive is running again, click on “Virtual Machine” -> “Install VMware Tools” from the menu. This will mount a virtual disk with VMware Tools. Open Terminator again and type:
    $ cp /media/VMware\ Tools/VMwareTools-<version>.tar.gz ~/
    $ tar zxvf VMwareTools-<version>.tar.gz
    $ cd vmware-tools-distrib
    $ sudo ./vmware-install.pl -d
    $ sudo reboot
    

That’s it, enjoy HoneyDrive in VMware!

  • Pingback: Security-Vision » HoneyDrive 3 VMware guide()

  • Pingback: Setup HoneyDrive on VMware (Workstation, ESXi, etc) - BruteForce Lab's Blog()

  • Pingback: HoneyDrive | Bountolos.info()

  • Matt Peterschlingmann

    Didn’t work for me under ESXi(5.1). I had to hack on the ovf manually, change SCSI references to IDE, remove Sound Card & cd-rom
    .

    • http://bruteforce.gr/ Ion

      Hi Matt, thanks for letting us know!

      I don’t own ESXi unfortunately. Is there a possibility for you to go over the procedure again, documenting the steps? (a final version of the edited file could also help a lot). I can then add it to the site specifically for ESXi.

      Thanks,
      Ion

      • Matt Peterschlingmann

        I will track down the OVF / steps on next build.

        Could you try a release by exporting the OVF from VMware fusion? This may be better for the ESXi users.

  • Brent

    First, Thanks for pulling this together. I ended up doing a two step migration.. First an OVA->VMX to clean up the problems and then VMX->OVA for deployment. Deployed through vCenter without any problem. Probably would have been faster to just edit the file, though.

  • turducken

    This process does not work, unfortunately. Tried using ovftool on both OSX and Windows (32 and 64) with no luck. It gets to the “Line 386: Unsupported hardware family ‘virtualbox-2.2′.” error then states it compiled with errors and ends processing. In reality this process does not finish and no file is exported… Anyone else run into this problem?

    • http://bruteforce.gr/ Ion

      Hi, perhaps you’re using a newer version of the software/tools? I don’t know if it’s possible, but if you can find the specific versions I used it might work (worked for me fine in OSX). Then save the exported files and upgrade to your desired versions again.

Powered by WordPress and the Graphene Theme.

More in Blog News, Honeypots, Virtualization
HoneyDrive 3 Royal Jelly edition
Vagrant configuration for Thug honeyclient
Kippo-Graph 1.2: pull master or re-download
Kippo-Graph 1.2 released!
Honeypots workshop at BSidesLV 2014!
Close