Ah, sounds like the issue I was having with a new install/upgrade as well 
(https://bugzilla.redhat.com/show_bug.cgi?id=2023919 
<https://bugzilla.redhat.com/show_bug.cgi?id=2023919>)

It’s definitely affecting stream users and pretty  much any new install at the 
moment.

> On Nov 18, 2021, at 7:14 AM, Yedidyah Bar David <[email protected]> wrote:
> 
> On Thu, Nov 18, 2021 at 2:14 PM Christoph Timm <[email protected]> wrote:
>> 
>> looks like they are already aware of it:
> 
> Indeed.
> 
>> https://lists.ovirt.org/archives/list/[email protected]/thread/BDYP62MAJL2QVQZ7RHM2USZD4HXBGUA6/
> 
> Now replied there, and created this bug:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2024605
> 
> Also posted now to centos-devel, "qemu-kvm 6.1.0 with 16 PCIE root
> ports is broken".
> 
> For the time being, we know of two workarounds:
> 
> 1. Use qemu-kvm 6.0.0, available from the advanced virtualization SIG
> repo, should automatically be enabled by ovirt-release package. So
> e.g.:
> 
> Per host:
> - Move to maintenance
> - dnf downgrade qemu-kvm-core-6.0.0
> - Activate
> 
> 2. Configure your engine to use less than 16 pcie root ports, e.g. 12 like 
> here:
> 
> https://gerrit.ovirt.org/c/ovirt-system-tests/+/117689
> 
> This might be problematic, though, if you need to add many devices to your 
> VMs.
> 
> Best regards,
> 
> --
> Didi
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/NELQ5MU6I6WYLWD4DG5H3AIHWETITVGR/

Reply via email to