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.
Comment 2Martin Kletzander
2014-01-16 14:45:33 UTC
This needs more code to be put in (either boot order or the particular order of disks). As a workaround you can remove and add those disks again in the order you want. Please try if enabling bootmenu (or disabling the boot order) helps also, that might be possible workaround as well.
Could reproduce this issue with virt-manager-0.10.0-16.el7.noarch
Reproduce steps:
1. Install a guest on an IDE disk.
2. Add a virtio disk as its second disk.
3. Destroy the guest, then change its IDE disk to virtio
4. Start the guest.
Guest will boot in the disk added by step 2, then report an error: no bootable device.
Verify this issue with:
virt-install-1.1.0-1.el7.noarch
virt-manager-1.1.0-1.el7.noarch
virt-manager-common-1.1.0-1.el7.noarch
1. Install a guest on an IDE disk.
2. Add a virtio disk as its second disk.
3. Destroy the guest, then change its IDE disk to virtio
4. Start the guest.
Guest could be started normally.
So change the status from 'ON_QA' to 'VERIFIED'
Comment 11Giuseppe Scrivano
2015-01-20 08:45:12 UTC
the following patch fixed the issue upstream (and it was included as part of the rebase for 7.1):
commit 4a006b5ff8ce5abc1935613dae49cb5801b818de
Author: Cole Robinson <crobinso>
Date: Sun Feb 9 16:21:26 2014 -0500
details: Expose fine grained boot config
Basically put an explicit device list in the boot UI, if the hypervisor
supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
If users mess up with devices, they can always re-configure the boot order as they prefer.
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-2015-0427.html