On 5/14/2026 4:53 AM, Peter Xu wrote:
> On Mon, May 04, 2026 at 04:30:06PM +0400, Marc-André Lureau wrote:
>> 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!
>>
>> (help fix https://issues.redhat.com/browse/RHEL-131968)
>
> Copy David for virtio-mem: David, please see if you're OK with virtio-mem
> side of things; if you have time look at everything it'll be even better.
>
> Copy Chenyi: would you please check with your environment on whether you
> still hit issue with this series?
With this series along with the ongoing virtio-mem guest change[1], I can
launch the TD guest with a virtio-mem device and do the plug/unplug/replug
operations
successfully.
[1] https://lore.kernel.org/lkml/[email protected]/
