On Saturday, 18 November 2017 20:55:09 UTC+8, Chris Laprise wrote: > > On 11/17/2017 06:12 AM, Elias Mårtenson wrote: > > On 17 November 2017 at 19:08, Unman <un...@thirdeyesecurity.org > <javascript:> > > <mailto:un...@thirdeyesecurity.org <javascript:>>> wrote: > > > > 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. > > > > Oops. Sorry about that. It's 4.0rc2. > > I was able to prevent sys-net and sys-firewall auto-start in rc2 by > simply disabling 'Start VM automatically at boot' in settings. The only > other difference is that my default netvm is set to 'VPN' but I wouldn't > expect that to matter.
I've confirmed that both the net- and firewall VM's are configured to not start at boot (as far as I understand, this option simply controls the ‘autostart’ prefs option), yet the VM's still start at boot. The only other thing that is special about these VM's is that my second netvm has the ethernet hardware attached to it. That said, even if that was the cause it wouldn't explain why the firewall vm starts at boot too. -- Elias -- 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 qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/ee18d200-8f9a-4d1d-b0a2-3eb3a3895333%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
