Il 13/06/2013 09:06, Sandro Bonazzola ha scritto:
> Hi,
> This is my vm.conf:
>
> vmId=f785ebfd-a9dc-4453-be0e-ae7e57a804b0
> memSize=4096
> macAddr=00:16:3e:71:bb:e5
> display=vnc
> drive=pool:63570f35-35b9-4f82-aea5-7a34535a670d,domain:77a192ce-175e-4085-bd1f-342e4993b802,image:279076a8-a888-4ac2-8b40-b72fd488c173,volume:bf24cc76-ada5-428a-8ded-0662d08fe5d5
> cdrom=/Fedora-18-x86_64-DVD.iso
> boot=d
> vmName=oVirt Hosted Engine
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
> bridge=ovirtmgmt
> nicModel=virtio
>
> I create the vm calling vdsClient create.
> After Fedora installation I need to boot from HD instead of cdrom.
> How may I specify the boot order for having it as hd,cdrom booting from
> hd on reboot?
>
drive=pool:63570f35-35b9-4f82-aea5-7a34535a670d,domain:77a192ce-175e-4085-bd1f-342e4993b802,image:279076a8-a888-4ac2-8b40-b72fd488c173,volume:bf24cc76-ada5-428a-8ded-0662d08fe5d5,bootOrder:1

seems to work for setting the HD as first device. However using this introduce 
a conflict on boot=d, boot option can't be used. cdrom also seems that can't be 
used if I specify the cdrom device. However, I'm not able to create a valid 
cdrom device:
I'm trying with:

devices={deviceType:disk,type:disk,device:cdrom,readonly:true,bootOrder:2,alias:cdrom0,iface=ide'}
and I've:
Bad volume specification {'index': '0', 'iface': "ide'", 'bootOrder': '2', 
'alias': 'cdrom0', 'readonly': 'true', 'deviceType': 'disk', 'device': 'cdrom', 
'type': 'disk'}




-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to