Bug 1312431

Summary:	Add support for detecting ppc64 LPAR as virt guests
Product:	Red Hat Enterprise Linux 6	Reporter:	Adrian Likins <alikins>
Component:	virt-what	Assignee:	Richard W.M. Jones <rjones>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:	Yehuda Zimmerman <yzimmerm>
Priority:	high
Version:	6.8	CC:	ailan, alemay, alikins, asaha, dgibson, jherrman, jsuchane, jwildman, leiwang, linl, ncoghlan, ptoscano, rbalakri, rjones, virt-bugs, xchen
Target Milestone:	rc	Keywords:	Reopened
Target Release:	6.8
Hardware:	ppc64
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1072524	Environment:
Last Closed:	2017-03-21 11:28:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1072524
Bug Blocks:	1151596, 1269194, 1301891, 1359965, 1364808

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