The Settings of an Appvm application are not persistent between reboots

I have installed mullvad-vpn from a rpm package in the Fedora template vm.
The application works fine in the appvm associated with the template but its settings are not persistent between the appvm reboots. Is there a solution?

Store the settings in /rw, (which includes /home and /usr/local) which is not reset on reboot.
Or use bind-dirs to make files from / which would normally be reset,

  1. Open Terminal in the appVM where you have installed Mullvad VPN.
  2. Type the following command to create a new Mullvad VPN configuration file:
sudo touch /rw/config/mullvad-vpn.conf
  1. Open the Mullvad VPN configuration file using your preferred text editor:
sudo nano /rw/config/mullvad-vpn.conf
  1. Copy and paste the Mullvad VPN settings from the original configuration file, which is located in the Fedora template VM at the following path:
  1. Save and close the configuration file.
  2. Type the following command to make the configuration file persistent:
sudo qvm-service --add mullvad-vpn --opts config=/rw/config/mullvad-vpn.conf
  1. Reboot the appVM to ensure that the changes take effect.

After following these steps, your Mullvad VPN settings should be persistent between appVM reboots.

1 Like

At point 1. you said that you should be working in the appVM where you
had installed Mullvad VPN, but now you refer to a “Fedora template VM”.
That’s quite confusing.

This looks like nonsense.
qvm-service is a dom0 application, not available in an appVM.
It doesn’t have an --add option, and it doesn’t support use of --opts
like that. I don’t know what you were thinking of.

No one will be able to follow these steps, and they certainly wont result in
VPN settings becoming persistent.
They are simply confused.

I never presume to speak for the Qubes team. When I comment in the Forum or in the mailing lists I speak for myself.
1 Like

He wasn’t.

1 Like