You can try to revert the template's filesystem like this (dom0):
$ qvm-volume revert templatename:root
This will only work if you haven't restarted the template since it was
damaged.
The next-easiest solution is to switch (at least temporarily) to another
template for sys-net if you have one -- this is a good reason to have
more than one template, in case your main one gets damaged.
Another thing to try is to get your Qubes install media and see if you
can locate the template .rpm package files on it (I don't recall the
path at the moment); They could be installed manually.
Finally, you could try connecting using the damaged template/sys-net.
There are advice pages around the Internet that describe connecting
without NetworkManager for instance (I suggest doing this with ethernet
cable which is easier than wifi):
https://unix.stackexchange.com/questions/253030/how-to-setup-network-without-wicd-or-networkmanager
In order to execute commands to repair the template, you'll need to
start a root shell from dom0 like this:
$ qvm-run -u root vmname 'xterm'
Good luck!
--
Chris Laprise,
tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886