On Jan 3, 2013, at 13:05 , Frank Wall <fw...@inotronic.de> wrote:

> Hi,
> 
> I'm using the REST API to change the boot device and attach CD-ROM images.
> At least I try to...  Currently I'm using the following calls to achieve this:
> 
> Task: attach cdrom
> Path: https://ovirt-engine.example.com/vms/%%%VM-ID%%%/cdroms
> Method: POST
> Data: <cdrom><file id='%%%FILE-ID%%%'/></cdrom>
> 
> Task: change boot order
> Path: https://ovirt-engine.example.com/vms/%%%VM-ID%%%
> Method: PUT
> Data: <vm><os><boot dev='%%%BOOT-DEVICE%%%'/></os></vm>
> 
> 
> And it seems to work, because I can see the changes to the cdrom...
> 
> <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?
> 
> Besides that I can see these settings on the oVirt Admin Portal, too.
> The first boot device is "CD-ROM", the CD is attached and the Image is
> "FreeBSD-8.3-RELEASE-amd64-disc1.iso". Looks good to me. But it still
> won't 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.
Hi,
regarding the Admin portal way - did you configure the order there or just look 
at it but it was originally configured via REST?

Thanks,
michal
> 
> Sounds strange, don't you think? So the question is: Is it a known
> bug or did I broke something with the above API calls?
> 
> # rpm -qa '*ovirt*'
> ovirt-engine-sdk-3.1.0.4-1.fc17.noarch
> ovirt-engine-config-3.1.0-2.fc17.noarch
> ovirt-engine-restapi-3.1.0-2.fc17.noarch
> ovirt-engine-3.1.0-2.fc17.noarch
> ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch
> ovirt-engine-tools-common-3.1.0-2.fc17.noarch
> ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch
> ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch
> ovirt-release-fedora-4-2.noarch
> ovirt-engine-userportal-3.1.0-2.fc17.noarch
> ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch
> ovirt-engine-dbscripts-3.1.0-2.fc17.noarch
> ovirt-engine-backend-3.1.0-2.fc17.noarch
> ovirt-engine-setup-3.1.0-2.fc17.noarch
> ovirt-engine-notification-service-3.1.0-2.fc17.noarch
> ovirt-engine-genericapi-3.1.0-2.fc17.noarch
> 
> 
> Thanks
> - Frank
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to