This thread shows where I started:
https://groups.google.com/forum/#!topic/qubes-users/5IurMRKaViU
Original issue related to inability to start sys-net with PCI USB controllers
attached.
Hardware info:
Dell Latitude E6420 - i5 that previously worked using R3.2
VT-x and VT-d are properly enabled
BRCM WiFi is disabled in BIOS
Attempting to attach both PCI USB controllers to sys-net using instructions
provided in the other thread yields partial results.
qvm-pci a sys-net -o no-strict-reset=true --persistent dom0:00_1a.0
completes without error, but
qvm-pci a sys-net -o no-strict-reset=true --persistent dom0:00_1d.0
returns "Got empty response from qubesd. See journalctl in dom0 for details."
The pertinent lines in journalctl are as follows:
-- Logs begin at Tue 2017-10-24 16:59:49 MST, end at Wed 2017-10-25 09:17:44
MST. --
Oct 25 09:17:44 dom0 libvirtd[1468]: 2017-10-25 16:17:44.129+0000: 1495: error
: libxlDomainAttachHostPCIDevice:3250 : internal error: libxenlight failed to
attach pci device 0000:00:1d.0
Oct 25 09:17:44 dom0 qubesd[1419]: unhandled exception while calling
src=b'dom0' meth=b'admin.vm.device.pci.Attach' dest=b'sys-net'
arg=b'dom0+00_1d.0' len(untrusted_payload)=36
Oct 25 09:17:44 dom0 qubesd[1419]: Traceback (most recent call last):
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/api/__init__.py", line 262, in respond
Oct 25 09:17:44 dom0 qubesd[1419]: untrusted_payload=untrusted_payload)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib64/python3.5/asyncio/futures.py", line 381, in __iter__
Oct 25 09:17:44 dom0 qubesd[1419]: yield self # This tells Task to wait
for completion.
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib64/python3.5/asyncio/tasks.py", line 310, in _wakeup
Oct 25 09:17:44 dom0 qubesd[1419]: future.result()
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib64/python3.5/asyncio/futures.py", line 294, in result
Oct 25 09:17:44 dom0 qubesd[1419]: raise self._exception
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
Oct 25 09:17:44 dom0 qubesd[1419]: result = coro.send(None)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 1109, in
vm_device_attach
Oct 25 09:17:44 dom0 qubesd[1419]: yield from
self.dest.devices[devclass].attach(assignment)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/devices.py", line 255, in attach
Oct 25 09:17:44 dom0 qubesd[1419]: device=device,
options=device_assignment.options)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/events.py", line 229, in
fire_event_async
Oct 25 09:17:44 dom0 qubesd[1419]: kwargs, pre_event=pre_event)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/events.py", line 164, in _fire_event
Oct 25 09:17:44 dom0 qubesd[1419]: effect = func(self, event, **kwargs)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/ext/pci.py", line 235, in
on_device_pre_attached_pci
Oct 25 09:17:44 dom0 qubesd[1419]: device=device, vm=vm, options=options))
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib/python3.5/site-packages/qubes/app.py", line 94, in wrapper
Oct 25 09:17:44 dom0 qubesd[1419]: return attr(*args, **kwargs)
Oct 25 09:17:44 dom0 qubesd[1419]: File
"/usr/lib64/python3.5/site-packages/libvirt.py", line 563, in attachDevice
Oct 25 09:17:44 dom0 qubesd[1419]: if ret == -1: raise libvirtError
('virDomainAttachDevice() failed', dom=self)
Oct 25 09:17:44 dom0 qubesd[1419]: libvirt.libvirtError: internal error:
libxenlight failed to attach pci device 0000:00:1d.0
Here's the output of qmv-pci ls:
dom0:00_00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller
dom0:00_01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core
Processor Family PCI Express Root Port
dom0:00_16.0 Communication controller: Intel Corporation 6 Series/C200 Series
Chipset Family MEI Controller #1
dom0:00_19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (Lewisville) sys-net
dom0:00_1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 sys-net (no-strict-reset=true)
dom0:00_1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller
dom0:00_1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 1
dom0:00_1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 3
dom0:00_1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 4
dom0:00_1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 6
dom0:00_1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1
dom0:00_1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC
Controller
dom0:00_1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA
Controller [RAID mode]
dom0:00_1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller
dom0:01_00.0 VGA compatible controller: NVIDIA Corporation GF119M [NVS 4200M]
dom0:01_00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller
dom0:0a_00.0 SD Host controller: O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS
SD/MMC Card Reader Controller
dom0:0a_00.1 Mass storage controller: O2 Micro, Inc.
You can see that I have successfully attached the device at 00_1a.0 to sys-net
using the no-strict-reset option.
I don't know where to go from here.
Thanks in advance for assistance.
Sonny Horton
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/80818075-3982-4f56-8529-78da9fa80720%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
