Hi On Thu, Sep 11, 2025 at 2:05 PM Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Mon, 8 Sept 2025 at 11:53, Paolo Bonzini <pbonz...@redhat.com> wrote: > > > > This includes: > > - bumping MSRV to 1.83.0 to support const_refs_to_static > > - Zhao's safe, builder-based implementation of migration callbacks > > - Manos's qdev properties macro. While bit-based properties are > > not yet supported, that's a small change overall. > > - the Rust crate split from Marc-André > > - adding proc macro aliases in individual crates, also from Marc-André > > > > I'm still not convinced about having "bql" depend on "migration", > > but I am convinced by the crate split between "util" and "bql", > > so we can move the implementation of VMState from "bql" to > > "migration" later if needed. > > > > For the purpose of getting this in as an easy-to-use base for future > > development, I'm disabling CI from Debian and Ubuntu. The plan is: > > - that Debian will require trixie to enable Rust usage > > - that Ubuntu will backport 1.83 to its 22.04 and 24.04 versions > > (https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2120318) > > - that Marc-André or someone else will add Rust to other CI jobs > > How far into the future does moving to 1.83.0 push our > "we can enable rust and make it mandatory" point? I was > hoping we would be able to do that sometime soon but this > sounds like we're going to be still a long way out from that :-(
I suppose most distro will want to backport a newer rust in their stable distro, like ubuntu is doing or debian with rustc-web. With that, it shouldn't be too long before we could make Rust required. fwiw, I am working on a series to enable Rust on our various CI/docker/vm. I am mostly left with issues from windows and macos .. (btw, if someone can help me investigate the linking issue on mac https://gitlab.com/marcandre.lureau/qemu/-/jobs/11301499123, perhaps a temporary ssh somewhere?) -- Marc-André Lureau
