Android Goldfish QEMU guest pipe
A virtual device exposed by the QEMU-based Android Emulator that lets the emulated Android guest exchange data quickly with the host machine. It is not physical hardware; it exists only inside Android Virtual Devices (AVDs) used by app developers, where it carries things like graphics, sensor, and control traffic between the emulator and the host.
recommendation
Worth keeping but document its niche because this is the fast guest-to-host communication channel used inside Android Emulator (AVD) virtual machines, not a real piece of hardware. It still receives small maintenance fixes through 2024-2025 and has no replacement, but its only real-world users are developers running Android emulators, so a comment marking it as Android-emulator-only would help future readers.
repository signals
sources
- lore.kernel.org
The driver still receives upstream touches in 2024, but the visible work is minor maintenance rather than feature development.
- lore.kernel.org
Recent mailing-list activity includes janitorial updates, indicating the code is not abandoned even if it is niche.
- cateee.net
CONFIG_GOLDFISH_PIPE remains present in current kernel series and is explicitly described as the Goldfish virtual device for QEMU pipes.
- android.googlesource.com
The device is the Android emulator's fast guest-host pipe interface, confirming it is virtual emulator infrastructure rather than sold hardware.
- developer.android.com
The Android Emulator and AVDs are still current developer-facing products in 2026, so Goldfish-style guest support remains relevant in a niche VM/emulator deployment.
codex reasoning notes (technical)
Not removable on obsolescence grounds: this is an emulator-only virtual-device driver for Android Goldfish/AVD guests, not physical hardware, so 'still sold' is false and no sale year applies. `lore_file_timeline` on drivers/platform/goldfish/goldfish_pipe.c showed touches through 2024 (and later treewide churn in 2025), with returned events dominated by small fixes/cleanups rather than active removal talk; the cited lore URLs came from that tool output. Deployment evidence came from web search results: LKDDb confirms the Kconfig symbol is still shipped; AOSP QEMU pipe docs identify the exact guest-host interface; Android Developers emulator docs confirm AVD/emulator deployments still exist today. Recommendation is `keep-annotate`: niche but still live, with low present-day deployment outside emulator/AVD environments and no clear replacement driver for the same guest-host pipe ABI.