Skip to content

A rootless Android app that boots Alpine Linux: run containers (Podman/Docker/LXC) and GUI desktop apps.

docs: broaden AVF device framing and document in-app boot-failure recovery

ExTv69f285cff45f
diff --git a/README.md b/README.md
index 5ded10f..d6cb425 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ A real Alpine Linux VM with its own kernel - not a chroot or proot trick - so ro
## What you get
- **Podman, Docker and LXC** - rootless, pre-installed, ready the moment it boots
-- **A real VM** - Alpine Linux on a custom kernel via QEMU, or hardware-accelerated AVF on Pixel
+- **A real VM** - Alpine Linux on a custom kernel via QEMU, or hardware-accelerated AVF on supported pKVM devices
- **In-app terminal** - full xterm-256color, 122 color themes, 13 fonts, live resize
- **X11 desktop** - run GUI Linux apps in a built-in viewer with touch, keyboard, mouse and audio
- **USB passthrough**, **SSH**, **port forwarding** and a **guest-to-Android bridge**
diff --git a/docs/guide/backends.html b/docs/guide/backends.html
index f3b5a9b..fc22c3a 100644
--- a/docs/guide/backends.html
+++ b/docs/guide/backends.html
@@ -164,8 +164,8 @@
</table>
<div class="callout warn">
- <span class="label">AVF boot failures on some Pixel 8 / 8a / 9 units</span>
- <p>Some Pixel 8, Pixel 8a, and Pixel 9 units reboot the device during AVF VM startup. This appears to be a pKVM firmware issue on certain builds. If AVF causes a reboot, switch the backend to <strong>QEMU (TCG)</strong> in Settings &rarr; Advanced. QEMU is the reliable fallback on all devices. See <a href="limitations.html">Limitations &amp; troubleshooting</a> for the current status.</p>
+ <span class="label">AVF boot failures with multiple vCPUs on some units</span>
+ <p>On some units (notably certain Pixel 8 / 8a / 9 builds) the guest fails to boot under AVF when more than one vCPU is used - the all-cores topology trips secondary-CPU bringup early in boot on those hypervisors, before any console output appears. Podroid now detects an AVF guest that fails to boot and offers in-app recovery: <strong>Use 1 core</strong> - which boots successfully on the affected units - or <strong>Switch to QEMU</strong>. You can also set CPU cores to 1 in Settings &rarr; Advanced beforehand. QEMU (TCG) remains the reliable fallback on all devices. See <a href="limitations.html">Limitations &amp; troubleshooting</a> for the current status.</p>
</div>
<div class="pagenav">