Sys-net vm not starting properly [4.1.0-rc3] [Lenovo Thinkpad X13]


I am somewhat new to Qubes and am trying to run it on my Lenovo X13 laptop [1]

While the default fedora VM is starting, the sys-net VM is always restarting.
Since with sys-net missing, it seems that the other VMs (as fedora or fw) fail to get proper network routes.

The pop-up error message reads

Que Status: sys-net
Qube sys-net has failed to start: internal error: Unable to reset PCI device 0000:02:00.0: internal
error: Active 0000:02:00.2 devices on bus with 0000:02:00.0. not doing bus reset

which looks to me like a clash between the two enumerated devices .0 vs .2 ??

So far, I have not found been able to grep something in the dom0’s logs, but probably I have not found the corresponding service unit yet for the right journal?

I already tried to switch the sys-net VM from HVM to PV (without a better idea) - but without success.

Maybe somebody has an idea what could be breaking my sys-net here? (and where I could take a closer look in which logs/journals?)

Cheers and thanks

Machine: Type: Laptop System: LENOVO product: 20UGS00800 v: ThinkPad X13 Gen 1 serial:
Mobo: LENOVO model: 20UGS00800 serial: UEFI: LENOVO v: R1CET56W(1.25 ) date: 09/15/2020

CPU: Info: 8-Core model: AMD Ryzen 7 PRO 4750U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 rev: 1 cache:
L2: 4 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 54301
Speed: 1397 MHz min/max: 1400/1700 MHz boost: enabled Core speeds (MHz): 1: 1397 2: 1397 3: 1397 4: 1397 5: 1397
6: 1397 7: 1397 8: 1397 9: 1397 10: 1397 11: 1397 12: 1397 13: 1397 14: 1397 15: 1397 16: 1397

Did you find a solution?

I have the same issue. Lenovo Thinkpad with Qubes 4.1.0 official release.

Also dragging a window in dom0 (without any VM running) is not smooth, it is feels like my CPU is frozen, although according to stats is used at around 1%.

Could this be an answer to your problem?