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