Debian Patches
Status for virtme-ng/1.38-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| increase-udev-timeout.patch | [PATCH] virtme-init: Increase timeout for udevadm settle By default, udevadm has a 2 minutes timeout: https://github.com/systemd/systemd/blob/main/src/udev/udevadm-settle.c#L27 This is more than enough for a normal system, but when running inside a virtual machine without kvm this timeout might not be enough. Media-ci has seen a spike of this errors: [ 174.273649] virtme-init: waiting for udev to settle Failed to wait for daemon to reply: Connection timed out [ 296.460652] virtme-init: udev is done [ 300.023643] ip (123) used greatest stack depth: 11808 bytes left dmesg(1) may have more information after failed mount system call. https://gitlab.freedesktop.org/linux-media/users/ci/-/jobs/85882743 When it works, it requires around 100+ seconds to settle: [ 124.949429] virtme-init: waiting for udev to settle [ 227.774217] udevadm (136) used greatest stack depth: 11680 bytes left [ 227.787152] virtme-init: udev is done In theory we could even have --timeout=infinity, but that could break other use-cases. |
Ricardo Ribalda <ribalda@chromium.org> | no | 2025-10-13 |