Install MikroTik CHR on VMware Workstation

Introduction

Cloud Hosted Router (CHR) is the RouterOS edition designed to run as a virtual machine. In VMware Workstation, the official VMDK image can be attached as the virtual disk and then configured as a lab router.

Prerequisites

• VMware Workstation and a 64-bit host with virtualization support.
• The official CHR image for VMware (VMDK), downloaded from MikroTik.
• A planned lab network, IP address, gateway, DNS servers, and access to the Workstation virtual-network settings.

01 — Download the official image

Download the CHR VMware disk image from the official MikroTik download area. CHR images are virtual disks, not ready-made VMs; create a new guest VM and attach the downloaded VMDK as its disk.

02 — Create the VM and attach the disk

1. Create a new virtual machine in VMware Workstation and select an appropriate 64-bit guest type.
2. Remove the automatically created empty disk if needed, then add the official CHR VMDK as an existing virtual disk.
3. Allocate CPU and RAM appropriate to the lab; MikroTik documents 256 MB as a minimum and recommends at least 1024 MiB for CHR instances.

03 — NIC mapping and boot

Add the required virtual NICs before starting the VM. In Workstation, NAT normally gives the lab guest outbound access through the host; Bridged connects the guest to the selected physical network. Choose intentionally and avoid connecting an untrusted lab router to a production network.

Boot the VM, sign in as the default admin user, and set a strong password immediately. Check interface names with /interface print; interface order can change when adapters are added, removed, or reordered in the hypervisor.

04 — Configure basic network settings

Replace the example address, gateway, DNS servers, and interface name with values for the actual lab network. Confirm the correct interface before adding the address.

/system identity set name=CHR-LAB
/ip address add address=192.168.1.10/24 interface=ether1
/ip route add dst-address=0.0.0.0/0 gateway=192.168.1.1
/ip dns set servers=1.1.1.1,8.8.8.8
/ping 8.8.8.8

05 — CHR license levels

MikroTik also documents a 60-day trial for paid levels. Check the current official licensing page before purchasing or changing a license.

06 — Test

1. Verify the address and default route with /ip address print and /ip route print.
2. Ping the gateway first, then test an external IP address. Test DNS separately with a name lookup after enabling the required RouterOS DNS behavior for the lab.
3. Open WinBox or WebFig only from the management network and confirm the identity and interface mapping.

Troubleshooting

• No network: verify the selected NAT or Bridged network, adapter connection state, and the corresponding RouterOS interface name.
• No route: confirm the gateway is reachable from the configured subnet and that only the intended default route is active.
• Unexpected traffic behavior: inspect Workstation virtual-network settings and RouterOS firewall/NAT configuration; do not assume NAT or Bridged creates RouterOS firewall rules automatically.

Best Practices

• Use an isolated NAT or host-only lab network unless Bridged access is explicitly required.
• Label VM NICs and RouterOS interfaces consistently, record the mapping, and take snapshots only with a clear rollback plan.
• Change the default password, restrict management access, and keep RouterOS updated according to the supported release plan.

Frequently Asked Questions

Conclusion

Attach the official CHR VMDK to a deliberately networked Workstation VM, confirm interface order, then apply and test the correct address, route, and DNS settings. Use the license tier and virtual network mode that match the lab objective.

Official references

• MikroTik Documentation — Cloud Hosted Router (CHR)
• MikroTik — Official downloads