On Wed, Jan 09, 2013 at 18:02:22 +0000, Daniel P. Berrange wrote: > On Wed, Jan 09, 2013 at 12:36:52PM -0500, Laine Stump wrote: > > > > Just a note about this: as far as I can tell virt-manager currently only > > uses the "old style" of specifying boot order; it needs to be enhanced > > to recognize the presence of bootindex=n ordering, and behave > > accordingly. Looking from the outside, that looks to be not completely > > trivial, as the old style of ordering only allows specifying "hard disk" > > as a single line in the priority order, but the new style has each disk > > specified separately. Not only that, but *which* of the disks is tried > > first under the old order may change depending on whether or not a > > bootmenu is requested (in one case it picks unit=0 on the controller, in > > the other case, it orders the disks alphabetically by target dev name) > > Hmm, well libvirt should be using bootindex=n on the QEMU command line > regardless of what applications put in the XML. ie if the application > uses the old style XML, libvirt should translate that into bootindex=n > for them. It should already be doing that. However, when I was implementing this, I was told bootmenu is incomatible with bootindex and thus, if you turn on bootmenu, libvirt will not translate the old-style boot order into bootindex. Jirka -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list