On 01/25/18 13:27, Marek Marczykowski-Górecki wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, Jan 25, 2018 at 01:05:04PM +0200, Ivan Mitev wrote:
Hi,
IIRC in R3.2 VMs were started at boot time according to their dependency on
other VMs. Eg. - for a basic setup without whonix/tor/... - sys-net would
start first, then sys-firewall, and then other VMs configured to start at
boot time (in my case sys-usb, untrusted and work).
In R4.0 (rc3) I see that all the VMs start in parallel at boot time.
/usr/lib/systemd/system/[email protected] don't show any qubes specific VM
dependency mechanism, and neither do systemctl list-dependencies nor
systemd-analyze critical-chain qubes-vm@sys-firewall (for instance) show a
dependency on sys-net.
Q: is starting *all* the VMs in parallel the "new" way in R4.0 ?
Yes. Starting a VM (same as in R3.2) implicitly start also its network
dependencies. What is improved in R4.0 that simultaneous requests for
starting the same VM (for example both work VM and personal VM require
starting sys-firewall) are queued and if VM is already running it
doesn't try to start it again.
Thanks for the explanation...
I'm asking because each time I reboot, sys-net consistently fails with the
error message below so I'm wondering whether I'm hitting a totally unrelated
bug (in which case I'll open an issue) or if VMs in 4.0 have to be started
in a specific order but the mechanism isn't implemented yet (or doesn't work
in my case):
`Start failed: invalid argument: network device with mac [...] already
exists`
This looks like the problem when sys-net is restarted while sys-firewall
was still running. See here:
https://github.com/QubesOS/qubes-issues/issues/3163
https://github.com/QubesOS/qubes-issues/issues/1426
I guess what happened is:
1. sys-net starts
2. sys-firewall starts
3. sys-net crashes
4. sys-net fails to start again
Ah, I see...
I was 99% sure that the problem was startup concurrency because sys-net
would then start fine after all the other VMs were stopped. My bad :)
So, the question is why sys-net crashes. Take a look at
/var/log/xen/console/guest-sys-net.log and
/var/log/qubes/vm-sys-net.log.
/var/log/qubes/vm-sys-net.log didn't have any helpful info, but I see
some panic logs in guest-sys-net.log ; I'll try to debug it when time
allows.
Thank you !
Ivan
- --
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-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlppvy0ACgkQ24/THMrX
1yy5+gf9E6n4lFQzh8T6wMmrfMdcGxKE7PHDvhRvgi434n6Ykv+2/SRDIQmqYimQ
XfAR2cHLfSVytopYO/P7EJl7bNqcsh1c4vI+RBShYy0UD8Lc4Vvq8lYxaTldIIz/
xiG+/wAhR4ealpmeSNWdFsL1ksQEItYzFtkUQIuKSNlUool9QHDnjTxbtWvq9sDL
weq2ELAtD9Z/K6QxZ4Vlol5ORxFd1NNPlPtxQZZmTBe2vKT14eEFcvq5JPfLubkJ
LRw1GG33g+V8KagdaRfgo6ZS70iOIX5anrh3pnsJtiTeZW89ClfGUMtt9ZhJuIZ0
n6zDAUy352Kt83pEGY/Nj5v6rga9rg==
=x2xp
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" 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-devel/1caed751-19eb-1323-6c6a-a549c0f1c1dc%40maa.bz.
For more options, visit https://groups.google.com/d/optout.
