Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1808846

Summary: VM failed to boot from attached CD (ISO domain image)
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: Nisim Simsolo <nsimsolo>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, lrotenbe, nsimsolo, rbarry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-09 16:24:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log
none
vdsm.log
none
console video capture
none
systemd journal
none
qemu log
none
libvirt log none

Description Nisim Simsolo 2020-03-01 15:13:37 UTC 
Description of problem:
Trying to boot VM from attached CD failed with boot failed message (inside VM console):
Could not read from CDROM (code 0003)

- This issue is relevant for run once and edit VM -> boot options dialog.
- When selecting ISO from console -> change CD option and rebooting VM, the VM boots from CD successfully.
- This issue is not related to VM CPU type or custom emulated machine type.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0-0.24.master.el8ev
vdsm-4.40.5-1.el8ev.x86_64
libvirt-daemon-6.0.0-7.module+el8.2.0+5869+c23fe68b.x86_64
qemu-kvm-common-4.2.0-12.module+el8.2.0+5858+afd073bc.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create new VM with 20GB disk.
2. Run once VM, boot options -> attach cd, select ISO file and change CD-ROM to be first in boot sequence.
3. Click OK

Actual results:
VM failed to boot from CD

Expected results:
It should be possible to boot VM from CD

Additional info:
engine.log, vdsm.log (VM started at 2020-03-01 17:12:34,136+0200) and screen video attached.
Comment 1 Nisim Simsolo 2020-03-01 15:16:48 UTC 
Created attachment 1666781 [details]
engine.log
Comment 2 Nisim Simsolo 2020-03-01 15:17:23 UTC 
Created attachment 1666782 [details]
vdsm.log
Comment 3 Nisim Simsolo 2020-03-01 15:17:52 UTC 
Created attachment 1666783 [details]
console video capture
Comment 4 Ryan Barry 2020-03-02 00:39:20 UTC 
Qemu logs, libvirt logs, systemd journal, please

I'd also ask whether this is reproducible on i440fx, as it may be related to the SATA CDROM on q35
Comment 5 Nisim Simsolo 2020-03-03 08:12:58 UTC 
(In reply to Ryan Barry from comment #4)
> Qemu logs, libvirt logs, systemd journal, please
> 
> I'd also ask whether this is reproducible on i440fx, as it may be related to
> the SATA CDROM on q35

Not related, as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1808846#c0
- This issue is not related to VM CPU type or custom emulated machine type.
Comment 6 Nisim Simsolo 2020-03-03 08:56:49 UTC 
Created attachment 1667141 [details]
systemd journal
Comment 7 Nisim Simsolo 2020-03-03 15:37:15 UTC 
Created attachment 1667217 [details]
qemu log
Comment 8 Nisim Simsolo 2020-03-03 15:37:58 UTC 
Created attachment 1667218 [details]
libvirt log
Comment 9 Liran Rotenberg 2020-03-09 16:24:55 UTC 
This looks like the same as bz 1811425.

From the vdsm.log:
2020-03-01 17:12:38,852+0200 WARN  (vm/252d0b20) [virt.vm] (vmId='252d0b20-e797-4fd1-8772-534e254a7621') updating drive ua-26ea349b-a5ae-499c-a3da-7e4d02494fbe path from /rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_nsimsolo__ISO/50835a00-573c-4d1d-965a-44d4af0e3470/images/11111111-1111-1111-1111-111111111111/RHEL-7.7-20190212.n.2-Server-x86_64-dvd1.iso to  (storage:177)
2020-03-01 17:12:38,852+0200 WARN  (vm/252d0b20) [virt.vm] (vmId='252d0b20-e797-4fd1-8772-534e254a7621') updating drive ua-26ea349b-a5ae-499c-a3da-7e4d02494fbe config path from /rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_nsimsolo__ISO/50835a00-573c-4d1d-965a-44d4af0e3470/images/11111111-1111-1111-1111-111111111111/RHEL-7.7-20190212.n.2-Server-x86_64-dvd1.iso to  (storage:198)

In libvirt:
2020-03-03 08:27:26.612+0000: 252080: error : virDomainDiskTranslateSourcePool:31516 : XML error: 'startupPolicy' is only valid for 'file' type volume
2020-03-03 08:27:26.612+0000: 252080: debug : qemuDomainCheckRemoveOptionalDisk:11203 : Dropping disk 'sdc' on domain 'new_vm' (UUID '252d0b20-e797-4fd1-8772-534e254a7621') due to inaccessible source '/rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_nsimsolo__ISO/50835a00-573c-4d1d-965a-44d4af0e3470/images/11111111-1111-1111-1111-111111111111/RHEL-7.7-20190212.n.2-Server-x86_64-dvd1.iso'

Closing as a duplicate.

*** This bug has been marked as a duplicate of bug 1811425 ***