Wrong boot order.

  • Thread starter Thread starter cirroz
  • Start date Start date
C

cirroz

Guest
Looks like it's a bug in booting KVM guests.
I have several kvm machines.
I set boot order like this:

VMID-100: order=1
VMID-201: order=5
VMID-220: order=10
VMID-222: order=11

In fact they boot in this order:
VMID-100 - 1
VMID-220 - 10
VMID-222 - 11
VMID-201 - 5

Check this out, please.
 
Sorry, didn't find any thread about it.
Thanx.
 
Last edited by a moderator:
It's me again.
According documentation:

--bootorder number Sets the boot order priority for this CT. The higher the number is, the earlier in the boot process this container starts. By default this parameter is unset, which is considered to be the lowest pri- ority, so containers with unset bootorder will start last.

But openvz containers boot in reverse order.
I.e. container with bootorder=100 starts after container with bootorder=90.

Maybe I do understand the phrase "the higher number" wrong?