On 06/08/2016 04:38 PM, Aline Manera wrote:
On 06/01/2016 05:12 PM, Ramon Medeiros wrote:
> Propose: Kimchi allow to change boot order ("fd", "hd",
"cdrom" or
> "network")
>
> hd device can specify which disk will be booted
>
> Rest API will receive answer from
>
I think we can list bootorder among with other VM information provided
by GET method and update it using PUT method
GET /vms/<name>
{ ...
bootorder: [...]
}
PUT /vms/<name> {bootorder: [<new values>]
ok
> /plugins/kimchi/<VM NAME>/bootorder
>
> {[{"dev": "hd"}]} or a list: {[{"dev": "hd"},
{"dev": "cdrom"}]}
>
> Doubts:
>
> How we can edit the bootloader? Like the list above or a kind of
> fixed list?
>
> Libvirt provides bootmenu too, which allows users to pick a device in
> the beginning. Must have it?
It would be good to have bootmenu enabled too.
I think there is an issue for it too and it is assigned to you. So if
you want to send a patch for it, I am fine! Just do not mix things.
One patch set for boot order and other, to enable boot menu.
I did not make bootmenu worked, even manually, so i will skip this. I
will look more examples and send a separated patch as you asked to.
> --
>
> Ramon Nunes Medeiros
> Kimchi Developer
> Linux Technology Center Brazil
> IBM Systems & Technology Group
> Phone : +55 19 2132 7878
> ramonn(a)br.ibm.com
>
>
> _______________________________________________
> Kimchi-devel mailing list
> Kimchi-devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel
--
Ramon Nunes Medeiros
Kimchi Developer
Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
ramonn(a)br.ibm.com