VMs cannot start (Error, 0), eek... and fixed

[Daniel Wilcox]

Hello, I searched the archives and saw this has come up before regarding firewall rules.
https://github.com/QubesOS/qubes-issues/issues/1570

I had half an email composed when I tried something and it unexpectedly worked.

So for posterity I wanted to add is that it is possible that *no* VM will start if you have exceeded the maximum number of firewall rules on *any* VM.

find /var/lib/qubes -name firewall.xml -exec wc -l '{}' \;

# found offending VMs with 38 - 40 lines (and hence 36-38 rules)

On a side note, does anyone have great ideas for dealing with CDNs like Fastly?  Which allocate the same host IP for a service, say pypi.python.org, in many /24s.

Big phew! and cheers,

=D

[Drew White]

What was the EXACT error message that showed up for you?

[Daniel Wilcox]

Good question, I appear to have dismissed the messages already.  It was closest to what is the subject of the email, either 'vm cannot start' or 'cannot start vm', and then '(Error, 0)'.  Hope that helps,

=D

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8afc01d9-f809-48ce-9a4a-56a186ba5138%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.