On Thu, Jan 03, 2013 at 01:05:00PM +0100, Frank Wall wrote:
<cdroms>
<cdrom href="/api/vms/VM-ID/cdroms/00000000-0000-0000-0000-000000000000"
id="00000000-0000-0000-0000-000000000000">
<vm href="/api/vms/VM-ID" id="VM-ID"/>
<file id="FreeBSD-8.3-RELEASE-amd64-disc1.iso"/>
</cdrom>
</cdroms>
...and the boot device is also changed...
[...]
<os type="unassigned">
<boot dev="cdrom"/>
</os>
[...]
...but the VM won't boot off the CD-ROM device, instead it just
boots from the first harddisk. So what am I doing wrong?
OK, the problem is still NOT solved, but I did some further
investigation. First, the problem ONLY affects VMs with a bootable
harddisk (and an operating system installed).
A newly created VM is NOT affected and is able to boot from CD-ROM.
Once I install an operating system, the VM will no longer be able
to boot from CD-ROM. No matter what is configured as boot device...
There is still only the following workaround to boot from CD-ROM:
The only way I am able to boot from CD-ROM is when using the
"Run once" function on the Admin Portal and configure the CD-ROM
device/image there (temporarely overwriting my config).
It will NOT work if I configure the CD-ROM device through the REST
API or the Admin Portal. Just "Run Once" will do the right thing.
Any idea how to debug this further and get a bugfix/working solution?
oVirt is running fine, except this annoying bug makes it somewhat
useless for us.
Thanks
- Frank