The current rc.d/vm REQUIREs 'NETWORKING' but is also BEFORE pf/ipfw. This is not well formed (as NETWORKING relies on pf/ipfw), but is desired to generate bridges before pf/ipfw are generated. Likewise for iscsi attachments to work, vm auto-booting should be after NETWORKING.
Split into vm_net (early / bridge generation) and vm (late / vm start as well as shutdown) phases/rc.d files. This allows non-circular ordering of dependencies.
We don't currently have a clean way to stop and restart the 'init' phase, especially in light of potentially needing to reload firewalls rules.
This still uses the same vm_enable rcvar, so there is no change in "user interface"
Split startup into two phases (bridges/vms)
The current rc.d/vm REQUIREs 'NETWORKING' but is also BEFORE pf/ipfw. This is not well formed (as NETWORKING relies on pf/ipfw), but is desired to generate bridges before pf/ipfw are generated. Likewise for iscsi attachments to work, vm auto-booting should be after NETWORKING.
Split into vm_net (early / bridge generation) and vm (late / vm start as well as shutdown) phases/rc.d files. This allows non-circular ordering of dependencies.
We don't currently have a clean way to stop and restart the 'init' phase, especially in light of potentially needing to reload firewalls rules.
This still uses the same vm_enable rcvar, so there is no change in "user interface"