| 128 | * While operating under the qemu chroot (ie on the host system) you may encounter 'qemu: Unsupported syscall'. Note that messages from QEMU about unsupported syscalls are often harmless, because typically they only appear for relatively new syscalls which QEMU hasn't implemented yet. The guest code will have a fallback path so it works on older kernels which don't implement the syscall, so a message is printed but the application still runs. So if the guest program is failing then it is quite likely to be for an entirely unrelated reason to the missing syscalls. |
| 129 | |
| 130 | Host specific notes: |
| 131 | * Ubuntu 16.04: |
| 132 | - **qemu: Unsupported syscall: 373**: an [https://salsa.debian.org/kernel-team/initramfs-tools/commit/b4804dd update] to initramfs-tools adds a 'sync -f' which isn't supported on qemu-2.5 used by Xenial 16.04. This is fixed in qemu-2.11 (used on Ubuntu 18.04 and beyond). This will cause initramfs updates to fail which may be used if you are trying to use a kernel needing an initramfs. To work around the issue you can comment out the 'sync -f' call in update-initramfs: |
| 133 | {{{#!bash |
| 134 | sed -i 's/sync/#sync/' /usr/sbin/update-initramfs |
| 135 | dpkg --configure -a # re-run any halted postinst scripts |
| 136 | }}} |