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.
DescriptionDon Dutile (Red Hat)
2011-09-01 19:55:57 UTC
Description of problem:
SME review of 8/11/11 doc version, chapter 3 found these errors and/or needed corrections:
chapter 3
a) 3.1
i) first paragraph:
do we really want to say:
"This is not theoretical; attacks already exist on hypervisors."
Ask Bhavna if we really want this statement in the guide.
b) 3.2
i) first output block
remove: the output line for qemu-system-x86
-- doesn't exist on rhel6
ii) Table 3.1
The SELinux Context in column 2 overruns into Description column
text, making the latter unreadable.
Need to shrink Type column, and give SELinux Context
column sufficient space;
if need more, try shrinking Description.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
3.1
"This is not theoretical; attacks already exist on hypervisors."
Let's remove this sentence, the paragraph reads fine without this, no need to sound ominous in an admin guide.
Description of problem: SME review of 8/11/11 doc version, chapter 3 found these errors and/or needed corrections: chapter 3 a) 3.1 i) first paragraph: do we really want to say: "This is not theoretical; attacks already exist on hypervisors." Ask Bhavna if we really want this statement in the guide. b) 3.2 i) first output block remove: the output line for qemu-system-x86 -- doesn't exist on rhel6 ii) Table 3.1 The SELinux Context in column 2 overruns into Description column text, making the latter unreadable. Need to shrink Type column, and give SELinux Context column sufficient space; if need more, try shrinking Description. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: