Running Hortonworks 2.4 Sandbox on Hyper-V

I wanted to download the latest Sandbox of Hadoop 2.4 from Hortonworks, but the only available options were VMWare or Oracle.

I downloaded the Oracle VM Virtual Box version, and got it working, after adjusting the BIOS setting on local laptop.  Had to initiate a reboot and enable a setting.


But I really wanted to get it working on Windows 10 Hyper-V and there wasn't a download for that on the site.

So I found a webpage to convert to VHD file:


Open dos command prompt, navigate to the following directory (change accordingly!): cd C:\Users\jbloom\VirtualBox VMs\Hortonworks Sandbox with HDP 2.4

run the command: "C:\Program Files\Oracle\VirtualBox\VBoxManage" clonehd "Hortonworks Sandbox with HDP 2.4-disk1.vmdk" HDP2.4.vhd --format vhd

From there, found this site: http://www.eightforums.com/virtualization/41195-how-import-vhd-file-into-hyper-v.html

They instruct to create a VM not connected to anything, other than a Network Switch, which you can create.

It created the Virtual Hard Drive:

And a Virtual Machine:

Then Copied the .VHD file into the folder listed above:

Went into Microsoft Hyper-V Virtual Machine newly created, went to hard drive, re-pointed to the .VHD file, and started the VM, then attempted to Connect:


Error, error...

Going into the Network and Sharing Center, we see an existing Switch already created for Oracle, with same IP address:

So let's go ahead and change the Oracle one to a different IP Address (from .1 to .2)...

Then disabled and set the Hyper-V to

Stop and re-start the VM:

 There was still a connectivity issue warning, however, was able to log into the Linux VM using Username & Password:

Decided to create a network bridge between the VM adapter and the Network Adapter:

An IPConfig indicates that the IP Address changed:

Modified the Network adapter checking the box "Enable virtual LAN identification":

Restarted VM, connection successful!!!

Once logged into the VM, 'ifconfig' to get the ip address:

Connect from Laptop (not VM):

So it looks like it's working.  One thing to note, although I originally connected to the VM via Oracle, changed the password there, when it got imported to Hyper-V, it remembered the new password.  Interesting.

And there you have it~!