On Mon, Aug 19, 2024 at 07:29:37PM +0300, Vasyl Vavrychuk wrote: > I create VM > > debvm-create -r stable -- --architectures=armhf > > I run it > > debvm-run > > but run stucks in kernel crashing in multi_cpu_stop (see attached debvm- > run.txt).
Would you be able to retry this on debvm 0.3.2 (just uploaded to unstable, but you may run from git if you prefer)? > Note, this problem is reproducible only if host Debian is run using WSL. If I > run host Debian natively on the same machine, then debvm for armhf works fine. > > Also, x86 debvm on WSL works fine too. I'm asking you to retry, because we have an arm32-specific failure where dracut-install would fail to include virtio_blk.ko in the initramfs due to a bug in glibc fts or dracut's use of it. In order to trigger this bug, the inodes of files created by debvm-create need to exceed 32bit. On a typical tmpfs that would only happen after creating 2 billion files, but maybe the WSL environment provides large inodes to trigger this bug. Since fixing the root cause is quite difficult, debvm now includes a workaround for the particular problem. The reported symptom is somewhat different and the messages about virtio-pci also hint at a different issue, but maybe we are lucky? Thanks in advance Helmut
