Sys-net fails to start when kernel version 7.1.10-1.fc41 is assigned

I am using QubesOS with Fedora 43 Xfce and kernel version 7.1.10-1.fc41. All associated AppVMs are running without any issues, with the exception of sys-net. sys-net currently only runs when kernel version 6.19.14-1.fc41 is assigned.
When starting “sys-net” with kernel 7.1.10-1.fc41, several message windows appear with the following content: “Qube sys-net could not be started: No connection could be established to the qrexec agent for 60 seconds. Details can be found in /var/log/xen/console/guest-sys-net.log.” I have checked the log file but could not find anything that might indicate the cause. I’ve no idea what exactly I should be looking for in the log either.
I’ve read the documentation and have already increased the allocated memory. But none of it has worked.
Perhaps someone is already familiar with this problem or has a helpful tip to guide my search.

I recall a similar issue on GitHub issues, but that arose when waking
from sleep with an active WiFi. I’m not familiar with this problem.

You have not provided enough information at this stage:
Is your sys-net disposable?
Is it also sys-usb?
What devices are attached?
Have you tried later kernels with Fedora-44-xfce?
Have you tried later kernels with Debian-13-xfce?

Check the logs under /var/log/xen/console for sys-net-dm and sys-net

If you have a number of devices attached, can you remove them all, check
sys-net starts, and then add them back individually.

Bonus - if you are able, can you boot sys-net using the native kernel?
(I think on Fedora you can do this simply be selecting “provided by
qube” in Kernel settings: check what kernel you are then running using
uname -ar.)

I never presume to speak for the Qubes team. When I comment in the Forum I speak for myself.

Thanks for your reply.

sys-net is not disposable
sys-usb is running fine and not involved
there is WiFi and ethernet adapter attached (WiFi mostly used)

I’ll give Fedora 44 a try.

Other AppVM use debian-13-xfce, not system VM.

I’ve seen and checked sys-net-dm sys-net logs but I don’t know what to search for (error, fatal, warning, other terms…)

Just installed Fedora 44, assigned it to sys-net, increased memory to 2GB but rebooting sys-net still fails. Assigned kernel 6.19.14-1.fc41 and it works again.
sys-usb still runs without any issue (template ist sys-dvm, kernel 7.1.10-1.fc41)

Installed another “sys-net” and hit the very same problem. But the last entry in sys-net.log with kernel 7.1.10-1.fc41 was: dwmac-motorcomm 0000:00:07.0: failed to disable L1 state: -22

So i assume it’s a driver related issue.

Thanks for your reply.

  1. works
  2. I modified the kernel options as specified: “pcie_aspm=off”
    Without the ethernet device the VM starts successfully with WiFi only
    With ethernet device attach the error occurs
  3. see 2.
  4. I performed shutdown changed devices and (re)started the qube

This command has been run in dom0:

lspci -nnk | grep -A3 -i ether
2d:00.0 Ethernet controller [0200]: Motorcomm Microelectronics. YT6801 Gigabit Ethernet Controller [1f0a:6801] (rev 01)
Subsystem: AIstone Global Limited Device [1d05:1382]
Kernel driver in use: pciback
Kernel modules: dwmac_motorcomm

Now the last lines of corresponding log file in dom0:

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Set up automount .[0;1;39mefi.automount.[0m - EFI System Partition Automount.

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-udevd.service.[0m - R…ager for Device Events and Files…

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Finished .[0;1;39msystemd-sysctl.service.[0m - Apply Kernel Variables.

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-resolved.service.[0m - Network Name Resolution…

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Started .[0;1;39mqubes-db.service.[0m - Qubes DB agent.

[2026-09-16 15:02:30] Starting .[0;1;39mqubes-sysinit.service.[0m - Init Qubes Services settings…

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-random-seed.service.[0m - Load/Save OS Random Seed…

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Finished .[0;1;39msystemd-random-seed.service.[0m - Load/Save OS Random Seed.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Finished .[0;1;39mqubes-sysinit.service.[0m - Init Qubes Services settings.

[2026-09-16 15:02:30] Starting .[0;1;39mqubes-rootfs-resize.service.[0m - Adjust root filesystem size…

[2026-09-16 15:02:30] Starting .[0;1;39mqubes-setup-minimal-vm.se….[0mminimal vm runtime configuration…

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-timesyncd.service.[0m - Network Time Synchronization…

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Started .[0;1;39msystemd-udevd.service.[0m - Ru…anager for Device Events and Files.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Started .[0;1;39msystemd-resolved.service.[0m - Network Name Resolution.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Reached target .[0;1;39mnss-lookup.target.[0m - Host and Network Name Lookups.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Started .[0;1;39msystemd-timesyncd.service.[0m - Network Time Synchronization.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Reached target .[0;1;39mtime-set.target.[0m - System Time Set.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Found device .[0;1;39mdev-zram0.device.[0m - /dev/zram0.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Found device .[0;1;39mdev-hvc0.device.[0m - /dev/hvc0.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Finished .[0;1;39mqubes-rootfs-resize.service.[0m - Adjust root filesystem size.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Found device .[0;1;39mdev-xvdb.device.[0m - /dev/xvdb.

[2026-09-16 15:02:30] [.[0;32m OK .[0m] Reached target .[0;1;39mswap.target.[0m - Swaps.

[2026-09-16 15:02:30] Mounting .[0;1;39mtmp.mount.[0m - Temporary Directory /tmp…

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-fsck@dev-xvdb.ser….[0m- File System Check on /dev/xvdb…

[2026-09-16 15:02:30] Starting .[0;1;39msystemd-oomd.service.[0m - Us…space Out-Of-Memory (OOM) Killer…

[2026-09-16 15:02:31] [.[0;32m OK .[0m] Mounted .[0;1;39mtmp.mount.[0m - Temporary Directory /tmp.

[2026-09-16 15:02:31] [ 4.819785] piix4_smbus 0000:00:01.3: SMBus Host Controller not enabled!
[2026-09-16 15:02:31] [ 4.836635] ehci-pci 0000:00:05.0: EHCI Host Controller
[2026-09-16 15:02:31] [ 4.836855] ehci-pci 0000:00:05.0: new USB bus registered, assigned bus number 1
[2026-09-16 15:02:31] [ 4.838251] ehci-pci 0000:00:05.0: irq 39, io mem 0xf201b000
[2026-09-16 15:02:31] [.[0;32m OK .[0m] Started .[0;1;39msystemd-oomd.service.[0m - Userspace Out-Of-Memory (OOM) Killer.

[2026-09-16 15:02:31] [.[0;32m OK .[0m] Finished .[0;1;39msystemd-fsck@dev-xvdb.ser…e.[0m - File System Check on /dev/xvdb.

[2026-09-16 15:02:31] [ 4.845247] ehci-pci 0000:00:05.0: USB 2.0 started, EHCI 1.00
[2026-09-16 15:02:31] [ 4.845423] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 7.01
[2026-09-16 15:02:31] [ 4.845457] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[2026-09-16 15:02:31] [ 4.845502] usb usb1: Product: EHCI Host Controller
[2026-09-16 15:02:31] [ 4.845519] usb usb1: Manufacturer: Linux 7.1.10-1.qubes.fc41.x86_64 ehci_hcd
[2026-09-16 15:02:31] [ 4.845541] usb usb1: SerialNumber: 0000:00:05.0
[2026-09-16 15:02:31] [ 4.845906] hub 1-0:1.0: USB hub found
[2026-09-16 15:02:31] [ 4.845938] hub 1-0:1.0: 6 ports detected
[2026-09-16 15:02:31] [ 4.851186] zram: Removed device: zram0
[2026-09-16 15:02:31] [.[0;32m OK .[0m] Finished .[0;1;39mqubes-setup-minimal-vm.se….[0my minimal vm runtime configuration.

[2026-09-16 15:02:31] Starting .[0;1;39mqubes-mount-dirs.service.[0m …itialize and mount /rw and /home…

[2026-09-16 15:02:31] [ 4.983425] EXT4-fs (xvdb): mounted filesystem 761e6b4e-3489-469a-954a-ae7e2b2bdd2f r/w with ordered data mode. Quota mode: none.
[2026-09-16 15:02:31] [ 5.020271] FDC 0 is a S82078B
[2026-09-16 15:02:31] [ 5.087729] usb 1-1: new high-speed USB device number 2 using ehci-pci
[2026-09-16 15:02:31] [ 5.112063] input: PC Speaker as /devices/platform/pcspkr/input/input5
[2026-09-16 15:02:31] [ 5.131391] dwmac-motorcomm 0000:00:07.0: failed to disable L1 state: -22

Best regards
CC