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.
Created attachment 1301150[details]
Update virt-what to detect AWS via dmidecode data.
> Description of problem:
Current virt-what just shows up 'xen,xen-hvm' on Amazon AWS platform. A little patch can help to detect these systems.
> Version-Release number of selected component (if applicable):
virt-what-1.13-8.el7.x86_64 or latest upstream
> How reproducible:
Always
> Steps to Reproduce:
1. Start AWS instance.
2. Run virt-what as root
> Actual results:
Returned output:
xen
xen-hvm
> Expected results:
Output can be:
xen
xen-hvm
aws
> Additional info:
Please kindly check the patch in the attachment.
Comment 2Richard W.M. Jones
2017-07-19 15:40:27 UTC
Can reproduce this bug with :
virt-what-1.13-10.el7.x86_64
Steps:
1. Apply for a AWS account and start an rhel7.4 instance
2.
# sudo virt-what
xen
xen-hvm
Verified with packages:
virt-what-1.18-4.el7.x86_64
Steps:
1. Apply for a AWS account and start an rhel7.5 instance
2.
# sudo virt-what
xen
xen-hvm
aws
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:0896