Sys-net not not searching for wifi network or connecting after being disconnected

[Insurgo]

@NicholasTrust

I’m using a privacy beast from insurgo.ca. I am also already using Debian as my default Disposable.

Clean install of Qubes 4.1.1 will require you to change memory assignment of sys-net yourself.

If you experience loss of networking, I recommended changing the default memory assignment to something around 500Mb.

Repeating:

@Insurgo

You will have to change sys-net and sys-usb default assigned memory settings to 450-500 Mb minimally to not lose webcam/network randomly (Will not be fixed upstream)

The default will not be changed upstream. Some services might be deactivated by default later on, as discussed in referred issue in previous post in thread (Fedora related, while discussions are relevant to other service qubes as well).

Where important traces for troubleshooting of issues would still be the same and important to others as well:

@Insurgo

I would recommend starting your qubes session by opening a shell on sys-net and calling sudo journalctl -f . It might be a faulty driver causing it to oops the kernel, amongst other things. Depending of the network card used, there might be a lot of kernel modules dependencies, and maybe one of them is having a memory leak.

I cannot replicate the issue on my side: Fedora-36-dvm based sys-net with 500Mb assigned.
Of course, you have to shut down sys-net first (dom0: qvm-shutdown --force --wait sys-net)
Open sys-net Settings, Advanced tab and set Initial memory to 500mb:

Apply, OK. And then start sys-net again.
(dom0: qvm-start sys-net will do, or starting a new qube will also start sys-net as well as part of its startup.)