Public bug reported:
I see a boot stall on a normal qemu/libvirt based KVM guest using an almost
fresh cloud image a stall on boot:
While live on the console I see:
[ OK ] Reached target System Time Set.
[ OK ] Finished Load AppArmor pro…s managed internally by snapd.
[* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s)
Afterwards in the console I see:
[ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp.
[DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon.
Note: Found after wondering why my system isn't available for ssh after
start
In the journal this bonus minute can be seen for example here:
Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated
successfully.
Apr 06 05:49:41 login-jammy systemd[1]:
sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job
sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out.
Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device
/sys/devices/virtual/misc/vmbus!hv_kvp.
Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP
Protocol Daemon.
Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job
hv-kvp-daemon.service/start failed with result 'dependency'.
Apr 06 05:49:41 login-jammy systemd[1]:
sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job
sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result
'timeout'.
Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job
(pre-networking)...
This behavior is from:
/usr/lib/systemd/system/hv-kvp-daemon.service
$ dpkg -S hv-kvp-daemon.service
linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service
It has the expected "should not matter elsewhere":
ConditionVirtualization=microsoft
ConditionKernelCommandLine=!snapd_recovery_mode
But it also has:
BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device
Right now it seems the latter overrules the former (in an obvious non microsoft
environment it does run and wait) and thereby makes it stall boot until it
gives up on it.
This is on my system since I wanted to do performance checks for
something completely else and is part of linux-cloud-tools-common which I had
installed for perf.
Repro:
1. get jammy system
2. install linux-cloud-tools-common
3. reboot and see the delay
I'd expect this stalls boot everywhere except when on azure, but I still
need to try that to confirm it.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-cloud-tools-common 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Apr 6 05:48 seq
crw-rw---- 1 root audio 116, 33 Apr 6 05:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed Apr 6 09:04:02 2022
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
PackageArchitecture: all
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic
root=UUID=16484d8a-587c-4c41-9201-e6079b9c6938 ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.15.0-25-generic N/A
linux-backports-modules-5.15.0-25-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.14.0-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-impish
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-impish:cvnQEMU:ct1:cvrpc-q35-impish:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-impish
dmi.sys.vendor: QEMU
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug jammy uec-images
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968013
Title:
Boot stall on non-azure systems due to linux-cloud-tools-common
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968013/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
