CHR in Hyper-V hang/unresponsive

RouterOS Virtualization
1

Hi

I’m doing some testing of CHR in Hyper-V, but experience a problem with the CHR hangs or stop responding when running certain commands.
The problem only occurs when I have added more than one network adapter. The first network adapter is connected, and the other ones are currently disconnected. I don’t use the legacy adapter.
If I run the command “interface print” or “ip address print” the router stop responding for 10 minutes.
After the 10 minutes wait it output “action timed out - try again, if error continues contact MikroTik support and send a support file (13)” to the console. I can’t connect to the router on http or winbox.
I have tested with both the “bugfix” and the “current” version. It’s tested on both Hyper-V in Windows Server 2012 R2 and Windows 10 (1607).
If I use legacy network adapters, I don’t see this problem. But I would prefer to use new/synthetic network adapter.

Anyone else experienced this issue?

2

we are working on the issue with the interfaces. You can try latest 6.38 release candidates.

3

Hi janisk

I’m pleased to know that you are aware of the issue. I have downloaded 6.38rc31 (release candidate) and sinned a new VM up.
If I add a second NIC and type “interface print” in the console the router output:

Rebooting…
Stopping services…
failed to stop ipsec: std failure: timeout (13)
failed to stop ppp: std failure: timeout (13)
failed to stop wireless: std failure: timeout (13)
failed to stop route: std failure: timeout (13)

When it start up again I see this error in the log:

system,error,critical open /dev/panics failed

After another reboot I can type interface print again, and see both interfaces right away. But if an add a 3 NIC, then I can’t use the router. It keeps writing “Rebooting..” and nothing happens until I do a power off. I can’t use the router afterwards.

Any hints?

4

zyflex
Build 6.36.3 works almost ideally with synthetic NIC on Hyper-V 2012 R2 and 2008 R2. I’m using it about 2 months.

5

Great tip, Rushmore.
The 6.36.3 build are also working on mine server. I have added 4 NIC’s without problems.

You write that it works almost ideally on your server. What issue(s) are you experiencing?

6

zyflex
Most annoying issue refers to live migration in Hyper-V cluster. I wrote about it here.
And the second issue I found is incomplete auto-negotiation on ethernet ports.

7

Good news then as I have not gotten any response if you could recreate this issue :slight_smile:

8

I hope that we will see a much better CHR for Hyper-V with version 7. Better multicore and a better Linux kernel for Hyper-V with correct tools. :slight_smile:
My guess regarding Live migration issue is to blame the old tools. As you said in that post this was an issue that could occur on older Linux and tools.
To solve that issue you could add netwatch job that pings the hyper-v host or something else close every second. This should do the trick. Don’t solve the problem but it’s a workaround 

9

Already did that. Now it recovers in 2 - 3 seconds after migration.

10

Test the new 6.38rc34 release. This is running for me now and all these hangings problems are gone. If we are talkning about production I would wait for next current release which may contain these fixes.