The daemons package is in the rc9. Could anyone test in Hyper-V if it works as expected?

I just made a few first tests with VyOS 1.2.0-rolling+201811281529 and VyOS 1.2.0-RC9 (downloaded now) on Hyper-V 2012R2 (Generation 2 VM, SecureBoot off):

Keyboard on Virtual Machine Connection (console session in Hyper-V manager) is ok in rolling but not in RC9

sudo lsmod shows loaded modules:

hv_utils               28672  0
cn                     16384  3 hv_utils
ptp                    20480  1 hv_utils
hv_netvsc              53248  0
hv_storvsc             20480  1
scsi_transport_fc      45056  1 hv_storvsc
hv_vmbus               45056  4 hv_utils,hv_netvsc,hv_storvsc,hyperv_keyboard
hyperv_keyboard        16384  0
hv_balloon             24576  0

(hyperv_keyboard, cn, ptp, scsi_mod not in RC9, in rolling only)

Daemons (the same in rolling and RC9):

vyos@vyos:~$ sudo ps -ef | grep hv
root       764     2  0 08:19 ?        00:00:00 [hv_vmbus_con]
root      1390     2  0 08:19 ?        00:00:00 [hv_balloon]
root      1673     1  0 08:19 ?        00:00:00 /usr/sbin/hv_fcopy_daemon -n
root      1675     1  0 08:19 ?        00:00:00 /usr/sbin/hv_kvp_daemon -n
root      1678     1  0 08:19 ?        00:00:00 /usr/sbin/hv_vss_daemon -n

Hyper-V Manager shows:
Heartbeat: OK
Integrations Services: Update required

Shutdown (not Power-off) from Hyper-V Manager: ok

So the rolling seems ok but not RC9

In 1.2.0-rc10 the keyboard bug is still there as in RC9. No keyboard in hyper-v virtual machine connection. Latest rolling is ok (vyos-1.2.0-rolling+201812050337)

@syncer is it really finished for you? The bug is still there in my tests

it works in rolling, it's just @dmbaturin who messed up RC builds

:-)

@dmbaturin :
The keyboard bug is still there in VyOS-1.2.0-epa2! No keyboard possible in hyper-v virtual machine connection (console)

I will test tomorrow on a Win2012R2 host

I tested on VyOS-1.2.0-rolling+201901030337 and the keyboard works in console on Win2012R2. As it already worked in older rolling releases I really hope it goes in EPA3.

I just tested with 1.2.0-EPA3 and it works! So the fix is included. Thanks c-po