I have reproduced a similar (I guess) issue when running Debian natively (without WSL). For that, I first run x86 VM, but ensure it has enough disk and memory:
debvm-create --release=stable --size=5T debvm-run -- -m 2G Then, from x86 VM I create and run arm VM similarly to how I do this from WSL: debvm-create -- --architectures=armhf && debvm-run I observed multiple backtraces printed from the kernel (debvm-run.log attached) and could not reach the console. Experimentally, I found this can be worked around by passing fewer CPUs to QEMU: debvm-run -- -smp 7 - is enough on native Debian > x86 debvm debvm-run -- -smp 4 - is needed on WSL (I have 8 cores in total) On Mon, Aug 19, 2024 at 10:51 PM Helmut Grohne <hel...@subdivi.de> wrote: > > 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. > > Thank you for the report along with good detail. Given that reproducing > the bug requires the use of non-free software, I do not intend to work > on it. For this reason, I am marking it as unreproducible. > > If you or someone else wants to work on it, please mark your self as > owner of the bug. I expect that this is not a bug in debvm, but in some > other component (e.g. linux or qemu). Please reassign as appropriate and > remove the unreproducible tag once it is better understood. > > Helmut >
debvm-run.log
Description: Binary data
