Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
This bz will be used to confirm with PM what kind of tier2 guest will be supported for x86KVM and powerKVM in rhel7.4 and also record the test effort later.
Here is what we supported for previous release:
X86 : SLES 12 SP1 and SLES 11 SP4(32/64)
Power : SLES 12 SP1 and SLES 11 SP4 BE
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
(In reply to juzhang from comment #1)
> Hi Martin,
>
> Could you confirm the tier2 guests in RHEL7.4?
>
> Best Regards,
> Junyi
Just some small changes as SLES has released new Service Packs:
X86 : SLES 12 SP2 and SLES 11 SP4(32/64)
Power : SLES 12 SP1 and SLES 11 SP4 BE
Not sure there is a SP2 for Power, as SUSE does not state SPs for Power on their Website.
(In reply to Martin Tessun from comment #3)
> (In reply to juzhang from comment #1)
> > Hi Martin,
> >
> > Could you confirm the tier2 guests in RHEL7.4?
> >
> > Best Regards,
> > Junyi
>
> Just some small changes as SLES has released new Service Packs:
>
> X86 : SLES 12 SP2 and SLES 11 SP4(32/64)
> Power : SLES 12 SP1 and SLES 11 SP4 BE
>
> Not sure there is a SP2 for Power, as SUSE does not state SPs for Power on
> their Website.
Thanks Martin.
Hi Chayang and Qzhang,
Please pay attention to our tier2 guests when we do rhel7.4 testing.
Best Regards,
Junyi
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/RHSA-2017:2392
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/RHSA-2017:2392
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/RHSA-2017:2392
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/RHSA-2017:2392
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/RHSA-2017:2392