Hi,

IIRC in R3.2 VMs were started at boot time according to their dependency on other VMs. Eg. - for a basic setup without whonix/tor/... - sys-net would start first, then sys-firewall, and then other VMs configured to start at boot time (in my case sys-usb, untrusted and work).

In R4.0 (rc3) I see that all the VMs start in parallel at boot time.
/usr/lib/systemd/system/[email protected] don't show any qubes specific VM dependency mechanism, and neither do systemctl list-dependencies nor systemd-analyze critical-chain qubes-vm@sys-firewall (for instance) show a dependency on sys-net.

Q: is starting *all* the VMs in parallel the "new" way in R4.0 ?

I'm asking because each time I reboot, sys-net consistently fails with the error message below so I'm wondering whether I'm hitting a totally unrelated bug (in which case I'll open an issue) or if VMs in 4.0 have to be started in a specific order but the mechanism isn't implemented yet (or doesn't work in my case):

`Start failed: invalid argument: network device with mac [...] already exists`

Note: sys-net has networking PCI devices assigned.

The odd thing is that sys-firewall always manages to start despite sys-net's failure and other VMs "higher" in the dependency chain (sys-usb, work, ...) also start successfully.

Starting sys-net manually fails with the same error as above. A helfpul qubes-user list thread [1] hinted that sys-firewall had to be stopped for sys-net to start successfully, so the workaround is to shutdown all the VMs and start them manually according their dependency order - eg. qvm-start sys-net, then sys-firewall, and then any of sys-usb/work/untrusted/...


Ivan

PS: as always, kudos for the great work - I've switched to R4.0rc3 in production with only very minimal issues so far in the past 2 weeks.

[1] https://groups.google.com/forum/#!topic/qubes-users/ta7yGkXoHYs

--
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/d23308f8-3563-e7bb-7a29-b69827a41753%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

Reply via email to