Follow

Migrating Visible Thread from VMware to Hyper-V

Here is how to move the VisibleThread virtual machine to Microsoft Hyper-V.

Estimated Time: 40M - 1Hour

http://www.starwindsoftware.com/converter

Steps to Migrate Visible Thread(VT) to Microsoft Hyper-V

  • Download and Install: Starwind V2V Converter
    • Know the location of the Virtual Appliance's VMDK file. If you have just downloaded the VisibleThread zip file, extract it to find the VMDK file.
  • Convert Virtual Appliance VMDK file to VHD
    • In the Starwind V2V Converter - Click the Browse button and select your VT Vmware Disk(VMDK)
    • If asked to choose a destination image format, select 'Microsoft Virtual PC growable image'
    • Select the location to save your VHD file
    • Estimated time for VT 6-8GB took 40-50M using a Dell T5400 Precision Workstation with Xeon Processor, 8GB RAM, and SAS storage drives.
  • Using the Hyper-V manager (Start Menu-> Administrative Tools-> Hyper-V manager) 
    • Create a New Hyper-V Virtual Machine, select 'New->Virtual Machine' from the menu on the right side of the Hyper-V manager
    • Call the Virtual Machine 'VisibleThread Server', click 'Next'
    • Allocate 4096MB memory to the Virtual Machine, click 'Next'
    • Select to create a 'New Virtual Network' for the Virtual Machine and click 'Next'
    • Select option to use an Existing VHD and browse for the new VHD file
    • Select 'Standard Network Adapter'
    • Start the VM (Generates new MAC Address for VM), right click on the VM and select 'Start'
    • Connect to your new VM (right click on the VM and select 'Connect', then Click File > Settings
    • Notate the MAC address for the legacy network device for the next steps
  • Login to the VM and perform these steps
    • The default username is 'visiblethread' and the password is 'password'
    • type 'sudo rm /etc/udev/rules.d/70-persistent-net.rules'
    • type 'nano /etc/network/interfaces'
      • Replace MAC address with the new Hyper-V Mac Address on the line, “HWADDR”
      • type 'Ctrl-O' and return to write the changes to disk and 'Ctrl-X' to exit
    • Type 'sudo reboot'

6GB VMDK converted in 42M and 5s. Results will vary on the hardware used for the conversion process.

 

By default, the VisibleThread server is configured to pick up an IP address automatically from your network. To see what the ip configuration for the server is type the following at the command prompt, you should see something similar to what is displayed below:

> ifconfig

eth0     Link encap:Ethernet HWaddr 40:40:2d:ef:41:54

inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::4240:2dff:feef:4154/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:17632221 errors:0 dropped:0 overruns:0 frame:0

TX packets:14928547 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:8069857778 (8.0 GB) TX bytes:17026117038 (17.0 GB)

 

 

It may be useful to assign a static IP to the VisibleThread server. This way users can use a consistent address to connect to the VisibleThread server. To do so follow these steps:


Open the /etc/network/interfaces file using the pico editor:

sudo pico /etc/network/interfaces

 

  In this file you should see the following line:

iface eth0 inet dhcp

 

Replace the word ‘dhcp’ with the word ‘static’ and add the relevant information for your network settings (ipaddress, gateway etc..), for example:

iface eth0 inet static

address 192.168.1.11

netmask 255.255.255.0

network 192.168.1.0

broadcast 192.168.1.255

gateway 192.168.1.1

Save and close the /etc/network/interfaces file. To save the file type Ctrl-O i.e. control key and the letter o (which will prompt to save the file), then hit enter. Then to exit to the console type ctrl-x.

 Restart the networking service on the Virtual Appliance:

sudo reboot

 

Kind Regards,

Steve Kline - MCITP, RHCSA

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

4 Comments

  • 0
    Avatar
    Steve

    Also, your VM will lie to you when the Issue is populated at the login prompt.

    I manually edited the Issue prompt, saying the IP address was something else that it wasn't.

    sudo nano /etc/issue - you can change the login prompt message.

  • 0
    Avatar
    Fergal McGovern

    Thanks Steve for sharing.

    This is pretty useful stuff for any Microsoft customers looking to deploy the virtual appliance onsite.

    thanks, Fergal.

  • 0
    Avatar
    Gabriel Rios

    How do you configure to connect to a domain?

     

  • 0
    Avatar
    Eoin

    Hi Gabriel,

    I know my colleague Jason was in touch with you and worked through the issues you were having.

    If you have any other questions regarding the deployment, contact us at support@visiblethread.com

     

    Eoin

Article is closed for comments.