RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1471284 +++

This is the BZ to track the rebase of SLOF in RHEL-7.5.

Mirek,

I know we discussed the dtc rebase, but I can't recall if we discussed this one.

I believe we should rebase to the version that's used in upstream qemu 2.12.  That's currently the tag 'qemu-slof-20171412' (yes that tag has day/month backwards - probably should have caught that when aik sent the update, but I don't think it's worth bothering with now).  It's very unlikely to change before the 2.12 release.

AIUI, you're the owner of the downstream SLOF tree, so only you can execute the actual rebase.  Do you need anything from me?

After discussion with Mirek on IRC.

I gave a quick smoke test to Mirek's rebased scratch build at:
    https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15785325

Seems to be fine.

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/RHBA-2018:3042