Comment 5 for bug 1932081

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

ubuntu@gen2:~$ dpkg-query -W linux-cloud-tools-common
linux-cloud-tools-common 5.4.0-79.88

ubuntu@gen2:~$ systemctl status hv-kvp-daemon.service
● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor preset: enab>
     Active: active (running) since Thu 2021-07-08 16:06:00 UTC; 1min 3s ago
   Main PID: 283 (hv_kvp_daemon)
      Tasks: 1 (limit: 8334)
     Memory: 3.2M
     CGroup: /system.slice/hv-kvp-daemon.service
             └─283 /usr/lib/linux-tools/5.8.0-1038-azure/hv_kvp_daemon -n

Jul 08 16:06:00 gen2 systemd[1]: Started Hyper-V KVP Protocol Daemon.
Jul 08 16:06:00 gen2 KVP[283]: KVP starting; pid is:283
Jul 08 16:06:00 gen2 KVP[283]: KVP LIC Version: 3.1

ubuntu@gen2:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.8.0-1038-azure root=PARTUUID=14d21af5-beed-4a59-966b-cbcab58b7936 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1

So with normal instances this service is still running.

Upgraded to a different kernel

ubuntu@gen2:~$ cat /proc/cmdline
snapd_recovery_mode=cloudimg-rootfs console=tty1 console=ttyS0 earlyprintk=ttyS0

ubuntu@gen2:~$ systemctl status hv-kvp-daemon.service
● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Thu 2021-07-08 16:12:39 UTC; 1min 45s ago
             └─ ConditionKernelCommandLine=!snapd_recovery_mode was not met

Jul 08 16:12:39 gen2 systemd[1]: Condition check resulted in Hyper-V KVP Protocol Daemon being skipped.

And the service is not running on this other kernel type.

This means that we are not regressing support for this service on stock instance type & kernel type; and correctly prevent running it on the other instance type & kernel type.

No other series apart from focal support this yet, hence this is now verified. This change should remain in all other kernels, in case we enable using those kernels on this instance type.