Comment 3 for bug 1968013

For easier debugging this can be reproduced on any affected system (Tried KVM and EC2) by just running:

$ sudo systemctl start hv-kvp-daemon.service

^^ This will stall while one would assume it should quick-exit due to the ConditionVirtualization not being met.

A full cycle (90 second stall) of this start-try in the journal will look like:
Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl start hv-kvp-daemon.service
Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000)
Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 06 09:17:01 ip-172-31-16-15 CRON[2295]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session closed for user root

Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out.
Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp.
Apr 06 09:18:31 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session closed for user root
Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon.
Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'.
Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'.