| 2017-12-19 16:31:24 |
David Coronel |
bug |
|
|
added bug |
| 2017-12-19 16:51:30 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2017-12-19 17:00:09 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2017-12-20 17:58:19 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-12-20 17:58:27 |
Joseph Salisbury |
tags |
|
kernel-da-key |
|
| 2017-12-20 17:58:37 |
Joseph Salisbury |
linux (Ubuntu): status |
Incomplete |
Triaged |
|
| 2017-12-21 16:18:25 |
Eric Desrochers |
bug |
|
|
added subscriber Dan Streetman |
| 2017-12-21 16:18:45 |
Eric Desrochers |
tags |
kernel-da-key |
kernel-da-key sts |
|
| 2017-12-21 16:19:03 |
Eric Desrochers |
tags |
kernel-da-key sts |
azure kernel-da-key sts |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
nominated for series |
|
Ubuntu Artful |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-12-21 20:29:08 |
Eric Desrochers |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-12-21 20:30:10 |
Eric Desrochers |
attachment added |
|
UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025785/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch |
|
| 2017-12-21 20:35:47 |
Eric Desrochers |
attachment removed |
UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025785/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch |
|
|
| 2017-12-21 20:36:40 |
Eric Desrochers |
attachment added |
|
0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025786/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch |
|
| 2017-12-21 20:49:06 |
Eric Desrochers |
attachment removed |
0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025786/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch |
|
|
| 2017-12-21 20:49:30 |
Eric Desrochers |
attachment added |
|
0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+attachment/5025788/+files/0001-UBUNTU-Debian-hyper-v-Ensure-that-hv-kvp-daemon.serv.patch |
|
| 2017-12-22 00:20:49 |
Ubuntu Foundations Team Bug Bot |
tags |
azure kernel-da-key sts |
azure kernel-da-key patch sts |
|
| 2017-12-22 00:20:51 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Joseph Salisbury |
| 2018-07-06 08:03:23 |
Andy |
merge proposal linked |
|
https://code.launchpad.net/~andyliuliming/ubuntu/+source/linux/+git/xenial/+merge/349032 |
|
| 2018-07-10 19:22:02 |
Eric Desrochers |
linux (Ubuntu): status |
Triaged |
Incomplete |
|
| 2018-07-10 19:22:06 |
Eric Desrochers |
linux (Ubuntu Xenial): status |
New |
Incomplete |
|
| 2018-07-10 19:22:08 |
Eric Desrochers |
linux (Ubuntu Zesty): status |
New |
Incomplete |
|
| 2018-07-10 19:22:09 |
Eric Desrochers |
linux (Ubuntu Artful): status |
New |
Incomplete |
|
| 2018-07-10 19:22:12 |
Eric Desrochers |
linux (Ubuntu Bionic): status |
Triaged |
Incomplete |
|
| 2018-07-27 01:38:22 |
Andy |
linux (Ubuntu): status |
Incomplete |
In Progress |
|
| 2018-07-27 01:38:34 |
Andy |
linux (Ubuntu): assignee |
|
Andy (andyliuliming) |
|
| 2018-07-27 01:45:54 |
Andy |
linux (Ubuntu Xenial): assignee |
|
Andy (andyliuliming) |
|
| 2018-07-27 01:45:55 |
Andy |
linux (Ubuntu Zesty): assignee |
|
Andy (andyliuliming) |
|
| 2018-07-27 01:45:57 |
Andy |
linux (Ubuntu Artful): assignee |
|
Andy (andyliuliming) |
|
| 2018-07-27 01:45:58 |
Andy |
linux (Ubuntu Bionic): assignee |
|
Andy (andyliuliming) |
|
| 2018-07-27 01:46:06 |
Andy |
linux (Ubuntu Xenial): status |
Incomplete |
In Progress |
|
| 2018-07-27 01:46:08 |
Andy |
linux (Ubuntu Zesty): status |
Incomplete |
In Progress |
|
| 2018-07-27 01:46:10 |
Andy |
linux (Ubuntu Artful): status |
Incomplete |
In Progress |
|
| 2018-07-27 01:46:13 |
Andy |
linux (Ubuntu Bionic): status |
Incomplete |
In Progress |
|
| 2018-07-27 03:11:13 |
Andy |
linux (Ubuntu): assignee |
Andy (andyliuliming) |
|
|
| 2018-07-27 03:11:15 |
Andy |
linux (Ubuntu Xenial): assignee |
Andy (andyliuliming) |
|
|
| 2018-07-27 03:11:17 |
Andy |
linux (Ubuntu Zesty): assignee |
Andy (andyliuliming) |
|
|
| 2018-07-27 03:11:20 |
Andy |
linux (Ubuntu Bionic): assignee |
Andy (andyliuliming) |
|
|
| 2018-07-27 03:11:23 |
Andy |
linux (Ubuntu Artful): assignee |
Andy (andyliuliming) |
|
|
| 2018-07-31 14:04:14 |
Eric Desrochers |
linux (Ubuntu Artful): status |
In Progress |
Won't Fix |
|
| 2018-07-31 14:04:16 |
Eric Desrochers |
linux (Ubuntu Zesty): status |
In Progress |
Won't Fix |
|
| 2018-07-31 14:04:39 |
Eric Desrochers |
linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2018-08-03 14:25:01 |
Eric Desrochers |
description |
This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start.
Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this:
====================
# On Azure/Hyper-V systems start the hv_kvp_daemon
#
# author "Andy Whitcroft <apw@canonical.com>"
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
[Service]
ExecStart=/usr/sbin/hv_kvp_daemon -n
[Install]
WantedBy=multi-user.target
====================
The suggested modification is to make the [Unit] section look like this:
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
DefaultDependencies=no
After=systemd-remount-fs.service
Before=shutdown.target cloud-init-local.service walinuxagent.service
Conflicts=shutdown.target
RequiresMountsFor=/var/lib/hyperv
The hv-kvp-daemon service is not currently part of the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.809s
└─multi-user.target @10.723s
└─ephemeral-disk-warning.service @10.538s +31ms
└─cloud-config.service @8.249s +2.252s
└─basic.target @8.044s
└─sockets.target @8.019s
└─snapd.socket @7.692s +264ms
└─sysinit.target @6.719s
└─cloud-init.service @5.803s +842ms
└─networking.service @5.137s +612ms
└─network-pre.target @5.074s
└─cloud-init-local.service @2.257s +2.783s
└─systemd-remount-fs.service @1.368s +656ms
└─systemd-journald.socket @1.218s
└─-.mount @649ms
└─system.slice @653ms
└─-.slice @649ms
In an Azure VM, the current startup time of my test is:
$ systemd-analyze
Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s
After making the suggested change, the startup time is similar:
$ systemd-analyze
Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s
And the service is now in the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.666s
└─multi-user.target @10.636s
└─ephemeral-disk-warning.service @10.556s +36ms
└─cloud-config.service @8.423s +2.095s
└─basic.target @8.124s
└─sockets.target @8.101s
└─lxd.socket @7.677s +326ms
└─sysinit.target @6.755s
└─cloud-init.service @5.814s +908ms
└─networking.service @5.111s +651ms
└─network-pre.target @5.087s
└─cloud-init-local.service @2.345s +2.707s
└─hv-kvp-daemon.service @2.316s
└─systemd-remount-fs.service @1.253s +680ms
└─system.slice @1.225s
└─-.slice @650ms
The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) |
This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start.
Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this:
====================
# On Azure/Hyper-V systems start the hv_kvp_daemon
#
# author "Andy Whitcroft <apw@canonical.com>"
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
[Service]
ExecStart=/usr/sbin/hv_kvp_daemon -n
[Install]
WantedBy=multi-user.target
====================
The suggested modification is to make the [Unit] section look like this:
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
DefaultDependencies=no
After=systemd-remount-fs.service
Before=shutdown.target cloud-init-local.service walinuxagent.service
Conflicts=shutdown.target
RequiresMountsFor=/var/lib/hyperv
The hv-kvp-daemon service is not currently part of the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.809s
└─multi-user.target @10.723s
└─ephemeral-disk-warning.service @10.538s +31ms
└─cloud-config.service @8.249s +2.252s
└─basic.target @8.044s
└─sockets.target @8.019s
└─snapd.socket @7.692s +264ms
└─sysinit.target @6.719s
└─cloud-init.service @5.803s +842ms
└─networking.service @5.137s +612ms
└─network-pre.target @5.074s
└─cloud-init-local.service @2.257s +2.783s
└─systemd-remount-fs.service @1.368s +656ms
└─systemd-journald.socket @1.218s
└─-.mount @649ms
└─system.slice @653ms
└─-.slice @649ms
In an Azure VM, the current startup time of my test is:
$ systemd-analyze
Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s
After making the suggested change, the startup time is similar:
$ systemd-analyze
Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s
And the service is now in the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.666s
└─multi-user.target @10.636s
└─ephemeral-disk-warning.service @10.556s +36ms
└─cloud-config.service @8.423s +2.095s
└─basic.target @8.124s
└─sockets.target @8.101s
└─lxd.socket @7.677s +326ms
└─sysinit.target @6.755s
└─cloud-init.service @5.814s +908ms
└─networking.service @5.111s +651ms
└─network-pre.target @5.087s
└─cloud-init-local.service @2.345s +2.707s
└─hv-kvp-daemon.service @2.316s
└─systemd-remount-fs.service @1.253s +680ms
└─system.slice @1.225s
└─-.slice @650ms
The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.)
https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html#
microsoft Hyper-V, also known as Viridian or Windows Server Virtualization |
|
| 2018-08-03 14:42:08 |
Eric Desrochers |
description |
This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start.
Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this:
====================
# On Azure/Hyper-V systems start the hv_kvp_daemon
#
# author "Andy Whitcroft <apw@canonical.com>"
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
[Service]
ExecStart=/usr/sbin/hv_kvp_daemon -n
[Install]
WantedBy=multi-user.target
====================
The suggested modification is to make the [Unit] section look like this:
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
DefaultDependencies=no
After=systemd-remount-fs.service
Before=shutdown.target cloud-init-local.service walinuxagent.service
Conflicts=shutdown.target
RequiresMountsFor=/var/lib/hyperv
The hv-kvp-daemon service is not currently part of the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.809s
└─multi-user.target @10.723s
└─ephemeral-disk-warning.service @10.538s +31ms
└─cloud-config.service @8.249s +2.252s
└─basic.target @8.044s
└─sockets.target @8.019s
└─snapd.socket @7.692s +264ms
└─sysinit.target @6.719s
└─cloud-init.service @5.803s +842ms
└─networking.service @5.137s +612ms
└─network-pre.target @5.074s
└─cloud-init-local.service @2.257s +2.783s
└─systemd-remount-fs.service @1.368s +656ms
└─systemd-journald.socket @1.218s
└─-.mount @649ms
└─system.slice @653ms
└─-.slice @649ms
In an Azure VM, the current startup time of my test is:
$ systemd-analyze
Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s
After making the suggested change, the startup time is similar:
$ systemd-analyze
Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s
And the service is now in the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.666s
└─multi-user.target @10.636s
└─ephemeral-disk-warning.service @10.556s +36ms
└─cloud-config.service @8.423s +2.095s
└─basic.target @8.124s
└─sockets.target @8.101s
└─lxd.socket @7.677s +326ms
└─sysinit.target @6.755s
└─cloud-init.service @5.814s +908ms
└─networking.service @5.111s +651ms
└─network-pre.target @5.087s
└─cloud-init-local.service @2.345s +2.707s
└─hv-kvp-daemon.service @2.316s
└─systemd-remount-fs.service @1.253s +680ms
└─system.slice @1.225s
└─-.slice @650ms
The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.)
https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html#
microsoft Hyper-V, also known as Viridian or Windows Server Virtualization |
This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start.
Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this:
====================
# On Azure/Hyper-V systems start the hv_kvp_daemon
#
# author "Andy Whitcroft <apw@canonical.com>"
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
[Service]
ExecStart=/usr/sbin/hv_kvp_daemon -n
[Install]
WantedBy=multi-user.target
====================
The suggested modification is to make the [Unit] section look like this:
[Unit]
Description=Hyper-V KVP Protocol Daemon
ConditionVirtualization=microsoft
DefaultDependencies=no
After=systemd-remount-fs.service
Before=shutdown.target cloud-init-local.service walinuxagent.service
Conflicts=shutdown.target
RequiresMountsFor=/var/lib/hyperv
The hv-kvp-daemon service is not currently part of the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.809s
└─multi-user.target @10.723s
└─ephemeral-disk-warning.service @10.538s +31ms
└─cloud-config.service @8.249s +2.252s
└─basic.target @8.044s
└─sockets.target @8.019s
└─snapd.socket @7.692s +264ms
└─sysinit.target @6.719s
└─cloud-init.service @5.803s +842ms
└─networking.service @5.137s +612ms
└─network-pre.target @5.074s
└─cloud-init-local.service @2.257s +2.783s
└─systemd-remount-fs.service @1.368s +656ms
└─systemd-journald.socket @1.218s
└─-.mount @649ms
└─system.slice @653ms
└─-.slice @649ms
In an Azure VM, the current startup time of my test is:
$ systemd-analyze
Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s
After making the suggested change, the startup time is similar:
$ systemd-analyze
Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s
And the service is now in the critical-chain:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.666s
└─multi-user.target @10.636s
└─ephemeral-disk-warning.service @10.556s +36ms
└─cloud-config.service @8.423s +2.095s
└─basic.target @8.124s
└─sockets.target @8.101s
└─lxd.socket @7.677s +326ms
└─sysinit.target @6.755s
└─cloud-init.service @5.814s +908ms
└─networking.service @5.111s +651ms
└─network-pre.target @5.087s
└─cloud-init-local.service @2.345s +2.707s
└─hv-kvp-daemon.service @2.316s
└─systemd-remount-fs.service @1.253s +680ms
└─system.slice @1.225s
└─-.slice @650ms
The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) by checking whether the system is executed in a virtualized environment and optionally test whether it is a specific implementation, in this case "microsoft" for Hyper-V.
https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html#
microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization |
|
| 2018-08-03 14:54:49 |
Eric Desrochers |
linux (Ubuntu Bionic): assignee |
|
Eric Desrochers (slashd) |
|
| 2018-08-03 14:54:51 |
Eric Desrochers |
linux (Ubuntu): assignee |
|
Eric Desrochers (slashd) |
|
| 2018-08-03 14:54:55 |
Eric Desrochers |
linux (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2018-08-23 15:52:08 |
Marcelo Cerri |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-08-23 15:52:10 |
Marcelo Cerri |
linux (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2018-08-28 17:01:45 |
Brad Figg |
tags |
azure kernel-da-key patch sts |
azure kernel-da-key patch sts verification-needed-bionic |
|
| 2018-08-28 20:25:48 |
Launchpad Janitor |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-08-28 20:25:48 |
Launchpad Janitor |
cve linked |
|
2018-9363 |
|
| 2018-08-29 06:39:10 |
Andy |
tags |
azure kernel-da-key patch sts verification-needed-bionic |
azure kernel-da-key patch sts verification-done-bionic |
|
| 2018-08-29 11:04:39 |
Brad Figg |
tags |
azure kernel-da-key patch sts verification-done-bionic |
azure kernel-da-key patch sts verification-done-bionic verification-needed-xenial |
|
| 2018-08-30 07:45:10 |
Andy |
tags |
azure kernel-da-key patch sts verification-done-bionic verification-needed-xenial |
azure kernel-da-key patch sts verification-done-bionic verification-done-xenial |
|
| 2018-09-10 17:53:06 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-09-10 17:53:06 |
Launchpad Janitor |
cve linked |
|
2018-1118 |
|
| 2018-09-10 17:53:13 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-09-10 17:54:50 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-10-06 13:30:35 |
Guillaume Penin |
bug |
|
|
added subscriber Guillaume Penin |
| 2019-07-24 21:08:31 |
Brad Figg |
tags |
azure kernel-da-key patch sts verification-done-bionic verification-done-xenial |
azure cscc kernel-da-key patch sts verification-done-bionic verification-done-xenial |
|
