Use it with eyes open

Known limits are part of the product.

Current limitations, unverified combinations and practical recovery guidance for VMBook 0.1.

Captured VMBook interface for VMBook Known Issues
Captured VMBook interface · view the complete gallery and evidence note

Release maturity

VMBook 0.1 is early. Windows 11 and Debian hosts have the strongest current evidence. A public macOS desktop package has not been published.

Guest and graphics limits

The current evidence records Android-x86 requiring a plain VGA device in the tested configuration; virtio graphics without 3D reached only a text console. Multi-display and general 3D acceleration are planned engineering work, not a shipped universal capability.

  • Do not assume a guest driver exists for every architecture
  • Use a compatibility display profile for installation and recovery
  • Retain another console path before experimenting with GPU passthrough
VMBook technical interface related to VMBook Known Issues
Captured interface from the current VMBook build; test status is documented separately.

Imported appliances

A VMware Photon OS appliance was imported successfully but its VMware-specific kernel did not start under QEMU hardware. Successful import does not guarantee that a guest kernel supports the destination virtual hardware.

Hibernation and command identity

A hibernated Windows machine must wake with the command on which it slept. VMBook retains that command; changing virtual hardware beneath a hibernated guest can still be unsafe.

Report a reproducible issue

Include the VMBook version, host OS, QEMU version, guest architecture, relevant machine settings, exact error and whether the disk is a disposable copy. Never email passwords, tokens or private keys.

Email [email protected]