The bug has been fixed in v5.14-rc1[1] and backported to the stable
kernels: 5.13.2, 5.12.17 and 5.10.50.

The newest archiso (shipped today) ships with 5.13.6.

[1] https://github.com/torvalds/linux/commit/2b9ac22b12a266eb4fec246a07b504dd4983b16b

Fix #139

This reverts commit 316d0523.

Downgrade to util-linux v2.36 to workaround kernel bug

Closes #138

See merge request archlinux/arch-boxes!171

losetup (>=2.37)[1] uses the LOOP_CONFIGURE ioctl which discard support
is broken[2].

[1] https://github.com/karelzak/util-linux/pull/1152
[2] https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.14/drivers&id=2b9ac22b12a266eb4fec246a07b504dd4983b16b

Fix #138

netctl isn't used since Vagrant v2.2.10[1][2] and the users has been
given a fair chance to update now (>9 months).

Fix #112

[1] https://github.com/hashicorp/vagrant/blob/ee2a5daceec7f18accc59a69b84ced299a219188/CHANGELOG.md#2210-august-24-2020
[2] https://github.com/hashicorp/vagrant/pull/11400

[1] archlinux/infrastructure!335

Fix shellcheck complains due to new version

See merge request archlinux/arch-boxes!169

Shellcheck v0.7.2[1] added more checks resulting in the following
complains in our case:
In build-host.sh line 12:
  readonly TMPDIR="$(mktemp --dry-run --directory --tmpdir="${PWD}/tmp")"
           ^----^ SC2155: Declare and assign separately to avoid masking return values.
In build-inside-vm.sh line 16:
  readonly TMPDIR="$(mktemp --dry-run --directory --tmpdir="${PWD}/tmp")"
           ^----^ SC2155: Declare and assign separately to avoid masking return values.
In build-inside-vm.sh line 19:
    chown "${SUDO_UID}:${SUDO_GID}" "${OUTPUT}" "${TMPDIR}"
                       ^---------^ SC2153: Possible misspelling: SUDO_GID may not be assigned, but SUDO_UID is.

[1] https://github.com/koalaman/shellcheck/blob/331e89be990547b6e21ad1b6e56065bcda1ba053/CHANGELOG.md#v072---2021-04-19

Refer to the ArchWiki for tested cloud providers and instructions

Closes #133

See merge request archlinux/arch-boxes!168

Fix #133

Remove haveged

See merge request archlinux/arch-boxes!167

haveged was presumably added to increase entropy and prevent entropy
starvation.

A few things has changed since, most notable:
* the kernel actively tries to add entropy (jitter entropy)[1][2][3][4]
* /dev/random no longer blocks after CRNG initialization[5][6]

[1] https://github.com/torvalds/linux/commit/3f2dc2798b81531fd93a3b9b7c39da47ec689e55
[2] https://github.com/torvalds/linux/commit/50ee7529ec4500c88f8664560770a7a1b65db72b
[3] https://lore.kernel.org/lkml/alpine.DEB.2.21.1909290010500.2636@nanos.tec.linutronix.de/T/
[4] https://lwn.net/Articles/800509/
[5] https://github.com/torvalds/linux/commit/30c08efec8884fb106b8e57094baa51bb4c44e32
[6] https://lwn.net/Articles/808575/

Don't use the secure runner on forks

See merge request archlinux/arch-boxes!166

The jobs will get stuck as the secure runner is only enabled for the
archlinux group.

Cleanup README

Closes #134

See merge request archlinux/arch-boxes!165

Fix #134

Fix partial upgrade in the guest

Closes #136

See merge request archlinux/arch-boxes!164

A partial upgrade is often a bad idea and can cause issue like:
qemu-img: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by qemu-img)

cow_spacesize is bumped as upgrading can use a lot of storage.

linux is ignored as we need the kernel modules for the current kernel to
be available.

Fix #136

Don't set initramfs compression to zstd as it's the default now[1]

See merge request archlinux/arch-boxes!163

[1] https://archlinux.org/news/moving-to-zstandard-images-by-default-on-mkinitcpio/

Dynamic allocation for file descriptors used in ./build-host.sh

Closes #135

See merge request archlinux/arch-boxes!162

Visual studio code had an issue with file descriptors already used by the integrated terminal.
This commit asks bash to dynamically assign a "free" file descriptor to be used in the expect function.
Closes #135

Make disk size configurable per image

Closes #127

See merge request archlinux/arch-boxes!160

It is meant for local usage so the disk should be "big enough".

cloud-init resizes the disk[1] so we don't need a "big disk" with a lot
of unused space + some cloud providers charges for the unused space +
some cloud providers offers VM with disk < 20GB.

[1] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart

Fix #127

Use the fast fast-single-thread runner when using qemu for testing

See merge request archlinux/arch-boxes!161

The fast-single-thread runner is much faster (test-cloudimg-qemu):
3min 39sec[1] vs 8min 37sec[2]

[1] https://gitlab.archlinux.org/klausenbusk/arch-boxes/-/jobs/14739
[2] https://gitlab.archlinux.org/klausenbusk/arch-boxes/-/jobs/14746

Add basic image

See merge request archlinux/arch-boxes!158

It is similar to the cloud-image but it comes with a preconfigured arch
user (pw: arch) and lacks cloud-init.

Use --reflink=always when copying the fallback initramfs

See merge request archlinux/arch-boxes!159

It saves us ~20MB.