I've attached all scripts for you:
If you store those scripts in dom0 unter ~/bin you can run those scripts without changing to the directory, as ~/bin is included in the PATH environment variable (in dom0: echo $PATH )
*** create-t-fedora-25-minimal.sh
this script will download and clone a fedora-25-minimal template.
it will install all needed packages in the template.
(the reason why I clone the template is that I like to have the original template untouched. The original fedora-25-minimal template will be hidden in Qubes Manager to get a better overview)
*** qvm-destroy
is just a helper script which will kill a VM and remove it.
I'm using qvm-destroy in my scripts so that I can run those scripts even when the AppVMs are in place already and I want to reinstall. With that I can rebuild all my sys-vms within a very short time.
*** create-my-sysvms.sh
this script will remove and then recreate the 3 sys-vms.
after this script you'll end up with running freshly installed sys-net, sys-firewall and sys-usb.
This scripts assumes that the first script has been run already (creation of fedora-minimal-template).
*** create-default-sys-vms.sh
this script will create the 3 sys-vms using the fedora-25 default image which is slightly bigger but might have all drivers etc. installed.
I've just used it to test out my other minimal-script :-)
So it can be used to migrate from the standard fedora-23 to fedora-25 sys-vms.
If you have any question regarding those scripts, do not hesitate
to contact me.
I am using all sys-vms based on my t-fedora-25-minimal template and they work fine.
If you start up the new sys-usb it might be that you get a 2nd nm-applet icon in the taskbar. I haven't been able to disable the start of nm-applet in sys-usb and as such I'm just killing the nm-applet through dom0:
I'm running this command in dom0 in a script which is executed when I login into qubes:
qvm-run sys-usb "killall nm-applet"
You need to find out what your wifi card is and then install the proper driver. I think this was covered here in the mailinglist already.
You could look into your current sys-net (based on the original template) and then use lsmod to find which kernel modules are running and find the proper drivers - but this is something I am not that familiar with.
Someone more skilled might help you out
Just one more thing which might be usefull for your new sys-net VM if you're working with a WWAN/LTE-card.
I have a scripts which auto-attached my LTE card to the sys-net VM:
#!/bin/bash