Hello mikrotik community,

I am trying to install CHR on a fresh Hetzner Cloud CCX13 VM (this is a new lineup with dedicated CPU cores on AMD hardware).

I'm following the official docs verbatim (hetzner-doc,mikrotik-doc):

• create vm
• boot into rescue mode
• download and write raw image

Commands executed in rescue console:

After rebooting the VM won't boot.
Attaching to the console windows shows the following error message:

I managed to locate a somewhat similar error message in combination with the new Hetzner lineup: reddit

Here the threads OP writes:

I wrote Hetzner a ticket and got a reply earlier today, apparently there's a workaround but I haven't tried it yet:
CCX\3 models are provisioned using UEFI.

Any ideas or insights are greatly appreciated.

I not know about this, but 2 suggestions:

1. Try with dirrerent ROS versions.
2. "UEFI hard disk" can't be changed to legacy and try it?

Regards.

@krafg: thanks for your input, but hetzner doesn't support editing of BIOS settings for their VM products (as far as I know only dedicated root servers support this feature)

Okay, so I tried different VMs (the default Hetzner Cloud VMs types):
- CX21 (Intel-based with Shared vCPUs): routeros installs and boots without issue
- CPX21 (AMD-based with Shared vCPUs): routeros installs and boots without issue

I've sent a support request to Hetzner, will post any insights here.

Getting this to work on this new VM type would be great, the price point for fully dedicated vCPUs on current hardware is quite compelling.

I not know about this, but 2 suggestions:

1. Try with dirrerent ROS versions.
2. "UEFI hard disk" can't be changed to legacy and try it?

Regards.

CHR does not support UEFI.

I am surprised Hetzner omits OVA and OVF from their documentation.
Router OS CHR OVA template proved useful with VMware ESXi 6.7u3 local host.

Got an update from Hetzner Support.

All new VMs of type CCXx3 (dedicated CPU) have UEFI boot mode enabled by default -- and routeros does not support UEFI.

But: Hetzner's support team can enable legacy boot if requested to do so (via ticket)

After the change I installed routeros via rescue console and the VM boots up just fine

Thanks for all your help and suggestions.

I've also come across this thing and lost an hour trying to understand what's happened.
Instructions are pretty clear and written by myself for the Inter, but they don't work.
The new AMD platform with the new firmware was the first idea, and I am glad that it was confirmed immediately by the googling.

Thanks for sharing this!