Could this be a race condition with the device file creation and start of the hv-kvp-daemon.service?
[from /var/log/syslog] Jan 16 10:26:45 kvp-disco-test systemd[1]: Started Hyper-V KVP Protocol Daemon. ... Jan 16 10:26:45 kvp-disco-test KVP: KVP starting; pid is:213 Jan 16 10:26:45 kvp-disco-test KVP: open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory Jan 16 10:26:45 kvp-disco-test systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE $ stat /dev/vmbus/hv_kvp File: /dev/vmbus/hv_kvp Size: 0 Blocks: 0 IO Block: 4096 character special file Device: 6h/6d Inode: 212 Links: 1 Device type: a,37 Access: (0600/crw-------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-01-16 10:26:56.868312550 +0000 Modify: 2019-01-16 10:26:56.868312550 +0000 Change: 2019-01-16 10:26:56.868312550 +0000 I realize this isn't the creation time (which I can't figure out if I can even get), but it's suspiciuos. Also, manually starting the service once logged in works and it stays running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779640 Title: [Hyper-V] KVP daemon crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
