Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1410437 - [RFE] [TestOnly] PCIe: Add Generic PCIe Root Ports
[RFE] [TestOnly] PCIe: Add Generic PCIe Root Ports
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
unspecified
All Unspecified
medium Severity low
: ovirt-4.2.0
: ---
Assigned To: Michal Skrivanek
Vitalii Yerys
: FutureFeature, TestOnly
Depends On: 1410441 1390316 1408808
Blocks: 1173755
  Show dependency treegraph
 
Reported: 2017-01-05 08:43 EST by Marcel Apfelbaum
Modified: 2018-05-15 13:40 EDT (History)
26 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: 1408808
Environment:
Last Closed: 2018-05-15 13:38:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mavital: needinfo+
vyerys: testing_plan_complete+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:40 EDT

  None (edit)
Description Marcel Apfelbaum 2017-01-05 08:43:41 EST
+++ 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.
Comment 1 Marcel Apfelbaum 2017-01-05 08:47:04 EST
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.
Comment 2 Martin Tessun 2017-03-16 04:22:39 EDT
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?
Comment 3 Martin Polednik 2017-03-16 06:02:43 EDT
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).
Comment 4 Yaniv Kaul 2017-06-06 17:35:55 EDT
Martin, can we delay this for 4.3 for the time being?
Comment 5 Martin Tessun 2017-06-07 16:36:37 EDT
That's just a TestOnly BZ, so I think there is not much of an effort here.
Leaving it to Maital for weighing in.
Comment 6 Martin Tessun 2017-06-07 16:37:51 EDT
... (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.
Comment 7 meital avital 2017-06-21 06:17:41 EDT
Yes, we can test it.
Comment 8 Yaniv Kaul 2017-07-30 04:52:33 EDT
Anything that prevents it from moving to ON_QA?
Comment 9 Martin Tessun 2017-08-03 03:00:25 EDT
(In reply to Yaniv Kaul from comment #8)
> Anything that prevents it from moving to ON_QA?

Not from my side.
Meital, Nisim?
Comment 10 Michal Skrivanek 2017-08-03 03:47:48 EDT
note this is q35 related, not sure it makes sense to test anything until we fully productize q35 in oVirt
Comment 11 meital avital 2017-09-28 07:58:02 EDT
(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.
Comment 12 Vitalii Yerys 2017-11-09 06:13:12 EST
Hi Michal, 

maybe you have some info on when q35 will be fully productized in oVirt so we could start testing? 

thanks.
Comment 13 Michal Skrivanek 2017-11-09 09:22:28 EST
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
Comment 14 RHV Bugzilla Automation and Verification Bot 2017-12-06 11:17:04 EST
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@redhat.com
Comment 15 RHV Bugzilla Automation and Verification Bot 2017-12-12 16:15:39 EST
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@redhat.com
Comment 16 RHV Bugzilla Automation and Verification Bot 2017-12-18 12:05:49 EST
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@redhat.com
Comment 19 errata-xmlrpc 2018-05-15 13:38:43 EDT
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

Note You need to log in before you can comment on or make changes to this bug.