No shell in Metarouter if memory is more than 128Mbytes

RouterOS Virtualization
1

If i set the memory of a Metarouter with Openwrt more than 128Mbytes, shell doesn’t come up after booting.

All the boot messages are shown properly and i can see that memory has been recognized by the system, but you can not get in to shell anymore by pressing enter.

Any thoughts on that?

Gokalp

2

with OpenWRT image from wiki i have no problems running it in metarouter with that amount of memory assigned to it.

[admin@hs] /metarouter> print 
Flags: X - disabled 
 #   NAME               MEMORY-SIZE   DISK-SIZE     USED-DISK     STATE        
 0   mr1-RouterOS       32MiB         unlimited     602kiB        running      
 1   mr2-OpenWrt        128MiB        unlimited     5938kiB       running      
[admin@hs] /metarouter> console 1
[;24r
[Ctrl-A is the prefix key]



root@OpenWrt:/#  ls
bin     etc     kernel  mnt     rom     sbin    tmp     vstore
cm      home    lib     pckg    root    store   usr     www
dev     jffs    logs    proc    run     sys     var
root@OpenWrt:/#

at least, if you have problems with that now, wait for release of RotuerOS 4.4

3

Hi Janisk,

If you set the memory more than 128Mbyte, i.e. 129Mbyte, it will generate the problem.

I’ll be happy if it is solved by the release of 4.4.

Thanks

4

have misunderstood you, well, 128MB works, 129 and up do not, currently check if you can run metarouter with max of 128MB of ram assigned.

5

I can run Openwrt with 128MB without any problem in Routerboard 450G.

We also tried Openwrt on a x86 system with 256MB and it runs (bare-metal install, no virt.) without any problem.

Regards
Gokalp

6

x86 is not metarouter, it is either KVM or, erm now KVM :slight_smile:

it is metarouter problem, we are looking into it.

7

I’m trying to tell that Openwrt can work on another platform with 256MB without any problem.

The topic is related to Metarouter and yes i’m aware of that it has a problem with the given condition.