Feature #538

Multiple boot devices for VMs

Added by Olli Tourunen over 8 years ago. Updated over 5 years ago.

Status:ClosedStart date:03/17/2011
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

80%

Category:Core & System
Target version:Release 4.4
Resolution:fixed Pull request:

Description

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.

multiboot.diff Magnifier (743 Bytes) Łukasz Oleś, 06/16/2012 06:52 AM


Related issues

Duplicated by Feature #588: Ability to specify boot order for VM Closed 04/25/2011

Associated revisions

Revision 0cee3d7a
Added by Ruben S. Montero over 5 years ago

feature #538: Changes using the new split function.

Revision 7f490cc4
Added by Ruben S. Montero over 5 years ago

feature #538: Changes using the new split function.

(cherry picked from commit 0cee3d7ac05c05f0a13e7dcf9e504021df98f6a2)

Revision 73c4d1ef
Added by Abel Coronado over 1 year ago

B #5473: Disabled actions can be scheduled (#538)

Revision 432caf56
Added by Abel Coronado over 1 year ago

B #5473: Disabled actions can be scheduled (#538)

History

#1 Updated by Ruben S. Montero over 8 years ago

  • Tracker changed from Request to Feature

#2 Updated by Ruben S. Montero over 8 years ago

  • 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.

#3 Updated by Timothy OBrien about 7 years ago

+1 here
This would solve issues when trying to install Windows 7/2008 from ISO and VirtIO drivers too.

#4 Updated by Łukasz Oleś about 7 years ago

I think making BOOT a multi valued attribute may be misleading. Adding comma separated values easily defines boot order. I'm using attached patch.

#5 Updated by Ruben S. Montero about 6 years ago

  • Priority changed from Low to Normal

#6 Updated by Ruben S. Montero about 6 years ago

  • Target version set to Release 4.2

#7 Updated by Ruben S. Montero about 6 years ago

  • Assignee deleted (Ruben S. Montero)

#8 Updated by Ruben S. Montero about 6 years ago

  • Target version changed from Release 4.2 to Release 4.4

#9 Updated by Ruben S. Montero almost 6 years ago

  • Assignee set to Javi Fontan

#10 Updated by Tino Vázquez over 5 years ago

  • 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

#11 Updated by Ruben S. Montero over 5 years ago

  • Assignee changed from Javi Fontan to Ruben S. Montero

#12 Updated by Ruben S. Montero over 5 years ago

  • Assignee changed from Ruben S. Montero to Javi Fontan

#13 Updated by Javi Fontan over 5 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Also available in: Atom PDF