On 04/23/21 19:36, Pavel Hrdina wrote: > On Fri, Apr 23, 2021 at 03:06:49PM +0200, Laszlo Ersek wrote: >> On 04/23/21 15:01, Pavel Hrdina wrote: >>> On Fri, Apr 23, 2021 at 02:34:02PM +0200, Laszlo Ersek wrote: >>>> On 04/23/21 12:31, Pavel Hrdina wrote: >>>>> On Fri, Apr 23, 2021 at 10:16:24AM +0200, Michal Privoznik wrote: >>>>>> On 4/22/21 4:13 PM, Laszlo Ersek wrote: >>>>>>> On 04/21/21 13:51, Pavel Hrdina wrote: >>>> >>>>>>> Should we file a libvirtd Feature Request (where?) for recognizing the >>>>>>> @amd-sev-es feature flag? >>>>>> >>>>>> Yes, we should. We can use RedHat bugzilla for that. Laszlo - do you >>>>>> want to >>>>>> do it yourself or shall I help you with that? >>>>> >>>>> This BZ looks like it's already tracking support for amd-sev-es [1]. >>>>> >>>>> Pavel. >>>>> >>>>> [1] <https://bugzilla.redhat.com/show_bug.cgi?id=1895035> >>>> >>>> That's a private RHBZ that tracks SEV-ES for a product that is different >>>> from "libvirt upstream". >>> >>> I didn't notice that's a private RHBZ, thanks for pointing it out. >>> >>> For upstream libvirt we no longer use RHBZ to track RFEs/BZs, we use >>> gitlab issues so if we want to track the work in upstream as well I can >>> create a new issue. >> >> Heh, I suspected I was missing something there :) Yes, please, if you or >> Michal could create a new issue in gitlab, that would be great. > > I've created a new libvirt issue [1], hopefully the description makes > sense. :) > > Pavel > > [1] <https://gitlab.com/libvirt/libvirt/-/issues/156>
Looks good to me, thank you! Laszlo
