On Thu, Feb 26, 2026 at 02:59:45PM +0100, [email protected] wrote: > From: Marc-André Lureau <[email protected]> > > Hi, > > This is an attempt to fix the incompatibility of virtio-mem with confidential > VMs. The solution implements what was discussed earlier with D. Hildenbrand: > https://patchwork.ozlabs.org/project/qemu-devel/patch/[email protected]/#3502238 > > The first patches are misc cleanups. Then some code refactoring to have split > a > manager/source. And finally, the manager learns to deal with multiple sources. > > I haven't done thorough testing. I only launched a SEV guest with a virtio-mem > device. It would be nice to have more tests for those scenarios with > VFIO/virtio-mem/confvm.. In any case, review & testing needed! > > (should fix https://issues.redhat.com/browse/RHEL-131968)
Hi, Marc-André, Just FYI that this series fails some CI tests: https://gitlab.com/peterx/qemu/-/pipelines/2361780109 Frankly I don't yet know on why rust fails with this, maybe you have better idea.. So I'll leave that to you.. ===8<=== error: unused import: `InterfaceClass` --> rust/bindings/system-sys/libsystem_sys.rlib.p/structured/lib.rs:23:15 | 23 | use qom_sys::{InterfaceClass, Object, ObjectClass}; | ^^^^^^^^^^^^^^ | = note: `-D unused-imports` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_imports)]` error: aborting due to 1 previous error ===8<=== The other thing is this series will generate tons of checkpatch issues, almost only line width issues and unmaintained files, so they're trivial. It seems to me it'll be nice if this series can land 11.0. We have one more week. Please take a look when repost, thanks! -- Peter Xu
