Bug 2044152

Summary:	[machines] The VM could not be booted if attaching a disk by "custom path"
Product:	Red Hat Enterprise Linux 9	Reporter:	YunmingYang <yunyang>
Component:	cockpit-machines	Assignee:	Martin Pitt <mpitt>
Status:	CLOSED WONTFIX	QA Contact:	YunmingYang <yunyang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	kkoukiou, skobyda, wshi, xchen, ymao
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-24 07:28:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description YunmingYang 2022-01-24 06:42:59 UTC

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:

Comment 1 YunmingYang 2022-01-24 07:04:29 UTC

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

Comment 2 Simon Kobyda 2023-04-04 15:08:19 UTC

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?

Comment 6 RHEL Program Management 2023-07-24 07:28:27 UTC

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.