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 Kernel Packages, which is subscribed to linux-aws-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2081745 Title: Anbox 1.23 Version Application failing Status in Anbox Cloud: In Progress Status in linux-aws-6.8 package in Ubuntu: New Bug description: Hi Team, I recently deployed the latest version of Anbox on AWS and encountered several issues during the application setup: 1.The instance is responding very slowly. 2.Upon checking the serial console logs, I found the following errors: yaml Copy code [ 1587.721879] binder_linux: 72068: binder_alloc_buf, no vma [ 1587.748032] binder_linux: 72068: binder_alloc_buf, no vma [ 1587.777123] binder_linux: 72068: binder_alloc_buf, no vma [ 1591.774328] binder_alloc_new_buf: 348 callbacks suppressed [ 1591.774333] binder_linux: 72068: binder_alloc_buf, no vma [ 1591.820201] binder_debug: 706 callbacks suppressed [ 1591.820202] binder_linux: cannot allocate buffer: vma cleared, target dead or dying [ 1591.843000] binder_linux: 74645:74645 transaction call to 72068:0 failed 19034/29189/-3, size 0-0 line 3253 [ 1591.926911] binder_linux: 72068: binder_alloc_buf, no vma [ 1591.952585] binder_linux: cannot allocate buffer: vma cleared, target dead or dying [ 1591.952588] binder_linux: 74647:74647 transaction call to 72068:0 failed 19035/29189/-3, size 0-0 line 3253 [ 1592.035897] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.061996] binder_linux: cannot allocate buffer: vma cleared, target dead or dying [ 1592.061999] binder_linux: 73114:73114 transaction call to 72068:0 failed 19036/29189/-3, size 0-0 line 3253 [ 1592.145473] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.171126] binder_linux: cannot allocate buffer: vma cleared, target dead or dying [ 1592.171129] binder_linux: 79431:79431 transaction call to 72068:0 failed 19037/29189/-3, size 0-0 line 3253 [ 1592.254447] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.280506] binder_linux: cannot allocate buffer: vma cleared, target dead or dying [ 1592.280507] binder_linux: 74623:74623 transaction call to 72068:0 failed 19038/29189/-3, size 0-0 line 3253 [ 1592.363856] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.389666] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.415762] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.444104] binder_linux: 72068: binder_alloc_buf, no vma [ 1592.467334] binder_li 3. The application is stuck in initialization mode. To manage notifications about this bug go to: https://bugs.launchpad.net/anbox-cloud/+bug/2081745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
