Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start:
$ systemctl status -o cat hv-kvp-daemon.service
● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr
Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a
Main PID: 219 (code=exited, status=1/FAILURE)
Started Hyper-V KVP Protocol Daemon.
KVP starting; pid is:219
open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
hv-kvp-daemon.service: Failed with result 'exit-code'.
The instance was created with:
$ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313
As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works.
Launching a recent daily image of disco on azure results in a VM in which the hv-kvp- daemon. service fails to start:
$ systemctl status -o cat hv-kvp- daemon. service daemon. service - Hyper-V KVP Protocol Daemon system/ hv-kvp- daemon. service; enabled; vendor pr
● hv-kvp-
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a
Main PID: 219 (code=exited, status=1/FAILURE)
Started Hyper-V KVP Protocol Daemon. daemon. service: Main process exited, code=exited, status=1/FAILURE daemon. service: Failed with result 'exit-code'.
KVP starting; pid is:219
open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
hv-kvp-
hv-kvp-
The instance was created with: UbuntuServer: 19.04-DAILY: 19.04.201903130 --size Standard_D2_v2 --name disco-0313
$ az vm create --resource-group [redacted] --image Canonical:
As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp- daemon. service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works.