This bug is awaiting verification that the linux-nvidia- tegra/6.8.0-1003.3 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-done-noble-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-failed-noble-linux-nvidia-tegra'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2091744 Title: When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Status in linux source package in Plucky: Fix Released Bug description: SRU Justification [Impact] Re-opening for Noble, Oracular, and current development cycle (Plucky) as this appears to have accidentally been dropped. * Previous LP bug: https://bugs.launchpad.net/bugs/2024900 * Commit from Jammy release: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/debian/linux-cloud- tools-common.hv-kvp-daemon.service?h=master- next&id=7da99ea3a1a745f6fd0c8632ef89573437888af6 * Previous mailing list discussion: https://lists.ubuntu.com/archives/kernel-team/2023-June/140646.html Following description copied from original LP bug: If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
