Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Listing PCI devices breaks when there is some with non-0000 PCI domain #6932

Closed
MarioSDR93 opened this issue Oct 4, 2021 · 16 comments · Fixed by QubesOS/qubes-core-admin#560
Closed

Listing PCI devices breaks when there is some with non-0000 PCI domain #6932

MarioSDR93 opened this issue Oct 4, 2021 · 16 comments · Fixed by QubesOS/qubes-core-admin#560
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: core diagnosed Technical diagnosis has been performed (see issue comments). hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. r4.1-dom0-stable r4.2-host-stable
Milestone
Release 4.2

Comments

@MarioSDR93
Copy link

How to file a helpful issue

Qubes OS release

R4.1

Brief summary

All actions related to PCI devices fail with the following error in journalctl:

unhandled exception while calling src=b'dome' meth=b'admin.vm.device.pci. Available' dest=b'dome' arg-b' len (untrusted_payload)=0
Traceback (most recent call last):
	File "/usr/lib/python3.8/site-packages/qubes/api/__init__.py", line 287, in respond
		response = yield from self.mgmt.execute(
	File "/usr/lib64/python3.8/asyncio/coroutines.py", line 124, in coro
		res = func(*args, **kw)
	File "/usr/lib/python3.8/site-packages/qubes/api/admin.py", line 1242, in vm_device_available
		devices = self.dest.devices [devclass].available()
	File "/usr/lib/python3.8/site-packages/qubes/devices.py", line 380, in available
		devices = self._vm.fire_event ('device-list:' + self._bus)
	File "/usr/lib/python3.8/site-packages/qubes/events.py", line 197, in fire_event
		sync_effects, async_effects= self._fire_event (event, kwargs,
	File "/usr/lib/python3.8/site-packages/qubes/events.py", line 170, in fire_event
		effects.extend (effect)
	File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 191, in on_device_list_pci
		yield PCIDevice (vm, None, libvirt_name=libvirt_name)
	File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 140, in _init_
		assert dev_match
AssertionError

Steps to reproduce

Install Qubes 4.1 on Dell Latitude 5520
11th Gen Intel i7-1185G7

Error occurs on initial setup, when configuring sys-net/sys-usb

Expected behavior

PCI devices are usable. no errors occur

Actual behavior

PCI devices are not usable
Devices Tab in Qubes Manager is greyed out
sys-net does not start
qvm-devices pci does show nothing
@MarioSDR93 MarioSDR93 added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug labels Oct 4, 2021
@andrewdavidwong andrewdavidwong added C: other needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Oct 4, 2021
@andrewdavidwong andrewdavidwong added this to the Release 4.1 updates milestone Oct 4, 2021
@Shoko-Asahara
Copy link

Unfortunately I am also experiencing this same issue on:

Device: MSI GE66 RAIDER 11UH

 CPU - Intel® Core™ i9-11980HK
 CHIPSET - HM570 
 GRAPHICS - NVIDIA® GeForce RTX™ 3080 Laptop GPU 16GB GDDR6
 NOTE: Attempted installation was on an m.2 ssd connected via USB-C

Tried using 4.1 rc3 and 4.1 rc2 rc2

There is a related post on the qubes forum here. I believe it is just myself and the OP here on that post as well but it seems one thing we have in common is the 11th gen intel processor.

So when I do qvm-pci i get an error that says there is no permission to view pci devices, I can give a better more detailed explanation when I get on that device again but essentially the devices tab is greyed out in the settings for any vm. on the other hand, lspci and lsusb populate just fine.

The only thing I havent yet tried is putting the ssd in my computer and installing it without using a usb cord and enabling sys-usb during the installation. I will attempt to do so soon though and report back also.

Note:
Actually for me sys-net does start, and it has the ethernet card attached to it somehow and if i use an ethernet cable I can get internet but beyond that nothing. For example I tried attaching a usb wifi dongle which I couldnt get attached to sys-net due to there being no use of the qvm-pci command or the devices tab. I havent looked too far into xen's commands but I will do that also later today, any guidance would also be appreciated.

@RaspyVotan
Copy link

I have similar issues, adding just to help debugging this:

Qubes OS release

R4.1

Brief Summary:
PCI devices cannot be used adequately

My device:

Dell XPS 9510
Core i7-11800H
64 GB RAM
NVIDIO GeForce RTX 3050 TI

Steps to re-produce:
New install of Qubes OS on laptop
sys-net, sys-usb and sys-firewall created during setup process

Expected behaviour:

  • See all devices that are attached to the Thunderbolt Hub in sys-usb
  • Be able to attach PCI devices via the GUI under "VM Settings" - "Devices"
  • See all the PCI devices using "qvm-pci" without an error message

Actual behaviour:

  • Thunderbolt hub is not recognized
  • qvm-pci not usable - gives an error: "Failed to list PCI devices"
  • tab "device" is greyed out on the VM settings window

@xunillen
Copy link

Same issue after replacing my old thinkpad with 11th gen intel cpu laptop. Everything works, except qvm-pci command and Device tab which is greyed out in AppVM settings window (because of broken qvm-pci command).
Initial Qubes OS setup successfully assigns PCI devices to sys-* AppVMs, after that PCI devices are not attachable or detachable.

Device specs (Asus ExpertBook):

  • Intel i5-1135g7
  • 16GB of ram
  • Intel Iris Xe graphics

Result of qvm-pci while trying to attach pci device to AppVM

command - qvm-pci attach test-vm dom0:00_1f.3
test-vm - HVM model vm
dom0:00_1f.3 - Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)

result of command:
Traceback (most recent call last):
  File "/usr/bin/qvm-pci", line 5, in <module>
    sys.exit(main())
  File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_device.py", line 291, in main
    args = parser.parse_args(args, app=app)
  File "/usr/lib/python3.8/site-packages/qubesadmin/tools/__init__.py", line 409, in parse_args
    subaction.parse_qubes_app(self, namespace)
  File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_device.py", line 200, in parse_qubes_app
    dev = vm.devices[devclass][device_id]
  File "/usr/lib/python3.8/site-packages/qubesadmin/devices.py", line 282, in __getitem__
    for dev in self.available():
  File "/usr/lib/python3.8/site-packages/qubesadmin/devices.py", line 235, in available
    self._vm.qubesd_call(None,
  File "/usr/lib/python3.8/site-packages/qubesadmin/base.py", line 74, in qubesd_call
    return self.app.qubesd_call(dest, method, arg, payload,
  File "/usr/lib/python3.8/site-packages/qubesadmin/app.py", line 748, in qubesd_call
    return self._parse_qubesd_response(return_data)
  File "/usr/lib/python3.8/site-packages/qubesadmin/base.py", line 87, in _parse_qubesd_response
    raise qubesadmin.exc.QubesDaemonAccessError(
qubesadmin.exc.QubesDaemonAccessError: Got empty response from qubesd. See journalctl in dom0 for details.

Image of greyed out Device tab in AppVM settings window.
Device_error

@DemiMarie
Copy link

@xunillen Can you post the output of journalctl -b -u qubesd.service? Feel free to redact anything sensitive.

@xunillen
Copy link

Yes, of course. Hope it helps

Output of "journalctl -b -u qubesd.service":

-- Logs begin at Sun 2022-03-27 17:54:14 CEST, end at Wed 2022-03-30 09:15:00 CEST. --
Mar 30 08:39:41 dom0 systemd[1]: Starting Qubes OS daemon...
Mar 30 08:39:51 dom0 systemd[1]: Started Qubes OS daemon.
Mar 30 08:39:51 dom0 qubesd[2008]: vm.sys-net: Starting sys-net
Mar 30 08:39:52 dom0 qubesd[2008]: vm.sys-firewall: Starting sys-firewall
Mar 30 08:39:52 dom0 qubesd[2008]: vm.sys-usb: Starting sys-usb
Mar 30 08:39:52 dom0 qubesd[2008]: vm.sys-whonix: Starting sys-whonix
Mar 30 08:39:56 dom0 qubesd[2008]: vm.sys-net: Setting Qubes DB info for the VM
Mar 30 08:39:56 dom0 qubesd[2008]: vm.sys-net: Starting Qubes DB
Mar 30 08:39:56 dom0 runuser[4313]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:39:56 dom0 runuser[4313]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:39:56 dom0 qubesd[2008]: vm.sys-net: Activating the sys-net VM
Mar 30 08:39:56 dom0 runuser[4324]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:00 dom0 qubesd[2008]: vm.sys-usb: Setting Qubes DB info for the VM
Mar 30 08:40:00 dom0 qubesd[2008]: vm.sys-usb: Starting Qubes DB
Mar 30 08:40:00 dom0 runuser[5222]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:00 dom0 runuser[5222]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:00 dom0 qubesd[2008]: vm.sys-usb: Activating the sys-usb VM
Mar 30 08:40:00 dom0 runuser[5227]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:02 dom0 runuser[4324]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:05 dom0 qubesd[2008]: vm.sys-firewall: Setting Qubes DB info for the VM
Mar 30 08:40:05 dom0 qubesd[2008]: vm.sys-firewall: Starting Qubes DB
Mar 30 08:40:05 dom0 runuser[5756]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:05 dom0 runuser[5756]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:05 dom0 qubesd[2008]: vm.sys-firewall: Activating the sys-firewall VM
Mar 30 08:40:05 dom0 runuser[5760]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:09 dom0 runuser[5227]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:11 dom0 runuser[5760]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:14 dom0 qubesd[2008]: vm.sys-whonix: Setting Qubes DB info for the VM
Mar 30 08:40:14 dom0 qubesd[2008]: vm.sys-whonix: Starting Qubes DB
Mar 30 08:40:14 dom0 runuser[6408]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:14 dom0 runuser[6408]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:14 dom0 qubesd[2008]: vm.sys-whonix: Activating the sys-whonix VM
Mar 30 08:40:14 dom0 runuser[6412]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:18 dom0 runuser[6412]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:53 dom0 qubesd[2008]: vm.faks: Starting faks
Mar 30 08:40:56 dom0 qubesd[2008]: vm.faks: Setting Qubes DB info for the VM
Mar 30 08:40:56 dom0 qubesd[2008]: vm.faks: Starting Qubes DB
Mar 30 08:40:56 dom0 runuser[7430]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:40:56 dom0 runuser[7430]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:40:56 dom0 qubesd[2008]: vm.faks: Activating the faks VM
Mar 30 08:40:56 dom0 runuser[7434]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:41:01 dom0 runuser[7434]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:55:02 dom0 qubesd[2008]: vm.untrusted: Starting untrusted
Mar 30 08:55:06 dom0 qubesd[2008]: vm.untrusted: Setting Qubes DB info for the VM
Mar 30 08:55:06 dom0 qubesd[2008]: vm.untrusted: Starting Qubes DB
Mar 30 08:55:06 dom0 runuser[8361]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:55:06 dom0 runuser[8361]: pam_unix(runuser:session): session closed for user xuni
Mar 30 08:55:06 dom0 qubesd[2008]: vm.untrusted: Activating the untrusted VM
Mar 30 08:55:06 dom0 runuser[8365]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 08:55:10 dom0 runuser[8365]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:06:57 dom0 qubesd[2008]: vm.vault: Starting vault
Mar 30 09:07:00 dom0 qubesd[2008]: vm.vault: Setting Qubes DB info for the VM
Mar 30 09:07:00 dom0 qubesd[2008]: vm.vault: Starting Qubes DB
Mar 30 09:07:00 dom0 runuser[9794]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:07:00 dom0 runuser[9794]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:07:00 dom0 qubesd[2008]: vm.vault: Activating the vault VM
Mar 30 09:07:00 dom0 runuser[9798]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:07:04 dom0 runuser[9798]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:11:45 dom0 qubesd[2008]: vm.windows10: Starting windows10
Mar 30 09:11:52 dom0 qubesd[2008]: vm.windows10: Setting Qubes DB info for the VM
Mar 30 09:11:52 dom0 qubesd[2008]: vm.windows10: Starting Qubes DB
Mar 30 09:11:52 dom0 runuser[11279]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:11:52 dom0 runuser[11279]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:11:52 dom0 qubesd[2008]: vm.windows10: Activating the windows10 VM
Mar 30 09:11:52 dom0 runuser[11287]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:11:52 dom0 runuser[11287]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:11:52 dom0 runuser[11295]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:12:10 dom0 runuser[11295]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:13:24 dom0 qubesd[2008]: unhandled exception while calling src=b'dom0' meth=b'admin.vm.device.pci.Available' dest=b'dom0' arg=b'' len(untrusted_payload)=0    -> Error while running just 'qvm-pci' command without any parameters
Mar 30 09:13:24 dom0 qubesd[2008]: Traceback (most recent call last):
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/api/__init__.py", line 286, in respond
Mar 30 09:13:24 dom0 qubesd[2008]:     response = await self.mgmt.execute(
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/api/admin.py", line 1217, in vm_device_available
Mar 30 09:13:24 dom0 qubesd[2008]:     devices = self.dest.devices[devclass].available()
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/devices.py", line 376, in available
Mar 30 09:13:24 dom0 qubesd[2008]:     devices = self._vm.fire_event('device-list:' + self._bus)
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/events.py", line 195, in fire_event
Mar 30 09:13:24 dom0 qubesd[2008]:     sync_effects, async_effects = self._fire_event(event, kwargs,
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/events.py", line 168, in _fire_event
Mar 30 09:13:24 dom0 qubesd[2008]:     effects.extend(effect)
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 191, in on_device_list_pci
Mar 30 09:13:24 dom0 qubesd[2008]:     yield PCIDevice(vm, None, libvirt_name=libvirt_name)
Mar 30 09:13:24 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 140, in __init__
Mar 30 09:13:24 dom0 qubesd[2008]:     assert dev_match
Mar 30 09:13:24 dom0 qubesd[2008]: AssertionError
Mar 30 09:14:10 dom0 qubesd[2008]: vm.work: Starting work
Mar 30 09:14:14 dom0 qubesd[2008]: vm.work: Setting Qubes DB info for the VM
Mar 30 09:14:14 dom0 qubesd[2008]: vm.work: Starting Qubes DB
Mar 30 09:14:14 dom0 runuser[12708]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:14:14 dom0 runuser[12708]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:14:14 dom0 qubesd[2008]: vm.work: Activating the work VM
Mar 30 09:14:14 dom0 runuser[12712]: pam_unix(runuser:session): session opened for user xuni by (uid=0)
Mar 30 09:14:18 dom0 runuser[12712]: pam_unix(runuser:session): session closed for user xuni
Mar 30 09:15:00 dom0 qubesd[2008]: unhandled exception while calling src=b'dom0' meth=b'admin.vm.device.pci.Available' dest=b'dom0' arg=b'' len(untrusted_payload)=0    -> Error while running 'qvm-pci attach test-vm dom0:00_1f.3'. Command with test AppVM with test PCI device.
Mar 30 09:15:00 dom0 qubesd[2008]: Traceback (most recent call last):
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/api/__init__.py", line 286, in respond
Mar 30 09:15:00 dom0 qubesd[2008]:     response = await self.mgmt.execute(
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/api/admin.py", line 1217, in vm_device_available
Mar 30 09:15:00 dom0 qubesd[2008]:     devices = self.dest.devices[devclass].available()
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/devices.py", line 376, in available
Mar 30 09:15:00 dom0 qubesd[2008]:     devices = self._vm.fire_event('device-list:' + self._bus)
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/events.py", line 195, in fire_event
Mar 30 09:15:00 dom0 qubesd[2008]:     sync_effects, async_effects = self._fire_event(event, kwargs,
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/events.py", line 168, in _fire_event
Mar 30 09:15:00 dom0 qubesd[2008]:     effects.extend(effect)
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 191, in on_device_list_pci
Mar 30 09:15:00 dom0 qubesd[2008]:     yield PCIDevice(vm, None, libvirt_name=libvirt_name)
Mar 30 09:15:00 dom0 qubesd[2008]:   File "/usr/lib/python3.8/site-packages/qubes/ext/pci.py", line 140, in __init__
Mar 30 09:15:00 dom0 qubesd[2008]:     assert dev_match
Mar 30 09:15:00 dom0 qubesd[2008]: AssertionError

@marmarek
Copy link
Member

Can you show output of virsh -c xen nodedev-list?

@xunillen
Copy link

Here you go.

output of virsh -c xen nodedev-list:

computer
drm_card0
drm_renderD128
net_lo_00_00_00_00_00_00
pci_0000_00_00_0
pci_0000_00_02_0
pci_0000_00_04_0
pci_0000_00_06_0
pci_0000_00_08_0
pci_0000_00_0a_0
pci_0000_00_0d_0
pci_0000_00_0e_0
pci_0000_00_14_0
pci_0000_00_14_2
pci_0000_00_14_3
pci_0000_00_15_0
pci_0000_00_15_1
pci_0000_00_16_0
pci_0000_00_17_0
pci_0000_00_1f_0
pci_0000_00_1f_3
pci_0000_00_1f_4
pci_0000_00_1f_5
pci_10000_e0_06_0
pci_10000_e0_17_0
pci_10000_e1_00_0
scsi_host0

@DemiMarie
Copy link

Thanks! Obviously pci_10000_e0_06_0 does not match qubesd’s regex and will trip that assertion. It almost looks like your system has more than one PCIe root complex or something else strange. What happens if you unplug the Thunderbolt cable?

@xunillen
Copy link

xunillen commented Mar 30, 2022 •
edited
Loading

Here's the problem, nothing is connected to the ThunderBolt port. And i forgot to say, this laptop has Intel Volume Management Device (VMD) technology enabled. Can that cause such issues?

Here is the output of lspci command, if it helps in any way:

0000:00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
0000:00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 01)
0000:00:06.0 System peripheral: Intel Corporation Device 09ab
0000:00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
0000:00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
0000:00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
0000:00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
0000:00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
0000:00:17.0 System peripheral: Intel Corporation Device 09ab
0000:00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
10000:e0:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)
10000:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
10000:e1:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)

@DemiMarie
Copy link

Intel Volume Management Device (VMD) technology enabled. Can that cause such issues?

That is probably the culprit, but I have no idea how dom0 should handle it.

Here is the output of lspci command, if it helps in any way:

It does, and is about what I would expect for VMD given what I have just seen on Intel’s website.

@brendanhoar
Copy link

Perhaps Intel Volume Management Device can be disabled in bios?

B

@RaspyVotan
Copy link

RaspyVotan commented Mar 31, 2022 via email

@DemiMarie
Copy link

@marmarek @HW42: is it safe to just loosen the assertion?

@xunillen
Copy link

xunillen commented Apr 1, 2022 •
edited
Loading

I can confirm what RaspyVotan said. I just disabled VMD in BIOS and everything is working fine now. qvm-pci command works, and 'Device' tab is not greyed out anymore.

@andrewdavidwong andrewdavidwong added diagnosed Technical diagnosis has been performed (see issue comments). and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Apr 2, 2022
@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 updates milestone Aug 13, 2023
@marmarta marmarta moved this to Devices: misc in Device UX Redesign Sep 19, 2023
@marmarta marmarta moved this from Devices: misc to PCI pain in Device UX Redesign Sep 19, 2023
@marmarek marmarek added the affects-4.2 This issue affects Qubes OS 4.2. label Sep 27, 2023
@marmarek marmarek mentioned this issue Sep 27, 2023
Closed
@marmarek marmarek changed the title R4.1 PCI devices not working Listing PCI devices breaks when there is some with non-0000 PCI domain Sep 27, 2023
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 10, 2023
@marmarek
tests: check device on 1000 PCI domain
49a9f7e 
QubesOS/qubes-issues#6932
@marmarek marmarek mentioned this issue Oct 10, 2023
Merged
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 10, 2023
@marmarek
tests: check device on 1000 PCI domain
b249cc2 
QubesOS/qubes-issues#6932
@github-project-automation github-project-automation bot moved this from PCI pain to Done in Device UX Redesign Oct 11, 2023
@qubesos-bot qubesos-bot mentioned this issue Oct 12, 2023
Closed
@andrewdavidwong andrewdavidwong added C: core pr submitted A pull request has been submitted for this issue. and removed C: other labels Oct 12, 2023
@andrewdavidwong andrewdavidwong added this to the Release 4.2 milestone Oct 12, 2023
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Jan 20, 2024
@marmarek
Ignore PCI devices on non-0000 domain instead of crashing
47f0314 
This is a quick band-aid to unbreak Qubes on systems having such device.
Later change should implement handling them properly instead of
ignoring.

Fixes QubesOS/qubes-issues#6932

(cherry picked from commit 3384d98)
@qubesos-bot
Copy link

Automated announcement from builder-github

The component core-admin (including package qubes-core-dom0-4.1.35-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

@qubesos-bot qubesos-bot mentioned this issue Jan 20, 2024
Closed
@qubesos-bot qubesos-bot mentioned this issue Jan 31, 2024
Closed
@qubesos-bot
Copy link

Automated announcement from builder-github

The component core-admin (including package qubes-core-dom0-4.1.36-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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: core diagnosed Technical diagnosis has been performed (see issue comments). hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. r4.1-dom0-stable r4.2-host-stable
Projects
Device UX Redesign
Status: Done
Milestone
Release 4.2
Development

Successfully merging a pull request may close this issue.

Ignore PCI devices on non-0000 domain instead of crashing marmarek/qubes-core-admin
9 participants
@marmarek @MarioSDR93 @DemiMarie @brendanhoar @andrewdavidwong @RaspyVotan @qubesos-bot @Shoko-Asahara @xunillen