On Sun, Dec 24, 2017 at 3:14 PM, awokd <[email protected]> wrote: > > It's not very elegant but this should work: > > Boot from your Qubes install media > Troubleshooting > Rescue a Qubes system > 1 > Enter > chroot /mnt/sysimage > nano /var/lib/qubes/qubes.xml > look for the line with name="sys-net", it will probably start with QubesNetVm > change name="sys-net" to name="sys-net2" > ctrl-x, y to save changes, Enter > exit > reboot > remove Qubes install media > boot into Qubes normally Did the same by just changing the sys-firewall vm name in qubes.xml to sys-firewall2, which caused qubesd failure. That helped to boot into dom0 super fast. After that had to keep trying different combinatin to get qubesd service to start again, and later removed and recreated the sys-firewall vm. Thanks a lot for the tips.
I am not exactly sure why I am getting into this pain again and again :( For now, I updated dom0 with the packages from latest testing. Let us see how well those work. Kushal -- Staff, Freedom of the Press Foundation CPython Core Developer Director, Python Software Foundation https://kushaldas.in -- 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 [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-users/CAAzeMbxFMq7Jck-Wi9eVW-PCOdK%2BMJQYn6--L3-kvBBMZ5ZKJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
