The /dev/vmbus/hv_fcopy device won't be created unless the 'Guest
Service Interface' integration service is enabled in the VM. It isn't
enabled by default. This can be checked with the following PowerShell
command on the Hyper-V server:
Get-VMIntegrationService 'Guest Service Interface' -VMNam
cat /proc/version
Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
joe@cloud:~$ systemctl status hv-vss-daemon.service
● hv-vss-daemon.service - Hyper-V VSS Protocol Daemon
Loaded: loaded
I am seeing this as well in a Hyper-V 2012R2 environment, but with more
reasonable boot times.
$ systemd-analyze
Startup finished in 14.479s (kernel) + 3.101s (userspace) = 17.580s
$ cat /proc/version
Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ub
Is it possible for you to test other kernels with that instance? It
would be good to confirm this is in fact a regression and bisect it
down.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Chan
