3hhh

> That'd just be "don't call the function that updates the X property". But then you'd be in the rabbit hole of who gets priority when the client changes the...

Btw I think that this is fairly easy to implement with the current architecture and I guess I'll give it a shot once I have some time. From my perspective...

> From my perspective it doesn't even require any changes of the existing code. After some more thinking I believe that some qubes-rpc aliasing policy syntax (translate a qrexec call...

Hm I implemented such a qrexec proxy VM with Python asyncio and it incurred a 30-40% performance impact vs qrexec without proxy. Not great, but not too bad either. @brendanhoar...

> While having a proxy for some calls is probably a useful feature (as you said, for example for network-based qrexec), I don't think it should be for all the...

Here's the code: https://github.com/3hhh/qubes-qrexec-proxy

> I have a little bash menu script I run. Hitting 'm' mutes all VMs and dom0, while 'M' unmutes all. I just added something like that [here](https://github.com/3hhh/qubes-terminal-hotkeys/blob/master/util/qubes-pactl). However the...

As this issue is 5 years old, I rediceded and added a daemon to execute arbitrary code - incl. VM mutes - on VM starts, stops, ... etc. [here](https://github.com/3hhh/qubes-callbackd).

This is no bug, but a user error / misunderstanding. Please close. @sjug The `qubes-firewall-user-script` is ecxecuted once on Qubes firewall start as documented. If you want your own NAT...

Sounds like memory swapping. Try non-dynamic memory allocation and try to disable swapping in dom0.