• Install Mikrotik On Vmware Workstation Software
• Install Vmware Workstation 12
• Install Vmware Workstation Player
• Buy Vmware Workstation

Warning: This manual is moved to https://help.mikrotik.com/docs/x/mgAYAQ

آموزش نصب میکروتیک در VMware Workstation - برای نصب ابتدا از سایت میکروتیک نسخه RouterOS مورد نظرتان را دانلود کنید و طبق تصاویر زیر اقدام به نصب کنید. Manual Chr Vmware Installation Mikrotik Wiki. Virtual management software that works with isolinux booter installer on chr image (kvm, virtualbox or vmware workstation, vmware fusion, hyper v these tools are interchangeable); tool to resize the image file prior the installation as default image is 64mb of size and in some cases, more storage is required (qemu img, vmware built in tool. Cara Install Mikrotik RouterOS di VMware Workstation By. Cara Instal Mikrotik di VMware Workstation 1. Buka VMware Workstation dan klik pada Create a New Virtual Machine 2. Pilih Custom (advanced) 3. Pada hardware compatibility, pilih versi VMware Workstation.

• 2System Requirements
• 3How to Install CHR
• 4CHR Licensing
  • 4.1Paid licenses
  • 4.2Free licenses
• 5Getting the License
• 7Troubleshooting
  • 7.1Running on VMware ESXi
  • 7.4Using vlans on CHR in various Hypervisors
• 8Guest tools
  • 8.1VMWare
    • 8.1.5Provisioning
  • 8.2Xen
  • 8.3KVM

Cloud Hosted Router

Cloud Hosted Router (CHR) is a RouterOS version intended for running as a virtual machine. It supports the x86 64-bit architecture and can be used on most of the popular hypervisors such as VMWare, Hyper-V, VirtualBox, KVM and others. CHR has full RouterOS features enabled by default but has a different licensing model than other RouterOS versions.

System Requirements

Minimal requirements:

• Package version: RouterOS v6.34 or newer
• Host CPU: 64-bit with virtualization support
• RAM: 128MB or more
• Disk: 128MB disk space for the CHR virtual hard drive (Max: 16GB)

Note: The minimum required RAM depends on interface count and CPU count. You can get an approximate number by using the following formula: RAM = 128 + [ 8 × (CPU_COUNT) × (INTERFACE_COUNT - 1) ]

CHR has been tested on the following platforms:

• VirtualBox 5 on Linux and OS X
• VMWare Fusion 7 and 8 on OS X
• VMWare ESXi 6.5
• Qemu 2.4.0.1 on Linux and OS X
• Hyper-V on Windows Server 2008r2, 2012 and Windows 10 (Only Generation 1 Hyper-V virtual machine is supported at the moment)
• Xen Project 4.6.5
• Xen Server 7.1

Warning: Hypervisors that provide paravirtualization are not supported.

Usable Network and Disk interfaces on various hypervisors:

• ESX:
  • Network: vmxnet3, E1000
  • Disk: IDE, VMware paravirtual SCSI, LSI Logic SAS, LSI Logic Parallel

• Hyper-V:
  • Network: Network adapter, Legacy Network adapter
  • Disk: IDE, SCSI

• Qemu/KVM:
  • Network: Virtio, E1000, vmxnet3 (optional)
  • Disk: IDE, Sata, Virtio

• Xen Project:
  • Network: E1000, rtl8193, netfront
  • Disk: IDE, Sata

• VirtualBox
  • Network: E1000, rtl8193
  • Disk: IDE, Sata, SCSI, SAS

Note: SCSI controller Hyper-V and ESX is usable just for secondary disks, system image must be used with IDE controller!

Warning: We do not recommend using E1000 network interface if better synthetic interface options are available on specific Hypervisor!

How to Install CHR

We provide 4 different virtual disk images to choose from. Note that they are only disk images, and you can't simply run them.

• RAW disk image (.img file)
• VMWare disk image (.vmdk file)
• Hyper-V disk image (.vhdx file)
• VirtualBox disk image (.vdi file)

Steps to install CHR

1. Download virtual disk image for your hypervisor
2. Create a guest virtual machine
3. Use previously downloaded image file as a virtual disk drive
4. Start the guest CHR virtual machine
5. Log in to your new CHR. Default user is 'admin', without password

Please note that running CHR systems can be cloned and copied, but the copy will be aware of the previous trial period, so you cannot extend your trial time by making a copy of your CHR. However, you are allowed to license both systems individually. To make a new trial system, you need to make a fresh installation and reconfigure RouterOS.

Installing CHR

• VMWare Fusion / Workstation and ESXi 6.5

CHR Licensing

The CHR has 4 license levels:

• free
• p1perpetual-1 ($45)
• p10perpetual-10 ($95)
• p-unlimitedperpetual-unlimited ($250)

60-day free trial license is available for all paid license levels. To get the free trial license, you have to have an account on MikroTik.com as all license management is done there.

Perpetual is a lifetime license (buy once, use forever). It is possible to transfer a perpetual license to another CHR instance.A running CHR instance will indicate the time when it has to access the account server to renew it's license. If the CHR instance will not be able to renew the license it will behave as if the trial period has ran out and will not allow an upgrade of RouterOS to a newer version.

After licensing a running trial system, you must manually run the /system license renew function from the CHR to make it active. Otherwise the system will not know you have licensed it in your account. If you do not do this before the system deadline time, the trial will end and you will have to do a complete fresh CHR installation, request a new trial and then license it with the license you had obtained.

License	Speed limit	Price
Free	1Mbit	FREE
P1	1Gbit	$45
P10	10Gbit	$95
P-Unlimited	Unlimited	$250

Paid licenses

p1

p1 (perpetual-1) license level allows CHR to run indefinitely. It is limited to 1Gbps upload per interface. All the rest of the features provided by CHR are available without restrictions. It is possible to upgrade p1 to p10 or p-unlimited After the upgrade is purchased the former license will become available for later use on your account.

p10

p10 (perpetual-10) license level allows CHR to run indefinitely. It is limited to 10Gbps upload per interface. All the rest of the features provided by CHR are available without restrictions. It is possible to upgrade p10 to p-unlimited After the upgrade is purchased the former license will become available for later use on your account.

p-unlimited

The p-unlimited (perpetual-unlimited) license level allows CHR to run indefinitely. It is the highest tier license and it has no enforced limitations.

Free licenses

There are several options to use and try CHR free of charge.

free

The free license level allows CHR to run indefinitely. It is limited to 1Mbps upload per interface. All the rest of the features provided by CHR are available without restrictions. To use this, all you have to do is download disk image file from our download page and create a virtual guest.

60-day trial

In addition to the limited Free installation, you can also test the increased speed of P1/P10/PU licenses with a 60 trial.

You will have to have an account registered on MikroTik.com. Then you can request the desired license level for trial from your router that will assign your router ID to your account and enable a purchase of the license from your account. All the paid license equivalents are available for trial. A trial period is 60 days from the day of acquisition, after this time passes, your license menu will start to show 'Limited upgrades', which means that RouterOS can no longer be upgraded.

If you plan to purchase the selected license, you must do it within 60 days of the trial end date. If your trial ends, and there are no purchases within 2 months after it ended, the device will no longer appear in your MikroTik account. You will have to make a new CHR installation to make a purchase within the required time frame.

To request a trial license, you must run the command '/system license renew' from the CHR device command line. You will be asked for the username and password of your mikrotik.com account.

Warning: If you plan to use multiple virtual systems of the same kind, it may be possible that the next machine has the same systemID as the original one. This can happen on certain cloud providers, such as Linode. To avoid this, after your first boot, run the command '/system license generate-new-id' before you request a trial license. Note that this feature must be used only while CHR is running on free type of RouterOS license. If you have already obtained paid or trial license, do not use regenerate feature since you will not be able to update your current key any more

Install Mikrotik On Vmware Workstation Software

Getting the License

After the initial setup a CHR instance will have a free license assigned. From there, it is possible to upgrade the license to a higher tier. Once you have a trial license all the work with the license is done on the account server where it is possible to upgrade license to a higher tier unless it is p-unlimited already.

Upgrade from free to p1 or higher

Initial upgrade from the free tier to anything higher than that incurs CHR instance registration on the account server. To do that you have to enter your MikroTik.com username and password and a desired license level you want to acquire. As a result, a CHR ID number will be assigned to your account on the account server and 60-day trial created for that ID. There are 2 ways to obtain a license - using WinBox or RouterOS command line interface:

Using WinBox (Sytem -> License menu):

Using command line interface:

To acquire a higher level trial, set up a new CHR instance, renew the license and select the desired level.

To upgrade from a Trial license to Paid go to MikroTik.com account server and choose 'all keys' in Cloud Hosted Router (CHR) section:

You will be presented with a list of your CHR machines and licenses:

To upgrade from a Trial to a Paid license click 'Upgrade', choose the desired license level (it can be different than the level of the trial license) and click 'Upgrade key':

Choose the payment method:

Install Vmware Workstation 12

It is possible to pay using account balance (deposit), credit card (CC), PayPal or using Balance (prepaid) key (if you have any).

Install Vmware Workstation Player

Upgrade from higher tier up

Only an upgrade to a higher tier is possible at the moment (for paid licenses only) and that is done in the account server. For changes to take place on the router itself renew command should be issued. When the router already has any kind of trial or paid license, the license level you set for the renew command is not important anymore, it is mandated by [license.mikrotik.com account server]. Possible upgrades are as follows:

• p1 upgrade to p10
• p1 upgrade to p-unlimited
• p10 upgrade to p-unlimited

License Update

In '/system license' menu router will indicate the time next-renewal-at when it will attempt to contact server located on licence.mikrotik.com. Communication attempts will be performed once an hour after the date on next-renewal-at and will not cease until the server responds with an error.If deadline-at date is reached without successfully contacting the account server, the router will consider that license has expired and will disallow further software updates. However, router will continue to work with the same license tier as before.

Troubleshooting

Running on VMware ESXi

Changing MTU

VMware ESXi supports MTU of up to 9000 bytes. To get the benefit of that, you have to adjust your ESXi installation to allow a higher MTU. Virtual Ethernet interface added after the MTU change will be properly allowed by the ESXi server to pass jumbo frames. Interfaces added prior to MTU change on the ESXi server will be barred by the ESXi server (it will still report old MTU as maximum possible size). If you have this, you have to re-add interfaces to the virtual guests.

Example. There are 2 interfaces added to the ESXi guest, auto-detected MTU on the interfaces show MTU size as it was at the time when the interface was added:

Using bridge on Linux

If Linux bridge supports IGMP snooping, and there are problems with IPv6 traffic it is required to disable that feature as it interacts with MLD packets (multicast) and is not passing them through.

Packets not passing from guests

The problem: after configuring a software interface (VLAN, EoIP, bridge, etc.) on the guest CHR it stops passing data to the outside world beyond the router.

The solution: check your VMS (Virtualization Management System) security settings, if other MAC addresses allowed to pass if packets with VLAN tags allowed to pass through. Adjust the security settings according to your needs like allowing MAC spoofing or certain MAC address range. For VLAN interfaces, it is usually possible to define allowed VLAN tags or VLAN tag range.

Using vlans on CHR in various Hypervisors

In some of hypervisors before Vlans can be used on VMs they need to first be configured on hypervisor it self.

ESXI

Enable Promiscuous mode in port group or virtual switch that you will use for specific VM.

ESX documentation:

Hyper-V

Buy Vmware Workstation

Hyper-V documentation:

bhyve hypervisor

It wont be possible to run CHR on this hypervisor. CHR cannot be run as paravirtualized platform.

Linode

When creating multiple Linodes with the same disk size, new Linodes will have the same systemID. This will cause issues to get a Trial/Paid license. To avoid this, run the command /system license generate-new-id after the first boot and before you request a trial or paid license. This will make sure the ID is unique.

Some useful articles:

Specific vlan is untagged by nic interface:

Allow passing other vlans:

Guest tools

VMWare

Time synchronization

Must be enabled from GUI ('Synchronize guest time with host'). Backwards synchronization is disabled by default - if guest is ahead of host by more than ~5 seconds, synchronization is not performed

Power operations

• poweron and resume scripts are executed (if present and enabled) after poweron and resume operations respectively.
• poweroff and suspend scripts are executed before poweroff and suspend operations respectively.
• If scripts take longer than 30 seconds or contain errors, the operation fails
• In case of failure, retrying the same operation will ignore any errors and complete successfully
• Failed script output is saved to file (e. g. 'poweroff-script.log', 'resume-script.log' etc)
• Scripts can be enabled/disabled from hypervisor GUI ('run VMware Tools Scripts') or by enbaling/disabling scripts from console

Quiescing/backup

Guest filesystem quiescing is performed only if requested.

• freeze script is executed before freezing the filesystem
• freeze-fail script is executed if hypervisor failed to prepare for snapshot or if freeze script failed
• thaw script is executed after snapshot has been taken
• Script run time is limited to 60 seconds
• freeze script timeouts and errors result in backup operation being aborted
• FAT32 disks are not quiesced
• Failed script output is saved to file (e. g. 'freeze-script.log', 'freeze-fail-script.log', 'thaw-script.log')

Guest info

Networking, disk, and OS info is reported to hypervisor every 30 seconds (GuestStats (memory) are disabled by default, can be enabled by setting 'guestinfo.disable-perfmon = 'FALSE' in VM config).

• The order, in which network interfaces are reported, can be controlled by setting 'guestinfo.exclude-nics', 'guestinfo.primary-nics' and 'guestinfo.low-priority-nics' options. Standard wildcard patterns can be used.

Provisioning

Can use the ProcessManager from vim API to execute scripts. Python bindings are available

• Main data structure: GuestProgramSpec
  • The workingDirectory and envVariables members are ignored
  • programPath must be set to either 'inline' or 'import'
  • If programPath is 'inline', arguments are interpreted as script text
  • If programPath is 'import', arguments are interpreted as file path

After using GuestProgramSpec together with an instance of GuestAuthentication as arguments to StartProgramInGuest unique JobID is obtained.

Script progress can be tracked by using the ListProcessesInGuest command. ListProcessesInGuest accepts an array of job id's; passing an empty array will report on all jobs started from API

• ListProcessesInGuest returns an array of GuestProcessInfo instances:
  • pid field is set to JobID
  • endTime is only set after completion
  • exitCode is set to 0 on success and -1 on error
  • name is set to 'inline' or 'import' (same as programPath in GuestProgramSpec)

Information about completed jobs is kept around for ~1 minute, or untill ListProcessesInGuest (with the corresponding JobID) is called. If the script fails, a file named 'vix_job_$JobID$ .txt' containing the script output is created. Script run time is limited to 120 seconds and script output is not saved on timeout,

• The vmrun command runScriptInGuest can also be used
• The PowerCLI cmdlet Invoke-VMScript is not supported
• Host/guest file transfer is not supported

Python example

Xen

Network, disk, memory and OS info is reported to hypervisor every 30 seconds

• On older hosts (pre 21.06.2017) only the first ipv4 address assigned to interface is visible

Provisioning

Base-64 encoded strings written to (domain local) xenstore path ('vm-data/provision/script') are decoded and interpreted a script-text. Status ('ready', 'running', 'error') is reported in 'vm-data/provision/script/status'. Scripts are accepted only if 'status' != 'running'. Base 64 encoded script output (if any) is written to 'vm-data/provision/script/otuput'.

• When creating a VM scripts can be provided by using xenapi (VM.add_to_xenstore_data)

KVM

QEMU guest agent is available. Supported agent commands can be retrieved by using guest-info command. Host-guest file transfer can be performed by using guest-file-* commands. Guest networking information can be retrieved by using the guest-network-get-interfaces command.

• Scripts can be executed by using the guest-exec command together with the GuestExec data structure:
  • If the path member is provided, the corresponding file is executed
  • If the path member is not set and input-data member is provided, input-data value is used as script input
  • If capture-output is set, script output is reported back
  • args and env members are not used

• Script job progress can be monitored with guest-exec-status command. The GuestExecStatus data structure is populated as follows:
  • On success exitcode member is set to 0
  • If the script timed out exitcode is set to 1
  • If the script contained errors exitcode is set to -1
  • signal member is not set
  • The err-data member is not used
  • If capture-output was true, Base64 encoded script output is stored in out-data

• An additional agent channel ('chr.provision_channel') is also available

Proxmox

Some agent commands can be issued by using Proxmox REST api. Guest filesystem quiescing is automatically performed when taking a snapshot

• Enabling 'chr.provision-agent' for remote access on port 1234

In host shell:

• Disabling 'chr.provision-agent'

In host shell:

• Providing remote access to default agent on port 1234

In host shell:

Guest agent python example

[Top | Back to Content]

MikroTik is found both RouterBoard where RouterOS and License are prebuilt and RouterOS Application that can be installed on a Physical Machine or Virtual Machine. RouterOS installation on Physical or Virtual Machine has license limitations. Full RouterOS packages cannot be used more than 24 hours without license. So, RouterOS application is not suitable for the Trainee or not suitable to RND purpose. From RouterOS v6.34, MikroTik introduces Cloud Hosted Router (CHR, a new RouterOS version) which has different licensing scheme. MikroTik CHR has full RouterOS packages and can be used free with bandwidth limitation. So, MikroTik CHR is so helpful to trainee and RND user. In this article, I will discuss how to install MikroTik Cloud Hosted Router on VMware Workstation properly with step by step guide.

MikroTik Cloud Hosted Router (CHR) and License

MikroTik CHR is a RouterOS version aimed for running as a virtual machine. It supports both x86 and 64-bit architecture and can be used on most of the popular hypervisors such as VMWare, Hyper-V, VirtualBox, KVM and others. MikroTik CHR has full RouterOS features enabled by default but has a different licensing model based on upload bandwidth than other RouterOS versions.

MikroTik CHR has currently the following 4 levels licensing scheme.

License	Upload Speed Limit/interface	Price
Free	1Mbit	FREE
P1	1Gbit	$45
P10	10Gbit	$95
P100	Unlimited	$250

Creating a MikroTik account, any paid license level can be used for 60 days (60 days trial license). Within 60 days period, you must purchase any license level otherwise MikroTik CHR cannot be used more. You have to do a complete fresh CHR installation.

Installing MikroTik CHR on VMware Workstation

MikroTik CHR can easily be installed on VMware Workstation but you must know the proper installation procedure. MikroTik CHR installation on VMware Workstation can be divided into the following steps.

• Downloading MikroTik CHR disk image (vmdk)
• Downloading and Installing VMware Workstation
• Customizing VMware Networking
• Creating new virtual machine for MikroTik CHR
• Accessing Virtual MikroTik Router from Winbox

Step 1: Downloading MikroTik CHR Disk Image

MikroTik introduces Cloud Hosted Router from RouterOS v6.34. So, visiting MikroTik download page, you can easily download MikroTik CHR. We need VMDK image file for VMware Workstation. So, visit MikroTik Download Page and download VMDK image file from current stable RouterOS release. The current stable RouterOS version is 6.45.5 (At the time of publishing this article). So, I am using VMDK image chr-6.45.5.vmdk for this article.

Step 2: Downloading and Installing VMware Workstation

VMware Workstation is a type 2 hypervisor. So, it should be run on a Host Operating System. VMware Workstation can be installed on both Windows and Linux Operating System and can be downloaded from VMware download page but you must have a VMware account. If you don’t have a VMware account, create an account in VMware and login your account and then download VMware Workstation for your Operating System from VMware download page. Alternatively, you can download VMware Workstation from any software sharing site. In this article, I am using VMware Workstation 15.0.0 on Windows Operating System.

VMware Workstation installation on Windows Operating System is so easy. Like other software application it will just ask to follow some graphical instructions. Complete VMware installation and run it. VMware Workstation may ask for license at first running. You can find license by searching on Google or can use workstation for 30 days trial. The home page of VMware Workstation 15.0.0 looks like the following image.

VMWare Workstation 15 Home Page

Step 3: Customizing VMware Networking

Why? Because if you have multiple network cards/adapters, you can create multiple virtual switches whose uplink will be physical network adapter. In VMware Workstation 15.0.0, you can create maximum 20 virtual switches.

I have installed VMware Workstation in my laptop which has two network cards (WLAN and LAN). If I create two virtual switches whose uplink will be two physical network interfaces, I will be able to create two virtual network adapters for MikroTik CHR virtual machine where one network adapter will be connected to one virtual switch and another network adapter will be connected to another virtual switch. So, my virtual router will have two network interfaces and one can be used as WAN connection and another can be used as LAN connection.

The following steps will show how to create two virtual switches those will be connected with two physical network adapters.

• Go to Edit menu and click on Virtual Network Editor… option. Virtual Network Editor window will appear where current virtual switches/networks are listed. You may find all options are dimmed if you don’t have admin privilege. If so, click on Change Settings button at the bottom and then you will find all options are active.
• For simplicity, delete all virtual switches without VMnet0 and VMnet1 (Select any virtual switch and click Remove Network button). If you don’t have VMnet0 or VMnet1, click on Add Network… Add a Virtual Network window will appear. Choose VMnet0 or VMnet1 which one you want to create from Select a network to add dropdown menu and click OK button. You will find that your created virtual switch/network will be listed now.
• Click on VMnet0 virtual switch and click on Bridged radio button from VMnet Information panel and then choose your physical network adapter (I am choosing WLAN adapter for this article) that you want to make uplink for this virtual switch, form Bridged to dropdown menu.
• Similarly, click on VMnet1 virtual switch and click on Bridged radio button and then choose your physical network adapter (I am choosing LAN adapter for this article) that you want to make uplink for this virtual switch, from Bridged to dropdown menu.
• Now click Apply and OK button.

VMware Virtual Network Editor

Virtual switch creation for physical network adapters has been completed where one switch will be used as WAN connection and another will be used as LAN connection. If you have more physical network adapter, you can create more virtual switch in VMware Workstation.

Step 4: Creating Virtual Machine for MikroTik CHR

We will now create virtual machine that will be used as virtual router in VMware Workstation. The following steps will show how to create new virtual machine for MikroTik CHR.

• Go to File menu and click New Virtual Machine… New Virtual Machine Wizard window will come.
• It will now ask what type of configuration you want. Click on Custom radio button and then click Next
• There is nothing to do on virtual machine hardware compatibility. So, click Next button.
• From Guest Operating System Installation, choose I will install the operating system later radio button and then click Next button.
• From Select a Guest Operating System, click Other radio button and then choose Other 64-bit from version dropdown menu.
• Now put your virtual router name that you want in Virtual machine name (MikroTik CHR) input box. Optionally you can set virtual machine default location to your desired location where virtual machine related files will be kept. Now click Next button.
• From Processor Configuration, choose how many processors you want to assign for your virtual router from Number of processors dropdown menu and choose how many cores you want to assign per processor from Number of cores per processor drop down menu. Click Next button.
• Now assign your virtual router memory (RAM) and click Next button.
• From Network Type, click Use bridged networking radio button from Network connection panel and then click Next button.
• Select I/O controller type LSI Logic SAS and then click Next button.
• Now select virtual disk type IDE and then click Next button.
• From Disk panel, click Use an existing virtual disk radio button and click Next button.
• Now browse your downloaded VMDK image file from existing disk file panel and then click Next button. Now it will ask whether it will convert exiting virtual machine disk to newer format or not. Click Convert button.
• Now click Customize Hardware button. Hardware window will appear.
• Click Add button. Add Hardware Wizard will appear. Click on Network Adapter and click Finish button. Now you will find another network adapter in Hardware list.
• Click on first Network Adapter and click on Custom: Specific virtual network radio button and then choose VMnet0 from dropdown menu. Similarly, click on second Network Adapter and click Custom: Specific virtual network radio button and then choose VMnet1 from dropdown menu and then click Close button.
• Now click Finish button to close New Virtual Machine Wizard window. Your new virtual machine/virtual router will now be created and be listed under My Computer section.
• Click mouse right button on the new virtual machine and go to Power option and then click Start Up Guest.
• Virtual machine/Virtual Router (MikroTik CHR) will start up now and ask to login. The default username is admin and password is blank. So, login with this information. After login you will find your MikroTik CHR like the following image.

MikroTik Virtual Router on VMware

Step 5: Accessing MikroTik Virtual Router (CHR) from Winbox

We have successfully installed MikroTik CHR on VMware Workstation. We will now access MikroTik Virtual Router from Winbox so that we can easily configure our MikroTik Router. To connect MikroTik Virtual Router from Winbox, first download Winbox from MikroTik website. Connect your physical network adapters to physical switch and power on the physical switches. Now open Winbox from any PC connected with these physical switches or from your Desktop or Laptop where VMware Workstation is installed and click on auto detect button. If everything is OK, you will find your CHR router’s MAC address. Click on MAC address and put username admin and keep password blank and then click Connect button. You will now find your Cloud Hosted Router in Winbox.

MikroTik CHR Login from Winbox

Note: Use MikroTik CHR on VMware Workstation only for RND purpose. If you wish to use MikroTik CHR for production, I will suggest using ESXi Hypervisor which is a bar metal hypervisor that sits directly on physical hardware layer and manage virtual machine. On the other hand, VMware Workstation hypervisor sits on a Host Operating System (Windows or Linux) and completely depend on that Host Operating System. For this, VMware Workstation is not suitable always for production use.

If you face any confusion to install MikroTik Cloud Hosted Router on VMware Workstation, watch the following video on MikroTik CHR installation on VMware Workstation. I hope it will reduce your any confusion.

How to install MikroTik CHR on VMware Workstation has been discussed in this article. I hope you will now be able to install MikroTik CHR on VMware Workstation and can do your RND. However, if you face any confusion to install MikroTik Cloud Hosted Router on VMware Workstation, feel free to discuss in comment or contact with me from Contact page. I will try my best to stay with you.