This also happens in Bionic minimal images and seems to be a simple race where the daemon is launched when the device is not yet visible.
It seems Fedora had the same or a similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1195029 >From the conversation in that bug report, my understanding is that this daemon supports features that can be enabled/disabled while the system is live and that the daemon should therefore be launched/stopped dynamically when the /dev/vmbus/hv_kvp device node comes or goes. Since this race condition happening or not happening may depend on host, hypervisor and boot speed, it could pop up also on existing releases and thus should probably be treated with a certain amount of urgency. ** Bug watch added: Red Hat Bugzilla #1195029 https://bugzilla.redhat.com/show_bug.cgi?id=1195029 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
