Control: tag -1 + confirmed help Control: severity -1 minor
31.05.2022 10:44, Johannes Schauer Marin Rodrigues wrote:
Source: qemu Version: 1:7.0+dfsg-7 Severity: normal X-Debbugs-Cc: jo...@debian.org Hi, thanks a lot for your help with #1011003, much appreciated. With the `-cpu host` flag I now have a working workaround. Unfortunately I just
That bug still needs to be fixed though.
stumbled across another strange problem which I'm again able to reproduce inside QEMU with qemu-user-mode emulation. Have a look at this log file: https://jenkins.debian.net/job/fakeroot-foreign-worker/645/consoleText And search for "apt-get remove --yes qemu-user-static binfmt-support qemu-user". This used to successfully remove qemu-user support from the virtual machine. As you can see from a few lines below, running mmdebstrap --architectures=arm64 [...] succeeds. Why? Is this because I'm now running qemu with "-cpu host"? Or is this due to another change in qemu-user from recently?
It has nothing to do with -cpu host. It is due to the fact that I switched from binfmt-support to systemd for binfmt registration (actually the two work in parallel). And systemd does not provide an official way to trigger binfmt (de)registration besides a reboot. And in systemd, the service (systemd-binfmt.service) is described as "early boot service". Maybe I can run /lib/systemd/systemd-binfmt explicitly but this does not look like a good thing to do. And I don't see any way to remove registered formats which are not there anymore. It is actually the same for *installing* qemu-user - without binfmt-support it will not register its binfmts until reboot. /mjt
