On Wed, Nov 17, 2021 at 2:34 PM Danilo de Paula <ddepaula@redhat.com> wrote:
On Wed., Nov. 17, 2021, 4:54 a.m. Yedidyah Bar David, <didi@redhat.com> wrote:
On Wed, Nov 17, 2021 at 9:44 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 17 nov 2021 alle ore 03:12 Danilo de Paula <ddepaula@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.
Thanks. Now filed this Stream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2024605 IMO waiting till beginning of Dec is too late. We already got a few reports on the users list by people hitting this. If it's too much work to fix/revert, perhaps consider excluding this on centos-release package, repo, whatever. Thanks! -- Didi