RustInQemu

For the old RustInQemu page, see RustInQemu/2022

Active effort

• Current state
• Documentation
• Roadmap: November 2024 | January 2025

Past efforts

• [RFC v3 00/32] Rust binding for QAPI and qemu-ga QMP handler examples
  on patchew on lore

Work in progress

Paolo

• Posted: Opaque<> (to split crates and also first step for annotated pinning)
• Planned: chardev
• Later: pinned_init... maybe use MaybeUninit as a first step?
• Upstream Meson: "objects:", rustdoc, -C prefer-dynamic

Manos

• Documentation

Zhao

• HPET live migration.

Kevin

• Executing async code, block driver implementations
  • https://lore.kernel.org/qemu-devel/20250211214328.640374-1-kwolf@redhat.com/

TODO

Bugs

• Integration tests are linked with libqemuutil as link_whole, which does not work when modules are enabled
  • meson seems to be buggy and does not allow using link_with instead?
  • probably best to require meson 1.8.0 anyway as it has nicer integration with clippy, and possibly rustdoc
• Add BQL abstraction for tests - avoid running them with "--test-threads 1"
• Distros would prefer to link libstd dynamically; Rust-enabled QEMU binaries are huge

Nice things to have

• run doctests with meson test
• Remove need for manual "meson subprojects update --reset" when updating packagefiles/
• Improve tool integration
  • Run code checks a la "meson test --suite codecheck"? (clippy and rustfmt)
• rustfmt currently requires nightly, decide what to do about it
• Place rustdoc output for master somewhere?
• split qemu_api into multiple crates
• more QOM procedural macros
  • generate qdev properties
  • generate parts of TypeInfo?
  • monomorphization of T: IsA<Class> to &T (like the momo crate)
• distros need dynamically linked libstd
  • rewrite all main()s in Rust and use -C prefer-dynamic?
  • or should Meson be able to link C programs with rlibs?

New code to write

• feature parity for pl011
• safe object creation with pinned_init, originating from Linux)
• complete vmstate bindings
• Generic Rust<->C interop, Error (https://github.com/bonzini/rust-qemu)
• DMA (investigate vm-memory?)
• Trace/log

Ideas for lints without breaking CI

See https://github.com/bonzini/rust-qemu/commit/95b25f7c5f4e2694a85a5503050cc98da7562c7c

• run clippy as part of "make check", possibly only if Rust is newer than some version (1.74.0 so that clippy can be configured in Cargo.toml?)
• deny many individual lints, do not deny groups (complexity, perf, style, suspicious) on regular builds. allow unknown_lints.
• add to CI a fallible job that runs on nightly clippy with -Dclippy::complexity -Dclippy::perf -Dclippy::suspicious -Dclippy::style -Dunknown_lints. the job should generally pass, and if a new lint triggers it probably should be added to Cargo.toml as either "allow" (rare) or "deny" (possibly after adding #[allow()] to the source).

Possible project targets

Miscellanea

• qemu-bridge-helper.c Re-write SUID C executable with useful features.

Devices

• hw/block/pflash_cfi01.c, hw/block/pflash_cfi02.c (claimed, WIP)
  • needs block bindings
• hw/timer/i8254.c (claimed, WIP)
• hw/mem/nvdimm.c (suggested by Manos)