On 02/07/18 10:22, haaber wrote:
I remember some issues with reattaching in the past, but recently, the qvm-shutdown
--wait --force sys-net && qvm-start sys-net seems to be working.
This sounded even more interesting than the script. But: It does not
work in my Q4rc4 install. last experience of this type was with
sys-whonix and anon-whonix. The latter running, the former did not power
off (even with --force); after some wait I kill it, but it won't reboot:
on boot it spills out "network device with MAC ... already exists"
before dying. I had to power off anon-whonix, then restart sys-whonix.
Same thing happen with the sys-net - sys-firewall - sys-whonix -
anon-whonix chain. I need to power off all of them to get sys-net to
rebbot, which is, frankly, annoying. So finally a script is a good idea,
even if Ilpo's did not work out of the box in my install (may be a Q3.2
- Q4 issue).
FWIW on R4.0rc4 I don't need to poweroff/boot any VM depending on
sys-net: 'qvm-kill sys-net' (or clean shutdown) followed by 'qvm-start
sys-net' works perfectly well, ie. network connectivity is automatically
restored in sys-firewall and other dependent VMs.
Note that I ran 'qvm-prefs sys-firewall netvm sys-net' (once after a
complete reboot) after reading Awokd's reply, where he pointed to the
doc explaining how to reconnect sys-firewall after a sys-net crash [1].
So maybe that step is required to get "automatic" re-connection.
[1] https://www.qubes-os.org/doc/firewall/
--
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/2685ee5f-5863-fcce-104d-f60eac9a8f9e%40maa.bz.
For more options, visit https://groups.google.com/d/optout.
