Hi everyone one, I’ve a problem with sys-net service that none of the dirs exist are persistent…I tired to make a script on /rw/config that actually execute some nmcli operations to connect into wifi with a stored SSID and pass, and it’s fully work when I execute it alone…and also made it as autorun…

When configuring Qubes OS after installation, did you select “Make sys-net disposable”? You can check by pasting the output of qvm-ls | grep sys-net executed in dom0 here.

should i make it non-disposable ?

If you want persistence, it’s going to have to be an AppVM and not a DispVM. Once you make it an AppVM, you can make it selectively persistent (only certain files/directories) via custom-persist. How to make any file persistent (bind-dirs) — Qubes OS Documentation

thanks brother, durring that time i sent last message, i searched a bit and fixed everything, thanks )) sys-net was configured as dispvm, i had to make a new qube and name it sys-net and switch some other stuff, beside the post forgot to mention to disallow the autorun for the old sys-net qube and c…

See also: [image] Customize a named disposable using the vm-config feature Community Guides Intro This is a technique for automatically passing custom information to named disposables as they boot up. Our example case will be making a disposable sys-net remem…

Problem with sys-net dirs persistence

User Support

parulin December 1, 2025, 9:00pm 7