Multiple boot devices for VMs
|Assignee:||Javi Fontan||% Done:|
|Category:||Core & System|
|Target version:||Release 4.4|
The users should be able to define multiple boot devices for VMs. This is especially useful in virtual cluster node installations, where it is common to have the nodes always first boot from the network and then from the harddisk, if no reinstallation is needed.
I've made a quick hack to the LibVirtDriverKVM.cc deployment description generation in our ONE 2.2 instance by just generating a new <boot dev='xxx'/> element for each whitespace separated token defined in BOOT attribute of the VM description. It seems to work ok. Of course, something more elegant would be nice, like making BOOT a multi valued attribute.
feature #538: Changes using the new split function.
(cherry picked from commit 0cee3d7ac05c05f0a13e7dcf9e504021df98f6a2)
- Tracker changed from Request to Feature
- Category set to Core & System
- Assignee set to Ruben S. Montero
Thanks for the feedback, it seems totally reasonable. I moved this to feature and schedule in a future release.
This would solve issues when trying to install Windows 7/2008 from ISO and VirtIO drivers too.
I think making BOOT a multi valued attribute may be misleading. Adding comma separated values easily defines boot order. I'm using attached patch.
- Priority changed from Low to Normal
- Target version set to Release 4.2
- Assignee deleted (
Ruben S. Montero)
- Target version changed from Release 4.2 to Release 4.4
- Assignee set to Javi Fontan
- Status changed from New to Assigned
- % Done changed from 0 to 80
Multi boot not working for VMware
- extraConfig is for ESX <= 5.0
- RbVmomi doesn't seem to be able to handle the new Bootable objects ATM
- Assignee changed from Javi Fontan to Ruben S. Montero
- Assignee changed from Ruben S. Montero to Javi Fontan
- Status changed from Assigned to Closed
- Resolution set to fixed
Also available in: Atom