KVM Virtual Machine Boot Order
-
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Not really, it's once a month at worst.
-
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
-
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
Well. . . that's just bad. . .
-
The only actual need I got was a vm expecting a postgres to be up. I delayed such a vm. But yes: complex dependency schemas are a PITA but also out of the smb standard scenario imho.
-
@black3dynamite said in KVM Virtual Machine Boot Order:
Uncomment
START_DELAY=0in/etc/sysconfig/libvirt-guestsfile.https://access.redhat.com/discussions/685243
This will kill parallel startup adding a delay between each vm boot
-
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@black3dynamite said in KVM Virtual Machine Boot Order:
Uncomment
START_DELAY=0in/etc/sysconfig/libvirt-guestsfile.https://access.redhat.com/discussions/685243
This will kill parallel startup adding a delay between each vm boot
I think that's the point, though. Some of the VMs are starting before the other VMs that they need to work properly.
-
@dafyre nope starting order is still 'random'
-
I still find it odd that there isn't a start priority or weight setting to apply to each VM so the hypervisor could do this automatically. . .
-
XenServer and XCP-ng both have this option to set for individual VM's under "Start options" under properties of each VM.
By default everything is "0" aka start immediately if configured for Autostart/HA. But it can be changed easily to 1, 2 3 etc and the VM's will boot in that order.
-
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
Hyper-V had startup priority since 2012... fully configurable... startup action and startup delay.
-
@obsolesce said in KVM Virtual Machine Boot Order:
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
Hyper-V had startup priority since 2012... fully configurable... startup action and startup delay.
You mean you can use action to wait for another vm to be up and running? If so I ignored it. Delay is mostly a workaround as no one really knows when a dependency will be ready!
-
@dustinb3403 but this will include "wait until vm A is operational/service B is available"?
-
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 but this will include "wait until vm A is operational/service B is available"?
The hypervisor has no way of knowing what the VM does, so no. It just says start this VM first, then that one, and then that one etc.
-
@dustinb3403 said in KVM Virtual Machine Boot Order:
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 but this will include "wait until vm A is operational/service B is available"?
The hypervisor has no way of knowing what the VM does, so no. It just says start this VM first, then that one, and then that one etc.
At this level hyperv acts like xen. Anyway pre post hooks could be available...
-
Now to be fair both mine and @dafyre cases could be solved with longer polling intervals, so they are a sysadmin issue not related to virtualization. Anyway hv agents are used for a lot of things, I don't see why they couldn't act as kubernates with containers. I suppose it is just a lack of demand.
-
@obsolesce said in KVM Virtual Machine Boot Order:
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
Hyper-V had startup priority since 2012... fully configurable... startup action and startup delay.
This is inaccurate. There is not a priority.
Hyper has only ever had this.
-
@jaredbusch said in KVM Virtual Machine Boot Order:
@obsolesce said in KVM Virtual Machine Boot Order:
@matteo-nunziati said in KVM Virtual Machine Boot Order:
@dustinb3403 said in KVM Virtual Machine Boot Order:
@obsolesce that's annoying. . .
Edit: still annoying but doesn't Hyper-V have startup priority?
No it hasnt until I checked 6 months ago. Only way is build a delay schema by hand and assign delays to VM batch start them in layers
Hyper-V had startup priority since 2012... fully configurable... startup action and startup delay.
This is inaccurate. There is not a priority.
Hyper has only ever had this.
Okay, technically incorrect.... I'll give you that.
The point I was trying to make, was you can artificially set priority VM booting by adjusting the "startup delay" for each VM.
