Bug 1312431 - Add support for detecting ppc64 LPAR as virt guests
Summary: Add support for detecting ppc64 LPAR as virt guests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-what
Version: 6.8
Hardware: ppc64
OS: Unspecified
high
unspecified
Target Milestone: rc
: 6.8
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
Yehuda Zimmerman
URL:
Whiteboard:
Depends On: 1072524
Blocks: rhsm-ppc64 1269194 1301891 1359965 1364808
TreeView+ depends on / blocked
 
Reported: 2016-02-26 16:47 UTC by Adrian Likins
Modified: 2019-11-14 07:30 UTC (History)
16 users (show)

Fixed In Version: virt-what-1.11-1.3.el6
Doc Type: Bug Fix
Doc Text:
"virt-what" now detects IBM POWER LPARs Previously, the "virt-what" utility did not recognize if the current system was running in an IBM POWER logical partition (LPAR). As a result, the *subscription-manager* utility displayed misleading licensing information for guest virtual machines running in an IBM POWER LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER LPAR. As a result, *subscription-manager* now provides correct subscription information in this scenario.
Clone Of: 1072524
Environment:
Last Closed: 2017-03-21 11:28:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0748 0 normal SHIPPED_LIVE virt-what bug fix update 2017-03-21 12:45:31 UTC

Comment 4 Bin Han 2016-11-02 01:45:09 UTC 
Packager version:
virt-what-1.11-1.3.el6.ppc64


Steps：
1.prepare a lpar ppc4 system with RHEL6.9
2.Update the virt-what to the latest version
3.Run "Virt-what" 

Result:
[root@ibm-p730-03-lp1 ~]# virt-what
ibm_power-lpar_shared

So verified.
Comment 10 errata-xmlrpc 2017-03-21 11:28:43 UTC 
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://rhn.redhat.com/errata/RHBA-2017-0748.html
Note You need to log in before you can comment on or make changes to this bug.