Bug 1131018

Summary: installed VM still booting from CD although first boot device is HDD
Product: [Retired] oVirt Reporter: Netbulae <info>
Component: ovirt-engine-coreAssignee: Omer Frenkel <ofrenkel>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kubica <pkubica>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5CC: ecohen, gklein, iheim, michal.skrivanek, ofrenkel, rbalakri, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: ovirt-3.5.0_rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:35:21 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:
Bug Depends On: 1149637    
Bug Blocks:    
Attachments:
Description Flags
screenhost boot options none

Description Netbulae 2014-08-18 11:53:19 UTC
Created attachment 927825 [details]
screenhost boot options

Description of problem:
Installing a VM with the Second Boot device CDROM. After installation, I choose reboot in the VM and the installer of the CDROM appears again even though I have the HDD as first boot device.

When I power down the VM, don't change anything, and power it up again. It does start from the local HDD

Comment 1 Omer Frenkel 2014-08-20 15:13:10 UTC
the issue is in add disk that cause the boot order to be wrong (order is calculated before the disk is added).

looks like this affects vms created from blank (or other diskless) template and the disk is added afterwards.

a workaround is to first create the vm and the disk,
and only after that, edit the vm and choose the wanted boot options, this will cause the boot order to be re-calculated, taking into account also the disk.

Comment 2 Petr Kubica 2014-10-16 10:59:00 UTC
Verified in 3.5.0.1-0.0.master.20141009085636.el6

Comment 3 Sandro Bonazzola 2014-10-17 12:35:21 UTC
oVirt 3.5 has been released and should include the fix for this issue.