Comment 4 for bug 1614618

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-6ubuntu1~16.04.2) ) #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016

$ systemctl status hv-fcopy-daemon.service --no-pager --full
● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
   Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-08-30 15:51:41 PDT; 32min ago
  Process: 3105 ExecStart=/usr/sbin/hv_fcopy_daemon -n (code=exited, status=1/FAILURE)
 Main PID: 3105 (code=exited, status=1/FAILURE)

Aug 30 15:51:41 xenial01 systemd[1]: Started Hyper-V File Copy Protocol Daemon.
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

$ sudo grep -E -i "hv.fcopy" /var/log/syslog
Aug 30 15:51:41 xenial01 HV_FCOPY: starting; pid is:3105
Aug 30 15:51:41 xenial01 HV_FCOPY: open /dev/vmbus/hv_fcopy failed; error: 2 No such file or directory
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.