+++ This bug was initially created as a clone of Bug #1408808 +++ +++ This bug was initially created as a clone of Bug #1390316 +++ Two reasons: 1. Can be used by both x86 and ARM VMs 2. Add a vendor-specific pci capability to these ports, with recommended window sizes (io/mem/prefmem) for the firmware for more efficient resource allocation. Add libvirt support for the new controller.
The new controller will be selected automatically by libvirt for new setups, but ovirt should be aware the Intel Root Port is being replaced by a generic one. Not sure if there are any actual work items for this BZ.
Hi Michal, your take on this. According to comment 1, I believe we could move this to TestOnly. I don't think there are any implication for this, or do you see anything that might cause issues in Virt?
I believe this should be TestOnly as we use libvirt defaults in this regard (and we don't interfere with libvirt's idea of addressing at all).
Martin, can we delay this for 4.3 for the time being?
That's just a TestOnly BZ, so I think there is not much of an effort here. Leaving it to Maital for weighing in.
... (damn BZ edit function is missing) ... I don't think we have a real chance in avoiding the test, as this will be selected automatically by libvirt, so we need to test and check it.
Yes, we can test it.
Anything that prevents it from moving to ON_QA?
(In reply to Yaniv Kaul from comment #8) > Anything that prevents it from moving to ON_QA? Not from my side. Meital, Nisim?
note this is q35 related, not sure it makes sense to test anything until we fully productize q35 in oVirt
(In reply to Martin Tessun from comment #9) > (In reply to Yaniv Kaul from comment #8) > > Anything that prevents it from moving to ON_QA? > > Not from my side. > Meital, Nisim? Not from our side too.
Hi Michal, maybe you have some info on when q35 will be fully productized in oVirt so we could start testing? thanks.
I don't. It's a tech preview status in 4.2 AFAIK It can be tested independently though as it's "just a libvirt change" to us
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No external trackers attached] For more info please contact: rhv-devops
INFO: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [No external trackers attached] For more info please contact: rhv-devops
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync