virtme-ng currently depends on bysubox-static.  This package
was built to be used for rescue purposes, to restore a badly
damaged filesystem with no presence of initrd or a rescue
media.  For one, it was not intended to be used in regular
system initrd, it has quite some shortcoming in this context.
However, since both regular and static builds of busybox
provide the same binary ([/usr]/bin/busybox), they conflict
with each other.  So, when busybox-static is installed, it
is now used for the regular system initrd too.

virtme-ng is the only package in debian which depends on
bysubox-static.  All other packages with busybox dependency
usually depends on either regular or static build, allowing
either of them to satisfy the dependency.  So installing
reuglar busybox is enough.

But when one installs virtme-ng, you're forcing static busybox
in their system initrd.  Which is not good, becaue it is not
intended to be used there at all.

At the same time, it looks like initrd you build for qemu
(where you use busybox-static) also includes other binaries,
not just busybox.  For these binaries, regular libc.so is
needed.  So you ends up with having two libcs in that initrd,
when just one is sufficient.  I must admit I haven't studied
scripts close enough, might be I'm wrong here.

It's quite easy to handle regular build of busybox in initrd.
You need to copy the libraries it is linked to, -- for that,
there's `ldd` tool, - copy everything which starts with /
(omitting linux-vdso.so).

This long-term conflict between busybox and busybox-static
pacages should be resolved somehow (it's been a more than
two decades already).  And I'm thinking about removing
the static build of busybox entirely.  See #1147074 about
this.  Obviously, before #1147074 is fixed, we shluld fix
this issue in virtme-ng.

Thanks,

/mjt