units: systems might take a while to boot

vmspawn systems might take quite a while to boot in particular if they
go through uefi and wait for a network lease. Hence let's increase the
start timeout to 2min (from 45s). We'll do that for both nspawn and
vmspawn, even though the UEFI thing certainly doesn't apply there (but
the DHCP thing still does).

units/systemd-nspawn@.service.in

@@ -29,6 +29,7 @@ Delegate=yes
 DelegateSubgroup=supervisor
 CoredumpReceive=yes
 TasksMax=16384
+TimeoutSec=2min
 {{SERVICE_WATCHDOG}}
 
 {# Enforce a strict device policy, similar to the one nspawn configures (in

units/systemd-vmspawn@.service.in

@@ -21,6 +21,7 @@ ExecStart=systemd-vmspawn --quiet --register=yes --keep-unit --network-tap --mac
 KillMode=mixed
 Type=notify
 Slice=machine.slice
+TimeoutSec=2min
 {{SERVICE_WATCHDOG}}
 
 {# Enforce a strict device policy. Make sure to keep these policies in sync if you change them! #}

units/user/systemd-nspawn@.service.in

@@ -25,6 +25,7 @@ Delegate=yes
 DelegateSubgroup=supervisor
 CoredumpReceive=yes
 TasksMax=16384
+TimeoutSec=2min
 {{SERVICE_WATCHDOG}}
 
 [Install]

units/user/systemd-vmspawn@.service.in

@@ -18,6 +18,7 @@ ExecStart=systemd-vmspawn --quiet --keep-unit --register=yes --network-tap --mac
 KillMode=mixed
 Type=notify
 Slice=machine.slice
+TimeoutSec=2min
 {{SERVICE_WATCHDOG}}
 
 [Install]