When PyGrub is used as the bootloader in Xen, it gets passed the first
bootable disk. Xend supports a bootable-flag for this, which was
previously unused.
In commit c2969ec7aec5c40519aadf422ab5c47a21938bff the bootable=1 flag
was used to re-order the disks when converting from SEXPR to XML, such
On Mon, Oct 31, 2011 at 13:39:09 +0100, Philipp Hahn wrote:
When PyGrub is used as the bootloader in Xen, it gets passed the first
bootable disk. Xend supports a bootable-flag for this, which was
previously unused.
In commit c2969ec7aec5c40519aadf422ab5c47a21938bff the bootable=1 flag
was
Hello Kiri,
Am Montag 31 Oktober 2011 15:15:12 schrieb Jiri Denemark:
Is there any way you can pass the exact order to Xen?
Not that I know of. This is one of the corner cases, which is only relevant if
you have a Xen-PV domain AND are using PyGrub as the boot-loader. For HV the
flag is
Hello Jiri,
one more thing:
On Monday 31 October 2011 15:15:12 Jiri Denemark wrote:
Is there any way you can pass the exact order to Xen?
As far as I know the disks of Xen just have an order. This implicit order is
lost when the disks are sorted by target/@bus and target/@name.
BYtE
Philipp
On Mon, Oct 31, 2011 at 16:14:46 +0100, Philipp Hahn wrote:
Hello Jiri,
one more thing:
On Monday 31 October 2011 15:15:12 Jiri Denemark wrote:
Is there any way you can pass the exact order to Xen?
As far as I know the disks of Xen just have an order. This implicit order is
lost when