I have also tried the online update method which seemed to work fine. +
I have tried several versions in an attempt at the VMWare 10gbps interfaces which work but i have not been able to trial the speed test successfully yet.
Do we know when speed test and licensing will work? I currently have the ccr1036 with two tengb sfp+ and would like to see the cost models for the CHR.
All depends on the pricing. Right now vedges are free to me as part of vmwares bundle. However, they are quite limited. Would be nice to replace them.
I think you need to price on the vedge model where you can select to deploy:
compact
normal
max
compact is basically 1 core, 512mb memory
normal 2 cores 1gb memory
etc etc.
Don’t make it painful to switch.
I’m interested if there will be a “home use” licensing option ? Something with similar restrictions to the regular Mikrotik licenses and no speed limits.
I run RouterOS in a vm for gigabit since you still don’t have a consumer device that can handle gigabit routing (serious finger shaking).
Huh… I disabled ‘Allow x86-64’ in System → Resources → Hardware, and now CHR on ESXi sees only 1 CPU core and no Ethernet (VMXNET3). How can I enable ‘Allow x86-64’ from console?
I found that we could not use sstp server . sstp client 's log imply that it’s terminated by remote peer. But when i checked the server side, i found it’s the chr not responded.
And i found that the chr is not very productive. it went down sometimes,making me to rebuild again.
just change the interface to E1000 and then you’ll have access.
then add the x86-64 option and then change the interface to VMXNET3 again.
See our article about CHR: http://forum.mikrotik.com/t/routeros-virtual-labs/90606/1
hi Mikrotik, Can we get an idea about pricing and subscriptions? Technically this looks nice, but would like to know if it make financial sense for us to put in development work. Will there be an outright purchase option like today’s License levels?
for CHR do not change away from x86_64. That will be the default and only option on CHR. For non-CHR x86 deployments, there will be only 1 option (as it was through ou 6.x branch) only x86 option.
So CHR will have a 64bit kernel. The other x86 will have a 32bit kernel.
So, enjoy that switch while it is there as in the future it will be removed.
edit: sorry, currently cannot give any details regarding licensing.
so, it’s WinBox-only switch? I cannot change it via CLI?
No, the switch will not be there at all, not in the winbox nor in the CLI. CHR will use exclusively x86_64 kernel and standard RouterOS will use the usual X86 kernel as it was till now. At this time you could still change the flavor of kernel used.
how can I do that now, without network access to the router? I have only CLI
Chupaka. Once more. Ignore this bug.
i’m using mikrotik rb2011uas-rm router.. There i configured some basic radius and hotspot configs…when i did my login i found that i’m unable to access some websites…plzz let me why its happening…
thanks, reinstalled to solve 
I hoped there was easy way…
I don’t know whether it is already mentioned by somebody but I did not read it yet.
I have tried the latest available version (6.31) on Hyper-V (Running on windows 10, if it matters) and it seems to work.
Only thing I noticed is that only legacy network interfaces are available on the RouterOS installation. Normal network interfaces won’t show up in the OS
I can’t find a 6.31rc9 user-manager package. the full 6.31 package wont install, nor will a 6.30 package. any help here? want to get into testing
Another possible bug I found is that when I assign more than 1 virtual processor, the interface I configured won’t get an IP address from my DHCP server (running on a real routerboard).
The routerboard does offer an IP, but it keeps in status offered and the DHCP client on the CHR keeps searching.
Hello. I have read this topic and it seems that mikrotik users here are looking for bugs in CHR and talk about it to developers. I think it is not good. The real good thing is the developers should help us to move the CHR or simply the VM image of router OS to current cloud hosted servers such as Azure. I make some actions and see that current situation is bad. Nor CHR nor VM image of routerOS have no ability to be successfull working in Azure. The current network infastructure not capable to work from the box with network infrastructure of Azure. The lack of VMagent leave no chance to deploy the RouterOS images in Azure. I really want to do that and pay for x86 license.
CHR is in early test stage. It has only been posted on forum, so this is like Beta1. There is no Azure support because it is too early. We will have Amazon and Azure later, just be patient. If you are not comfortable with Beta1 test level, just ignore this thread for a while.