Hi @paelzer, what I had done was testing "netlink RTM_SETLINK command" against the latest git source of qemu (around July 2020), and seeing that self-compiled version from the source worked fine. I had never seen a working Ubuntu qemu-user-static package that can start an armhf container on an amd64 host... I just saw "fix released" status, so I assumed someone verified the Ubuntu package...
If an urgent fix is not required (I think nobody complains this issue here so very few people seem to use LXC/systemd-nspawn containers of armhf on amd64, which is in my opinion convenient for testing Raspberry Pi SD card images), then we can just wait the official release of qemu 5.1, which should not have this issue... If fix of this issue is important (I am doubting if it is), then https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606 still exists in qemu-user-static 1:4.2-3ubuntu6.3 in focal-updates, armhf container cannot be used on amd64 Focal host, and a fix in Focal is desirable. I cannot see if this issue #LP1890881 exists in Focal or not as #LP1887606 suppress this issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
