(Qrexec not working) "qubes-qrexec.service" could not be found

[apparatus]

@ezpect

In dom0. Maybe I should have done it in both? Why? I’ll do it once I use the qubes computer tomorrow again.

qrexec-agent is only used in VMs:

Qrexec: secure communication across domains

@ezpect

I have not checked. I don’t think so necessarily since the blockchain qube for example was running (I was installing bitcoin core) and it was allowed Qrexec access then and there. Why? I can check that as well.

There was a comment that running monero blockchain in qube could cause these errors:

Boot time of 25 minutes due to fragmentation of monero blockchain [solved]

The plot just seemed to show that qubesd.service took over 15 minutes again. journalctl -u qubesd.service gave helpful info though, for each reboot major stalls occur with this each time: May 29 21:30:33 dom0 systemd[1]: Starting Qubes OS daemon... May 29 21:35:06 dom0 qubesd[1974]: Reflinked file: '/var/lib/qubes/appvms/crypto/private.img' -> '/var/lib/qubes/appvms/crypto/private.img.44@2023-05-30T03:56:38Z~j3nypgxl' May 29 21:35:09 dom0 qubesd[1974]: Renamed file: '/var/lib/qubes/appvms/c…