Control: reassign -1 dracut-install Control: forcemerge 1079031 -1 Control: affects 1079031 + debvm
On Mon, Aug 19, 2024 at 04:25:27PM +0300, Vasyl Vavrychuk wrote: > Package: debvm Thank you for following my request and taking it to bugs.debian.org. > Severity: grave Please use severities sensibly. Refer to https://www.debian.org/Bugs/Developer#severities for details. The grave severity should only be applied if most uses of the package in question fail. Whilst it fails in the default configuration for you, that happens to be unstable and unstable is known to be broken at times. > Justification: renders package unusable Consider whether that really is likely. I sent you a link to CI logs earlier. The package may be unusable to you, but a grave severity needs an indication that it likely fails for everyone. > I have installed dependencies > > apt install arch-test dpkg-dev e2fsprogs mmdebstrap qemu-system-x86 > uidmap Note that reportbug also generates this information in what it appens to the bug report. > Got debvm version 83876f58901900ab59dc2aec3027d2d36723a446 from Git. Thanks for pinning down the environment precisely this time around. > Create VM > > bin/debvm-create > > But run VM fails > > $ bin/debvm-run > ... > Begin: Running /scripts/local-block ... done. > done. > Gave up waiting for root file system device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Missing modules (cat /proc/modules; ls /dev) > ALERT! LABEL=debvm does not exist. Dropping to a shell! > (initramfs) Thanks for also attaching precise logs. The detail you provided makes debugging this feasible. From the debvm-run log, I can see that the kernel did not detect any disks. It seems likely that the virtio-blk driver was not loaded as there is no trace of it working. Looking into the debvm-create log, we can spot something more worrying: > Setting up initramfs-tools (0.143.1) ... > update-initramfs: deferring update (trigger activated) > Setting up linux-image-6.10.4-cloud-amd64 (6.10.4-1) ... > I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.10.4-cloud-amd64 > I: /initrd.img.old is now a symlink to boot/initrd.img-6.10.4-cloud-amd64 > I: /vmlinuz is now a symlink to boot/vmlinuz-6.10.4-cloud-amd64 > I: /initrd.img is now a symlink to boot/initrd.img-6.10.4-cloud-amd64 > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-6.10.4-cloud-amd64 > W: No zstd in /usr/bin:/sbin:/bin, using gzip > /usr/lib/dracut/dracut-install: symbol lookup error: > /usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, > version LIBKMOD_5 > W: Couldn't identify type of root file system for fsck hook > /usr/lib/dracut/dracut-install: symbol lookup error: > /usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, > version LIBKMOD_5 This is a problem in dracut. There already is a bug for it #1079031. I'm merging the reports. Helmut
