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.

Bug 679146

Summary:	manpage boot priority magic
Product:	Red Hat Enterprise Linux 6	Reporter:	Lubos Kocman <lkocman>
Component:	qemu-kvm	Assignee:	Gleb Natapov <gleb>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.1	CC:	juzhang, knoel, mkenneth, tburke, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-12 18:32:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lubos Kocman 2011-02-21 17:55:23 UTC

Description of problem:

 -boot [order=drives][,once=drives][,menu=on|off]
           Specify boot order drives as a string of drive letters. Valid drive
           letters depend on the target achitecture. The x86 PC uses: a, b
           (floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p
           (Etherboot from network adapter 1-4), hard disk boot is the
           default. To apply a particular boot order only on the first
           startup, specify it via once.


Exactly:  n-p
           (Etherboot from network adapter 1-4)

n .. 1
o .. 2
? .. 3
p .. 4

What kind of alphabet are u using? I guess that it should be n-q right?


Version-Release number of selected component (if applicable):

qemu-kvm-0.12.1.2-2.147.el6.x86_64

How reproducible:


Steps to Reproduce:
1. man qemu-kvm
2.
3.
  
Actual results:

a hidden letter

Expected results:

valid range

Additional info:

Comment 1 Lubos Kocman 2011-02-21 18:00:30 UTC

<danpb> 
if (*p < 'a' || *p > 'p') {
            fprintf(stderr, "Invalid boot device '%c'\n", *p);
             exit(1);
}

Seems like the the MAXVALUE is 'p'

Comment 4 Lubos Kocman 2011-06-10 07:52:47 UTC

Is this ok or are we going to do something about it?

Comment 5 Gleb Natapov 2011-06-10 10:45:21 UTC

(In reply to comment #4)
> Is this ok or are we going to do something about it?

This is not the most important bug in our product especially as we do not support direct invocation of qemu (only via libvirt) and since bootindex should be used instead of -boot option. If you fill strong about it send the patch.