Re: [qubes-users] Re: Please help, can't get into Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Nov 14, 2016 at 01:31:28PM +, 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 ? Both should work. As for services, you need to disable: - qubes-netvm.service - qubes-vm@sys-net.service (this is really what 'autostart' VM property really does) - qubes-vm@sys-firewall.service - and any other using sys-net for its network - or set those to not use sys-net. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYKjDXAAoJENuP0xzK19csJs8H/0cEeo7N7EnYzIIi5s0QiPri s0djWNxg4I72EW/HIMdmTh6+YHNFoY+ZSIQpr4/6RH4047EyE3F8hSB8N+fxwpha rgMFiHWqsZGGoHxAFvl5goPKpWg91E3mUpgh4fJ991zq71P+D9nhX0EmLM1tGwoE sGeAzI5MfdBdxrjCSkH0mW7oGdhxEELQ3oQxZNjPn4/8TqIqOkWztB3DNs+T/Quv 5CeX3GfZDjLRH60lfrdkDvWCqlr7XsySueRwjPELC2Khagql+2jCWHbLThakWhMx arEZSVhs7gQ0SiMQQjifzjQ708p00cLwKiLyZDQMcdDGo87ID8JRK+8HlHllt3c= =Wuoj -END PGP SIGNATURE- -- 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/20161114214703.GL2994%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help, can't get into Qubes
On 14/11/2016 13:46, Unman wrote: > 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. That makes more sense. Thanks. -- 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/e37e6bef-f7c3-0fa0-de1c-f5719c7b1713%40gmsl.co.uk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help, can't get into Qubes
On Mon, Nov 14, 2016 at 01:31:28PM +, 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.
Re: [qubes-users] Re: Please help, can't get into Qubes
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 ? -- 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/691de818-3233-eb3c-d82d-11f2b447b91e%40gmsl.co.uk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help, can't get into Qubes
On 11/12/2016 04:32 AM, Sec Tester wrote: > On Saturday, 12 November 2016 06:39:50 UTC+10, Fred wrote: >> I made a change to the PCI devices for the sys-net VM and now >> Qubes hangs on boot when starting this vm. >> >> I've tried using the installation image to get to system rescue via >> the troubleshooting link in the installer. I can get into my system >> this way but I'm unsure what to change as removing the pci device >> from the sys-net XML file doesn't seem to make this change persist >> -- something keeps generating a new one with the bad PCI device XML >> node. >> >> How can I disable sys-net from starting when connected via a rescue >> shell? Try editing /var/lib/qubes/qubes.xml and set "autostart" to False instead of True for the sys-net vm -- Alex -- 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/9831f8e9-227a-1f36-1193-9a1833ed54f1%40gmx.com. For more options, visit https://groups.google.com/d/optout.
