Re: [libvirt] New Feature: Intel MKTME Support

Hi Daniel, QEMU/KVM work is in process of completion and would be published soon for the community approval(somewhere in March). We are working closely with development team of KVM/QEMU. Meanwhile, we wanted to start the process in Libvirt community. We will submit the work status of QEMU/KVM as they are available. We are new to the Libvirt community and wanted to know more about the Libvirt design approval process, and wanted to kick start our work Question we have are 1. What is the blueprint or design template for a feature approval?. 2. Procedure and requirements for design and code approval. 3. we wanted to use Libvirt MKTME in Openstack, what are the requirements? Yes you are right, SEV and MKTME are quite different , we were just mentioning the similarities of the features. We will definitely point out if they are any overlapping in the development of these two. Thanks Karim. -----Original Message----- From: Daniel P. Berrangé [mailto:berrange@redhat.com] Sent: Monday, March 4, 2019 2:33 AM To: Carvalho, Larkins L <larkins.l.carvalho(a)intel.com&gt; Cc: libvir-list(a)redhat.com; Mohammed, Karimullah <karimullah.mohammed(a)intel.com&gt; Subject: Re: [libvirt] New Feature: Intel MKTME Support On Thu, Feb 28, 2019 at 11:16:30PM +0000, Carvalho, Larkins L wrote: Libvirt is likely dependant on QEMU / KVM to implement the low level parts of this feature. So what is the status of QEMU / KVM work in this area ? If it already exists, can you outline how it is used. I get the feeling the impl is quite different from AMD SEV, but if there's any scope to use similar/overlapping libvirt design in libvirt that is highly desirable. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|