[Resolved] Mikrotik Router on VirtualBox shutdown prematurely

[hunterv]

Hello,

I have succesfully been running Mikrotik router software on virtualbox for testing purposes for some time. After recently upgrading virtualbox to the most current version, my mikrotik router VM doesn't run correctly. The device boots up and gets to the login prompt and then shutsdown. The log indicates that the is a request to power down. I didn't see any clear error in the log to indicate what the problem could be.

Regards,
hunterv

[hunterv]

I've included the log file from VirtualBox.

[mpack]

00:00:01.659800 Guest OS type: 'Other'
...
00:00:01.766896 RamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
...
00:00:01.767113 VRamSize <integer> = 0x0000000000600000 (6 291 456, 6 MB)

None of that looks right. What exactly is the guest OS?

[hunterv]

VirtualBox Version: 6.0.8 r130520 (Qt5.6.3)
Guest Additions are installed, version: n/a
Host: MacBookPro11,1, macOS 10.14.5 (18F132), 8 GB Memory
Guest: mikrotik routerOs -6.44.2

[hunterv]

00:00:01.659800 Guest OS type: 'Other'
...
00:00:01.766896 RamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
...
00:00:01.767113 VRamSize <integer> = 0x0000000000600000 (6 291 456, 6 MB)

None of that looks right. What exactly is the guest OS?

mikrotik routerOs -6.44.2

[mpack]

Apparantly Mikrotik RouterOS is based on a Linux 2.6 kernel, I suggest using that template, instead of "Other", in the VM settings.

Otherwise, since it seems to be a licensed product (software dongle), I suggest contacting the vendors for support. Perhaps your VM recipe does not match the requirements of this OS, or perhaps you did something to deactivate the software.

[hunterv]

Seems I have found the route of the issue. I've found something to indicate that the guest OS is sending a power off instruction.

[mpack]

Seems I have found the route of the issue. I've found something to indicate that the guest OS is sending a power off instruction.

Yes, that is what makes it look like a software activation issue.

[hunterv]

Thanks, looks like VirtualBox is functioning correctly.