In fedora-39-xfe template Settings → Advanced tab uncheck “Include in memory balancing” and set “Initial memory” to 2 GB.
Okay I had to set it to 3gb, now It worked, I succesfully installed the driver in the template, rebooted it to apply changes, in fedora-39-xfe I first set virt. mode to default (pvh), then kernel back to default.
Then I restarted sys-net, attached my wifi dongle via usb widget to sys-net, but in my network widget there is still no network devices avaible 
What’s the output of these commands in sys-net with WLAN Adapter attached to it?
uname -r
ip link
lsmod | awk '$1 ~ /88/ {print}'
ls -l /lib/modules/$(uname -r)/kernel/drivers/net/wireless/
cat /etc/modprobe.d/8812au.conf
What’s the output of this command in sys-net?
find /lib/modules -name "8812au.ko"
It seems the driver wasn’t installed. I guess there was some error during driver installation.
Post the output of the install-driver.sh script in the fedora-39-xfe template with HVM mode and (provided by qube) kernel:
sudo ./install-driver.sh
What’s the output of this command in fedora-39-xfe and in sys-net?
uname -r
For some reason you have kernel 6.9.8-100 in sys-net here:
But the driver was installed for kernel 6.9.9-100 in fedora-39-xfe:
You can try to run this command in fedora-39-xfe to build the driver for all kernel versions:
sudo dkms autoinstall --all
Ok, now it seems that sys-net kernel has correct version.
What’s the output of these commands in sys-net with WLAN adapter attached now?
uname -r
ip link
lsmod | awk '$1 ~ /88/ {print}'
ls -l /lib/modules/$(uname -r)/extra/
sudo modprobe 8812au
What’s the output of the commands in sys-net with WLAN adapter attached?
uname -r
ip link
lsmod | awk '$1 ~ /88/ {print}'
ls -l /lib/modules/$(uname -r)/extra/
sudo modprobe 8812au
Detach WLAN adapter from sys-net.
Run this command in sys-net terminal:
sudo journalctl -f -n0
Attach WLAN adapter to sys-net.
Post the log output in the terminal.
Are you sure you’ve attached the WLAN adapter from sys-usb to sys-net using the Qubes Devices widget in tray?
Try to attach it again and see if there will be any output in the sys-net terminal.