On Mon, Nov 14, 2016 at 01:31:28PM +0000, Fred wrote: > On 12/11/2016 08:27, Alex wrote: > > Try editing /var/lib/qubes/qubes.xml and set "autostart" to False > > instead of True for the sys-net vm > > I had actually found this file and tried setting the autostart attribute > but the VM still auto-started. > > I also tried editing the sys-net XML file directly (removing the bad > assigned device(s)). There was a warning in the comments at the top > about this file about changes potentially being overwitten but I > couldn't find the correct file to make these changes manually. This file > also existed in more than one place and the qvm-* commands didn't work > as they couldn't connect. > > In any case I just reinstalled as it was quicker. > > The offline mode of the qvm-* commands may have worked (referred to in > the link in Marek's response). Or maybe disabling the sysVM service via > systemctl ? > For future reference, I think the sys-net started because there were OTHER qubes downstream set to autostart, e.g sys-firewall. If they are still starting they will trigger the sys-net. So you need to either set the netvm to none for them or stop them starting.
unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20161114134652.GB9627%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
