Package: autopkgtest Version: 5.28 Severity: normal I get this warning when building packages with the autopkgtest sbuild-qemu backend:
qemu-system-x86_64: warning: 9p: degraded performance: a reasonable high msize sho. It looks like this is an upstream issue, but I wonder if we might not be able to do some better tweaking for this. This is discussed here upstream: https://wiki.qemu.org/Documentation/9psetup#Performance_Considerations_(msize) where they suggest changing from the default 128KiB to tens of *megabytes*. The example uses: msize=104857600 which is 100 megs, if i'm not mistaken. -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-5-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.5.6 ii libdpkg-perl 1.21.20 ii procps 2:4.0.2-3 ii python3 3.11.2-1 ii python3-debian 0.1.49 Versions of packages autopkgtest recommends: ii autodep8 0.28 ii fakeroot 1.29-1 Versions of packages autopkgtest suggests: pn docker.io <none> pn fakemachine <none> pn lxc <none> pn lxd <none> ii ovmf 2022.11-2 pn ovmf-ia32 <none> ii podman 4.3.1+ds1-5+b2 ii python3-distro-info 1.5 ii qemu-efi-aarch64 2022.11-2 ii qemu-efi-arm 2022.11-2 pn qemu-system <none> ii qemu-utils 1:7.2+dfsg-4 ii schroot 1.6.13-3+b1 ii util-linux 2.38.1-5 ii vmdb2 0.26-2 ii zerofree 1.1.1-1 -- no debconf information