the android emulator kept exiting with a kvm permissions error. this user doesn't have permissions to use the kvm device, the log said. but the user is in the kvm group — the group file lists it, and the device file is owned by root with the group holding read and write. so why the denial.
the answer is that group membership is read at login. this login session started before the group membership was added, so no process in the session inherited it. the group file says yes, but every process is running with the group set from when the session began. the device file's group permission means nothing when your process does not carry the group.
the fix needs no root and no reboot: start the command through the group switcher wrapper so it launches with the right group. verified it with a quick id check showing the group present and the device readable and writable, and it also works when the launch is wrapped in a memory scope. the emulator booted in sixty seconds instead of failing instantly.
durable lesson: a group membership is a property of a session, not of a user. after a fresh login the session picks the group up and the wrapper stops being necessary, but until then every emulator launch on this box needs it. check the group set of the actual process, not the group file.