The issue can be easily reproduce inside a LXD VM running Ubuntu 22.04, e.g.
$ lxc init ubuntu:j vm0 -c limits.cpu=4 -c limits.memory=4GiB --vm $ lxc config device override vm0 root size=80GiB $ lxc start vm0 Switch to the generic kernel first: $ lxc shell vm0 vm0$ apt-get update vm0$ env DEBIAN_FRONTEND=noninteractive apt purge -y linux-image-* linux-headers-* linux-modules-* vm0$ apt-get install -y linux-image-generic linux-headers-generic vm0$ apt-get autoremove -y vm0$ reboot Now lets setup Anbox Cloud $ lxc shell vm0 vm0$ pro attach xxx vm0$ pro enable anbox-cloud vm0$ anbox-cloud-appliance init --auto Install the -aws kernel: vm0$ apt install -y linux-image-aws linux-headers-aws linux-modules-extra-aws vm0$ reboot Once the VM is back up vm0$ anbox-cloud-appliance prepare-node-script | bash -ex # This will allow the instance to hit the issue a bit quicker vm0$ amc config set instance.security_updates false vm0$ amc launch -r --name test jammy:android13:amd64 The instance will start and trigger the faulty behavior in the kernel binder driver, you can use vm0$ dmesg -w to keep an eye on the kernel output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081745 Title: Anbox 1.23 Version Application failing To manage notifications about this bug go to: https://bugs.launchpad.net/anbox-cloud/+bug/2081745/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
