| Age | Commit message (Collapse) | Author |
|---|
|
Why?
genext2fs is slow. It has O(n^2) behaviour, which becomes annoying with
larger filesystems. It also creates an ext2 image and we have to upgrade
it to ext4 in multiple steps. Even then, the image has an inode size of
128, which is incompatible with 2038 and does not allow storing
sub-second precision time stamps.
How?
We use mkfs.ext4 from e2fsprogs (which is required anyway) instead.
Running this from within a --customize-hook does not work, because the
user namespace used for the hook often has no privileges to write to the
output image. Instead, we now ask mmdebstrap to output to a directory
and create the filesystem separately. We construct a special namespace
that has both access to the tree and to the output image and perform the
mkfs.ext4 there. As a consequence, we no longer support any mode but
unshare and since mkfs.ext4 consumes the size parameter, the size syntax
is reduced a bit.
|
|
Fix a syntax error in control.
Fixes: 1c98a5b3b36f ("bin/debvm-run: qemu (>> 1:8.0) provides symlinks for qemu-system-${debarch} as well as qemu-system-any")
|
|
as well as qemu-system-any
|
|
|
|
We completely treat all 32bit arm as armhf now. Booting the rpi kernel
installed by debvm-create for armel will not work at all. The only sane
way to boot armel is to enable a multiarch kernel.
Refine the VMARCH guess from /bin/true using the file output for the
kernel image for the common cases of i386+amd64 and armel/armhf+arm64.
|
|
|
|
This is a workaround for https://bugs.debian.org/1029309
|
|
* ppc64el needs seabios for vgabios-stdvga.bin
* We need ipxe-qemu for -device virtio-net-pci,netdev=net0
|
|
|
|
|
|
systemd-binfmt implements what we need here and that's what most users
will have, so only recommend binfmt-support when systemd is missing.
Reported-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
|
|
We really are using 1.3.0 features already.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Notably missing:
* manual pages
* autopkgtests
|
