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 962718 - "Boot from Local Drive" option didn't work for normal boot menu
Summary: "Boot from Local Drive" option didn't work for normal boot menu
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 10:19 UTC by haiyang,dong
Modified: 2013-05-16 12:19 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-16 12:19:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description haiyang,dong 2013-05-14 10:19:40 UTC
Description of problem:
At first, install rhev-hypervisor6-6.4-20130501.0.el6_4 into local disk.
Then insert the installation media(CD-ROM/USB), and start the system, When the automatic boot prompt appears, press Enter.
        Automatic boot in 30 seconds...
Select the "Boot from Local Drive" option, and press Enter.

Actually it boot the operating system installed on the first local drive failed.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130501.0.el6_4
rhev-hypervisor-advanced-6.4-20130513.0.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1.At first, install rhev-hypervisor6-6.4-20130501.0.el6_4 into local disk.
2.Insert the installation media(CD-ROM/USB), and start the system.
3.Start the system. When the automatic boot prompt appears, press Enter.
        Automatic boot in 30 seconds...
4.Select the "Boot from Local Drive" option, and press Enter.

Actual results:
It boot the operating system installed on the first local drive failed.

Expected results:
When selectting the "Boot from Local Drive" option, it should be success to 
boot the operating system installed on the first local drive 

Additional info:

Comment 2 Mike Burns 2013-05-15 15:16:14 UTC
I suspect this may not be fixable.  I would try (on the same machine) booting a rhel or fedora cd and choose "boot from local drive" to see if that fails as well.

Comment 3 haiyang,dong 2013-05-16 06:44:00 UTC
(In reply to comment #2)
> I suspect this may not be fixable.  I would try (on the same machine)
> booting a rhel or fedora cd and choose "boot from local drive" to see if
> that fails as well.

Hey mburns,

Tried to boot rhel 6.4 and fedora 18 cd media and choose "boot from local drive" option, check that:
rhel 6.4   --Failed
fedora 18  --Failed

Comment 4 Mike Burns 2013-05-16 12:19:25 UTC
Ok, that's what I expected.  This is something that we can't fix for all hardware, unfortunately.  

Similar to our option for serial console, it's a best effort that will work for some machines, but won't for others.


Note You need to log in before you can comment on or make changes to this bug.