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.

Description of problem:
After attaching a bootable disk by "custom path" and setting the VM booted from this disk, the VM will be booted unsuccessfully, and "No bootable device" will be shown in "VNC console" 

Version-Release number of selected components (if applicable):
libvirt-dbus-1.4.1-5.el9.x86_64
cockpit-260-1.el9.x86_64
cockpit-machines-258.1-1.el9.noarch

How reproducible:
100%

Steps to Reproduce:
1 Create a VM
2 Detach all disks of the VM
3 Attach a bootable disk to the VM by "custom  path"
4 Run the VM

Actual results:
1 In the step 4, there will be "No bootable device" will be shown in "VNC console", and the VM is booted unsuccessfully 

Expected results:
1 In step 4, the VM could be booted successfully

Additional info:

Add a additional info that the disk attaching by "custom path" is a installed disk whose type is qcow2

Cannot reproduce locally. The issue can be that the qcow2 you are trying to attach might be actually empty, or that libvirt assume boot order of device.
Could you please share the XML of the VM after step 3?

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.