qubes-issues
qubes-issues copied to clipboard
QubesOS
VM with USB controller unable to start with more than 2200MB memory
Qubes OS release
debian-11: bullseye-testing enabled in qubes-r4.list dom0: 4.1 "testing-updates" xen-hvm-stubdom-linux-1.2.4-1
Brief summary
Above about 2200MB, an HVM with assigned USB controller is unable to start.
Steps to reproduce
- Create HVM with memory = 3072, memory balancing off, template = debian-11
- Assign a USB controller
- Start the VM.
Expected behavior
VM starts.
Actual behavior
VM fails to start.
Popup message:
Qube test-pci has failed to start: qrexec-daemon startup failed: ... qrexec-daemon[748421]: qrexec-daemon.c:135:sigchld_parent_handler: Connection to the VM failed
Workaround
The VM starts if I qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux from 1.2.4-1 to 1.2.3-1.
Edit: only need to downgrade xen-hvm-stubdom-linux
I usually run sys-usb with 300M. I have noticed that I can no longer start it at 4000.
Interestingly, there is a lower limit, but I can breach that limit by stepping upwards. i.e. Increase memory to 3000, cannot start. Assign 2000, starts. Assign 2400, starts. Assign 2800, starts. Assign 3200, starts. Assign 3600, starts.
The error message when start fails is the same as I reported in #6824: "The kernel doesn't support reset from sysfs for PCI device..."
I ran into a similar issue recently, where trying to dd data onto a USB drive would crash sys-usb at 4-8 GB of memory, but lowering memory to 2 GB worked. This happened with both Debian and Fedora templates on 4.0.
Same issue with PCI passthrough + HVM. Same popup message. /var/log/libvirt/libxl/libxl-driver.log shows no relevant error though.
The "step up" trick didn't work for me.
3000MB - failed 2000MB - failed 1600MB - ok 1700MB - ok 1800MB - ok 1900MB - failed
There was actually another issue before, where if a HVM is given > 4096MB initial memory, it will start... then stop (Linux didn't appear to start in that VM.
Simply detatching the PCI device works too (still HVM). If I switch to PV, it's the same error. (It was broken before)
Workaround: I only did qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux. And it worked afterwards.
I can breach that limit by stepping upwards
For me, I can't step upwards beyond 2200MB (but haven't tried with increments smaller than 100MB)
The error message when start fails is the same as I reported in #6824: "The kernel doesn't support reset from sysfs for PCI device..."
Not found in my logs.
Workaround: I only did qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux. And it worked afterwards.
Same here, I only needed to downgrade xen-hvm-stubdom-linux.
Workaround: I only did
qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux. And it worked afterwards.
That is useful. It means the regression is in the stubdomain, which runs very little code. Basically a bare bones Linux, QEMU, and a small userspace.
I think QEMU versions changed recently and several patches have been applied for Qubes as well, last I checked.
I'm not entirely sure but this patch https://github.com/QubesOS/qubes-vmm-xen-stubdom-linux/commit/be8896ba2fae2e377aa236df4407bc7dbdcec60b for https://github.com/QubesOS/qubes-issues/issues/4321 might be the problem.
I have the same message:
qrexec-daemon startup failed: 2022-11-16 12:17:08.046 qrexec-daemon[26396]: qrexec-daemon.c:135:sigchld_parent_handler: Connection to the VM failed
on up-to-date R4.1.1 with fedora-36 or other template (e.g. fedora-35) when I'm trying to start qube that has USB controller attached to it. If I remove USB controller from list of the qube settings and keep everything else the same - the qubes starts.
I used 2000 MB of memory (without balancing) and it failed to start. I changed it to 1000 MB of memory (without balancing) and it started with USB Controller fine.
It's a huge issue. Good for me that I do not need decent amount of memory in this qube but in general that issue is a huge problem for some cases.
Maybe related issues: #7256 and #4321.
I've now updated a system I hadn't updated since mid-2022, and ran into this issue. I had sys-usb and sys-net set at 3000 MB, and they wouldn't start anymore with the new xen-hvm-stubdom-linux-1.2.5-1 that I got. I don't know which version I had before. Judging by my previous update date vs. package changelog, this should have been 1.2.4-1, but downgrading to that version didn't help wheras downgrading further to 1.2.3-1 did, which is consistent with the comments above. Still with the 1.2.4+ versions, setting the initial memory to 1500 MB enabled me to start these VMs.
While we're at it, any tips for conveniently switching between package versions on dom0 when network is not available (such as because of having bumped into a bug like this) or even ability to start VMs might be broken? Is there a standard Qubes feature for that? Ideally, a cache of previously installed packages would stay somewhere in dom0.
I have sys-usb with xen-hvm-stubdom-linux-1.2.5-1, able to start with
4000MB . Just saying.
Another data point: I also have xen-hvm-stubdom-linux-1.2.5-1, but my sys-usb won't start with 4000 MB memory. (It starts normally with 2000 MB.)
To be clear, I'm not saying that there is not some hard stop - just that on my system it isn't as low as reported. This is standard x230 with 16MB - I've reduced memory requirements for most qubes to mitigate what I think is bad memory handling - discussed elsewhere. My sys-usb usually has 300MB allocated, and is fine - no worse than other qubes. I seem to hit a ceiling above 4000, but haven't tried to find it precisely.
I have the same issue. Worked with > 2 GB and R4.0 and now doesn't anymore with same hardware on R4.1. HVM with USB controller attached are limited to 2 GB. That's no issue with things like sys-usb, but when running and IDE and developing / debugging embedded systems in Windows it's a bit tight and leads to a lot of waiting and paging.
And even with a similar Debian-minimal based qube. Once the IDE is loaded and the (Java-based) code generator kicks in, 2 GB is no fun. I use Linux based qubes when I can but some stuff is Windows only. These are the use cases where more memory = less waiting / better expirience and I hope this can be addressed soon.
My current workaround is another Windows PC / RDP ... but that's another 5 pounds to carry around when traveling. :-(
Obviously, if my ICE, logic analyzer and data loggers would work fine through sys-usb I wouldn't need to assign a USB controller to these qubes in the first plave. ;-) I'd love that solution the most.
I cannot start Windows 10 with USB controller even with 1800 MB, it shows no bootable device error.
And running Windows 10 with something useful on less than 2 GiB is already a problem.
P.S. I see that people struggle with this bug on forum a lot. On different OSes, including sys-usb qubes. Maybe this bug should be priorities somehow. Or known workarounds should be published to use enough memory in qubes.
Is it a diagnosed problem knowing that the bug is in xen-hvm-stubdom-linux and there is some patch about it:
https://github.com/QubesOS/qubes-vmm-xen-stubdom-linux/commit/be8896ba2fae2e377aa236df4407bc7dbdcec60b
Or is it not a working fix? Why is the bug not fixed for so long upstream?
Sorry for several posts in a row, but I want also note, that the topic's workaround does not work anymore (qubes-dom0-update --action=downgrade xen-hvm-stubdom-linux). Because the last working xen-hvm-stubdom-linux seems to be 1.2.3-1, and repos of Qubes OS R4.1 downgrade to 1.2.4-1 which is probably broken, too.
So, what is the best way to downgrade to 1.2.3-1 version if it is possible?
@jamke you are right, now the downgrade installs 1.2.4-1, so you have to explicitly install 1.2.3-1. In my case on Qubes OS 4.1 it is with:
sudo qubes-dom0-update xen-hvm-stubdom-linux-1.2.3-1.fc32
but it's possible on 4.2 it's a bit different (something different instead of fc32).
Can somebody with R4.2 check this, maybe it is somehow miraculously fixed?
Or add affects-4.2 if needed.
Can somebody with R4.2 check this, maybe it is somehow miraculously fixed? Or add
affects-4.2if needed.
I've tried this using sys-usb with 8 GB RAM and it works for me on R4.2 with these USB controllers:
lspci -vnn
00:0d.0 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller [8086:461e] (rev 02) (prog-if 30 [XHCI])
Subsystem: Dell Device [1028:0afe]
Flags: bus master, medium devsel, latency 0
Memory at 618d1c0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Capabilities: [b0] Vendor Specific Information: Len=00 <?>
Kernel driver in use: pciback
Kernel modules: xhci_pci
00:0d.2 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 [8086:463e] (rev 02) (prog-if 40 [USB4 Host Interface])
Subsystem: Dell Device [1028:0afe]
Flags: fast devsel, IRQ 16
Memory at 618d140000 (64-bit, non-prefetchable) [size=256K]
Memory at 618d1e2000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=16 Masked-
Kernel driver in use: pciback
Kernel modules: thunderbolt
00:0d.3 USB controller [0c03]: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #1 [8086:466d] (rev 02) (prog-if 40 [USB4 Host Interface])
Subsystem: Dell Device [1028:0afe]
Flags: fast devsel, IRQ 16
Memory at 618d100000 (64-bit, non-prefetchable) [size=256K]
Memory at 618d1e1000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=16 Masked-
Kernel driver in use: pciback
Kernel modules: thunderbolt
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller [8086:51ed] (rev 01) (prog-if 30 [XHCI])
Subsystem: Dell Device [1028:0afe]
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at 618d1a0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Capabilities: [b0] Vendor Specific Information: Len=00 <?>
Kernel driver in use: pciback
Kernel modules: xhci_pci
I think this problem may be hardware-specific for some USB controllers.
it works for me on R4.2 with these USB controllers:
Thanks, do any of these USB controllers have PCIe physical connection (so that you can populate PCIe slot of motherboard with it or remove)? I have problems with those.
Thanks, do any of these USB controllers have PCIe physical connection (so that you can populate PCIe slot of motherboard with it or remove)? I have problems with those.
I'm using laptop so no, they're from PCH/Thunderbolt.
I'm using laptop so no, they're from PCH/Thunderbolt.
That might be the difference.
I experience this or a similar problem on the certified NitroPC Pro running Qubes-OS 4.2 if the VM initial memory is set above 1300MB. This limit is the same for both a media VM using an extra PCIe-USB-controller and sys-usb using the builtin controller. I get the same behavior from sys-usb with the extra controller card removed from the machine. The VMs are all based on debian-12-xfce.
For sys-usb this isn't limiting me in any practical sense. The media vm however is barely usable, unfortunately. (Memory balancing doesn't happen despite beeing chect)
Brand: Micro-Star International Co., Ltd.
Model: MS-7D25
CPU: 12th Gen Intel(R) Core(TM) i9-12900K
Chipset: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers [8086:4660] (rev 02)
Graphics: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA controller])
RAM: 65373 Mb
QubesOS version: R4.2.0
BIOS: Dasharo (coreboot+UEFI) v1.1.2
Kernel: 6.1.62-1
Xen: unknown
[user@dom0 ~]$ qvm-pci
BACKEND:DEVID DESCRIPTION USED BY
dom0:00_00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers
dom0:00_02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1
dom0:00_06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0
dom0:00_14.0 USB controller: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller sys-usb (no-strict-reset=True)
dom0:00_14.2 RAM memory: Intel Corporation Alder Lake-S PCH Shared SRAM
dom0:00_14.3 Network controller: Intel Corporation Alder Lake-S PCH CNVi WiFi sys-wl
dom0:00_16.0 Communication controller: Intel Corporation Alder Lake-S PCH HECI Controller #1
dom0:00_17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode]
dom0:00_1c.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #1
dom0:00_1c.1 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #2
dom0:00_1c.2 PCI bridge: Intel Corporation
dom0:00_1f.0 ISA bridge: Intel Corporation Z690 Chipset LPC/eSPI Controller
dom0:00_1f.3 Audio device: Intel Corporation Alder Lake-S HD Audio Controller
dom0:00_1f.4 SMBus: Intel Corporation Alder Lake-S PCH SMBus Controller
dom0:00_1f.5 Serial bus controller: Intel Corporation Alder Lake-S PCH SPI Controller
dom0:01_00.0 Non-Volatile memory controller: Kingston Technology Company, Inc.
dom0:03_00.0 USB controller: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller media (no-srict-reset=true)
dom0:04_00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V sys-net
With initial memory set to 1350MB:
[user@dom0 ~]$ qvm-start sys-usb
qrexec-daemon startup failed: 2024-01-20 22:33:26.130 qrexec-daemon[14757]: qrexec-daemon.c:144:sigchld_parent_handler: Connection to the VM failed
[user@dom0 ~]$ journalctl -xf
an 20 22:33:23 dom0 qubesd[2379]: vm.sys-usb: Starting sys-usb
Jan 20 22:33:23 dom0 lvm[1435]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
Jan 20 22:33:23 dom0 lvm[1435]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
Jan 20 22:33:23 dom0 lvm[1435]: No longer monitoring thin pool qubes_dom0-vm--pool-tpool.
Jan 20 22:33:23 dom0 lvm[1435]: Monitoring thin pool qubes_dom0-vm--pool-tpool.
Jan 20 22:33:23 dom0 libvirtd[2410]: internal error: Unable to reset PCI device 0000:00:14.0: no FLR, PM reset or bus reset available
Jan 20 22:33:23 dom0 kernel: loop3: detected capacity change from 0 to 1045968
Jan 20 22:33:23 dom0 kernel: loop4: detected capacity change from 0 to 1045968
Jan 20 22:33:23 dom0 kernel: pciback 0000:00:14.0: xen_pciback: vpci: assign to virtual slot 0
Jan 20 22:33:23 dom0 kernel: pciback 0000:00:14.0: registering for 27
Jan 20 22:33:23 dom0 kernel: xen-blkback: backend/vbd/27/51712: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen: registering gsi 22 triggering 0 polarity 1
Jan 20 22:33:23 dom0 kernel: Already setup the GSI :22
Jan 20 22:33:23 dom0 kernel: xen-blkback: backend/vbd/27/51728: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jan 20 22:33:23 dom0 kernel: xen-blkback: backend/vbd/27/51744: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jan 20 22:33:23 dom0 kernel: xen-blkback: backend/vbd/27/51760: using 1 queues, protocol 1 (x86_64-abi) persistent grants
Jan 20 22:33:24 dom0 qubesd[2379]: vm.sys-usb: Setting Qubes DB info for the VM
Jan 20 22:33:24 dom0 qubesd[2379]: vm.sys-usb: Starting Qubes DB
Jan 20 22:33:24 dom0 audit[14751]: CRED_ACQ pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 runuser[14751]: pam_unix(runuser:session): session opened for user user(uid=1000) by (uid=0)
Jan 20 22:33:24 dom0 kernel: audit: type=1103 audit(1705786404.593:646): pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 kernel: audit: type=1105 audit(1705786404.593:647): pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 audit[14751]: USER_START pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 runuser[14751]: pam_unix(runuser:session): session closed for user user
Jan 20 22:33:24 dom0 audit[14751]: USER_END pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 audit[14751]: CRED_DISP pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 kernel: audit: type=1106 audit(1705786404.600:648): pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 kernel: audit: type=1104 audit(1705786404.600:649): pid=14751 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 qubesd[2379]: vm.sys-usb: Activating the sys-usb VM
Jan 20 22:33:24 dom0 audit[14755]: CRED_ACQ pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 runuser[14755]: pam_unix(runuser:session): session opened for user user(uid=1000) by (uid=0)
Jan 20 22:33:24 dom0 kernel: audit: type=1103 audit(1705786404.612:650): pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 kernel: audit: type=1105 audit(1705786404.612:651): pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:24 dom0 audit[14755]: USER_START pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:26 dom0 runuser[14755]: pam_unix(runuser:session): session closed for user user
Jan 20 22:33:26 dom0 audit[14755]: USER_END pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:26 dom0 audit[14755]: CRED_DISP pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:26 dom0 kernel: audit: type=1106 audit(1705786406.130:652): pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:26 dom0 kernel: audit: type=1104 audit(1705786406.130:653): pid=14755 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="user" exe="/usr/sbin/runuser" hostname=? addr=? terminal=? res=success'
Jan 20 22:33:26 dom0 libvirtd[2410]: internal error: Unable to reset PCI device 0000:00:14.0: no FLR, PM reset or bus reset available
Jan 20 22:33:26 dom0 qubesd[2379]: vm.sys-usb: Start failed: qrexec-daemon startup failed: 2024-01-20 22:33:26.130 qrexec-daemon[14757]: qrexec-daemon.c:144:sigchld_parent_handler: Connection to the VM failed
[user@dom0 ~]$ sudo lspci -vnn
00:00.0 Host bridge [0600]: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers [8086:4660] (rev 02)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0
00:02.0 VGA compatible controller [0300]: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA controller])
DeviceName: VGA compatible controller
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 152
Memory at 51000000 (64-bit, non-prefetchable) [size=16M]
Memory at 60000000 (64-bit, prefetchable) [size=256M]
I/O ports at 1000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Capabilities: [320] Single Root I/O Virtualization (SR-IOV)
Kernel driver in use: i915
Kernel modules: i915
00:06.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 [8086:464d] (rev 02) (prog-if 00 [Normal decode])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 146
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: [disabled] [16-bit]
Memory behind bridge: 50600000-506fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Capabilities: [a0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [220] Access Control Services
Capabilities: [150] Precision Time Measurement
Capabilities: [280] Virtual Channel
Capabilities: [a30] Secondary PCI Express
Capabilities: [a90] Data Link Feature <?>
Capabilities: [a9c] Physical Layer 16.0 GT/s <?>
Capabilities: [edc] Lane Margining at the Receiver <?>
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller [8086:7ae0] (rev 11) (prog-if 30 [XHCI])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: medium devsel, IRQ 22
Memory at 50900000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Capabilities: [b0] Vendor Specific Information: Len=00 <?>
Kernel driver in use: pciback
Kernel modules: xhci_pci
00:14.2 RAM memory [0500]: Intel Corporation Alder Lake-S PCH Shared SRAM [8086:7aa7] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0
Memory at 10afe00000 (64-bit, non-prefetchable) [size=16K]
Memory at 10afe04000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
00:14.3 Network controller [0280]: Intel Corporation Alder Lake-S PCH CNVi WiFi [8086:7af0] (rev 11)
Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:0094]
Flags: fast devsel, IRQ 23
Memory at 50910000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
Kernel driver in use: pciback
Kernel modules: iwlwifi
00:16.0 Communication controller [0780]: Intel Corporation Alder Lake-S PCH HECI Controller #1 [8086:7ae8] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 158
Memory at 5091a000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [a4] Vendor Specific Information: Len=14 <?>
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] [8086:7ae2] (rev 11) (prog-if 01 [AHCI 1.0])
DeviceName: SATA controller
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 151
Memory at 50918000 (32-bit, non-prefetchable) [size=8K]
Memory at 5091d000 (32-bit, non-prefetchable) [size=256]
I/O ports at 1060 [size=8]
I/O ports at 1068 [size=4]
I/O ports at 1040 [size=32]
Memory at 5091c000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Kernel driver in use: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Alder Lake-S PCH PCI Express Root Port #1 [8086:7ab8] (rev 11) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 147
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff [size=4K] [16-bit]
Memory behind bridge: 50a00000-50bfffff [size=2M] [32-bit]
Prefetchable memory behind bridge: 10afc00000-10afdfffff [size=2M] [32-bit]
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [90] Null
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Alder Lake-S PCH PCI Express Root Port #2 [8086:7ab9] (rev 11) (prog-if 00 [Normal decode])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 148
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: [disabled] [16-bit]
Memory behind bridge: 50700000-507fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [98] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Capabilities: [a0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [220] Access Control Services
Capabilities: [150] Precision Time Measurement
Capabilities: [a30] Secondary PCI Express
Capabilities: [a90] Data Link Feature <?>
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:7aba] (rev 11) (prog-if 00 [Normal decode])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 149
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: [disabled] [16-bit]
Memory behind bridge: 50400000-505fffff [size=2M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [40] Express Root Port (Slot-), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [98] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Capabilities: [a0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [220] Access Control Services
Capabilities: [150] Precision Time Measurement
Capabilities: [a30] Secondary PCI Express
Capabilities: [a90] Data Link Feature <?>
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Z690 Chipset LPC/eSPI Controller [8086:7a84] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0
00:1f.3 Audio device [0403]: Intel Corporation Alder Lake-S HD Audio Controller [8086:7ad0] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:9d25]
Flags: bus master, fast devsel, latency 64, IRQ 159
Memory at 50914000 (64-bit, non-prefetchable) [size=16K]
Memory at 50800000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 <?>
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake-S PCH SMBus Controller [8086:7aa3] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: medium devsel, IRQ 22
Memory at 5091e000 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-S PCH SPI Controller [8086:7aa4] (rev 11)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0
Memory at 5091b000 (32-bit, non-prefetchable) [size=4K]
01:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:5017] (rev 03) (prog-if 02 [NVM Express])
Subsystem: Kingston Technology Company, Inc. Device [2646:5017]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 50600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [158] Secondary PCI Express
Capabilities: [178] Physical Layer 16.0 GT/s <?>
Capabilities: [19c] Lane Margining at the Receiver <?>
Capabilities: [1b4] Latency Tolerance Reporting
Capabilities: [1bc] L1 PM Substates
Kernel driver in use: nvme
Kernel modules: nvme
03:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller [1106:3483] (rev 01) (prog-if 30 [XHCI])
Subsystem: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller [1106:3483]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at 50700000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable+ Count=1/4 Maskable- 64bit+
Capabilities: [c4] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: pciback
Kernel modules: xhci_pci
04:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d25]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at 50400000 (32-bit, non-prefetchable) [size=1M]
Memory at 50500000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 04-7c-16-ff-ff-6f-03-b6
Capabilities: [1c0] Latency Tolerance Reporting
Capabilities: [1f0] Precision Time Measurement
Capabilities: [1e0] L1 PM Substates
Kernel driver in use: pciback
Kernel modules: igc
I can reproduce the issue, and https://github.com/QubesOS/qubes-vmm-xen-stubdom-linux/pull/61 fixes it for me.
on the certified NitroPC Pro running Qubes-OS 4.2
@andrewdavidwong => affects-4.2?
Automated announcement from builder-github
The component vmm-xen-stubdom-linux (including package xen-hvm-stubdom-linux-1.2.6-1.fc32) has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
Changes included in this update
Automated announcement from builder-github
The package vmm-xen-stubdom-linux has been pushed to the r4.2 stable repository for the CentOS centos-stream8 template.
To install this update, please use the standard update command:
sudo yum update
Changes included in this update
Automated announcement from builder-github
The package vmm-xen-stubdom-linux has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Changes included in this update
Automated announcement from builder-github
The component vmm-xen-stubdom-linux (including package xen-hvm-stubdom-linux-1.2.6-1.fc32) has been pushed to the r4.1 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
Changes included in this update