3:34 p.m.
On Wed., Nov. 17, 2021, 4:54 a.m. Yedidyah Bar David, <didi(a)redhat.com>
wrote:
On Wed, Nov 17, 2021 at 9:44 AM Sandro Bonazzola
<sbonazzo(a)redhat.com>
wrote:
>
>
> Il giorno mer 17 nov 2021 alle ore 03:12 Danilo de Paula <
> ddepaula(a)redhat.com> ha scritto:
>
>> Since you're consuming the CentOS Stream 8 packages (I assume) and the
>> CentOS Stream 8 is actually the opened development of the next RHEL
>> minor release (8.6) [1], it makes
>> a lot of sense to open BZs against those packages in RHEL-8.6.
>>
>> Especially since we won't fix those problems in CentOS Stream without
>> fixing it in RHEL first.
>>
>> So, if you believe that this is a problem with the package itself (as it
>> looks like), I strongly suggest opening a BZ against those packages in RHEL.
>>
>
> Didi can you please open a bug against RHEL 8 CentoStream version for
> qemu-kvm component?
>
Michal searched and found:
https://gitlab.com/qemu-project/qemu/-/issues/641
And indeed it seems to be our case:
[root@ost-he-basic-suite-master-host-0 ~]# ps uaxww | grep qemu | sed 's/
/\n/g' | grep ^pcie-root-port | wc
17 17 1160
Danilo - the gitlab page above mentions several patches linking to it
already, some of which from the last few days. I didn't check them. Is
there still value in opening a bug, or is the issue already sufficiently
clear?
That's a good question.
See, we don't track gitlab issues, the upstream project does.
So, unless those patches are included in the qemu 6.2 upstream release
(should happen in a few days, I think rc1 is about to be out), they need to
be backported in RHEL (when rhel rebases). And we only do backports with
RHEL BZs.
I see some commits being mentioned but the issue is still not closed.
So wait a few days and see. If it's not fixed by rc4, then I suggest open a
BZ for the backports.
I expect the rebase to be concluded by the beginning of December btw.
That said, I failed to verify this using isa-debugcon as mentioned
there,
and the various things the command uses (FDs, storage) are temporary -
created on the fly by libvirt/vdsm - so I can't just copy the command and
add a few options. If needed I guess it's possible to hack this using a
vdsm hook or something.
For the time being, is there a workaround/temporary-build/whatever other
than downgrading to qemu-kvm-6.0.0 (which is considered deprecated, I guess
- e.g. Sandro is going to remove it from ovirt-release package (
https://github.com/oVirt/ovirt-release/pull/2 ), following the thread
"[CentOS-devel] Is advanced-virt (Virtualization SIG) not relevant anymore
with latest CentOS Stream 8?")?
>
>
>
>>
>> [1] - This is only true for CentOS Stream 8 (which is a copy of RHEL).
>> CentOS Stream 9 is the other way around.
>>
>
> Sadly no, from my experience it's still fix in rhel first and then in
> CentOS Stream, at least for systemd on CentOS Stream 9.
> I would love to see fixes coming to Stream first.
>
I understand that. Please consider that the CentOS Stream 9 development
workflow change is a bit complex and some teams are still adapting.
And I can only talk about the virt packages. MRs and fixes are landing in
stream first, the situations where they don't are highly exceptional.
Best regards,
--
Didi