On Fri, Nov 17, 2017 at 02:58:24AM -0800, Elias Mårtenson wrote: > I have configured sys-net and sys-firewall to only manage the WLAN > connection. I have > then set up two separate VM's, foo-net and foo-firewall that manages the > ethernet > interface on my computer. The latter is connected a separate network, and > have > dedicated VM's connected to them. > > The behaviour that I am observing is that foo-net and foo-firewall are > automatically > started whenever I boot the machine, even though they have autostart = > False. > Also, there are no VM's started that depend on these network VM's. > > What could trigger the start of these VM's? >
You havent said which version if Qubes you are running. in 3.2 the qubes-netvm service may be responsible. You could try changing the default netvm, or temporarily disabling the qubes-netvm.service and see if that changes behaviour. -- 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/20171117110824.ny2hs64wcsgvg35c%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
