xaki23

i can assure you firmware-util.sh is not the only usecase for your flashrom build. while i am a user of your script, i also used your flashrom build for usecases...

actualy, more tricky. even if i set "qvm-features mirage-fw gui ''" ... (warning: two single ticks for "empty value", followed by a doubletick for "quoted string in github ticket") ......

afaict this still happens with a 20190416 build (aka "beyond the icmp issue"). i moved the backup vm (which gets restarted hourly) to a separate mirage-firewall instance some months ago,...

built and deployed on two systems in a role that triggers this bug 2-3 times a week. (fw for backup-sync vm that gets started/stopped once per hour)

2019-12-17 04:36:41 -00:00: INF [xenstore.client] ** XenStore with unwatch patch ** .... 2019-12-19 17:33:22 -00:00: INF [net-xen backend] Frontend asked to close network device dom:3167/vif:0 2019-12-19 17:33:22 -00:00: INF [client_net]...

there is still a benefit to deploying as a template: you can install templates without risking a dom0 compromise. so my mission there is still to have a mirage-firewall template...

what version of mirage-firewall is this? (or: is your mirage-firewall using "pv" or "pvh"?)

as part of the whole mess around (the lower parts of) https://github.com/QubesOS/qubes-issues/issues/6162 and https://github.com/Solo5/solo5/pull/516 i can confirm this branch works at least as much as any other, if not better....

@linse it was running only for about 6-7 hours at the time that happened, there had been about 15 downstream vm starts during that time. unless i find a reliable...

just happened again, right after starting a downstream VM. difference to the first observed case was that this time it didnt keep running for long. the packets are mostly null...