

The x86-ROS router uses a different license system from the CHR-ROS router. #2 I am not certain but I think this might work: Instead of using a CHR, try using an x86 ROS virtual router.

The disadvantage of this is everything is slower. Any virtaul machines ( CHR ) running on the virtual hypervisor will still be there. With this #1 method - you move the virtual hypervisor and spin it up. Install your CHR on the virtual hypervisor. #1 Create a virtual hypervisor on you primary hypervisor. There are two possible work-arounds options to retain the license ( for a CHR move ). When a Mikrotik CHR ( with the license ) is moved to another location on the hypervisor or to another hypervisor ( either manually or by automatically ) the new spun-up CHR will no longer retain the original license.
