Win7 as USB-VM: "No PCI-Reset available" libvirt-Problem

[game...@googlemail.com]

Hi,
for comfortable use of USB-only scanners and other devices such as this, it would be nice to have Win7 as USB-VM, e.g. have the USB-Controller-PCI-Device assigned to it to use USB-Devices from there.

When i try to start Win7, this happens (see the picture https://imgur.com/a/spnRC).
[The german sentence in the picure is like:
"libvirt.libvirtError: Internal Bug/Fail: PCI-Device can't be reseted. No FLR, PM or Bus Reset available."]
I already have the PCI-Device assigned to it, original Qubes-USB-VM dont have it assigned anymore.
the "strict pcireset"-qvm-prefs option is already turned on. Any suggestions to fix this?
Thank you.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

To work around this issue, pci_strictreset should be turned *off*, not on. (I.e., it should be set to "false," not "true.")

See: https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYQrFkAAoJENtN07w5UDAwW3YP/0kGZ3ikcLxOFFlET1Uv/jJn
ZFmMKqrcr8cKJGdfiW+luqE1gwrZLnULO7lDH8fXbEpmHEDP/aUM1NzTGv/mxDAe
efSGyoZR5tifgkxCwZAFdrkbQykJ3GI5mFiKSplGsUXd7PewWl+oiVmFOPcea0bl
PMPXV3sjEvUJwMgnx8OTxa6dfPS/IoEmK0fkjHCT3+PqMVk4Rik0/r/ykfqGjWut
LK98QpPX8r0oXYQ+Wv3ZB/IJXlSsqinz3SDWPIGKyiK6/xzl5sZtxfoEn84K0re2
L7FejYds8fXJFnfpPvCsT7wAv1mbfBuVGWHhr6ICR07MW6G96I1qH9Bd+eDRVJFs
Jl2YX8b6a5S+1s42+bstoemBj8p0dYNOey6/JNyZhiLChXSmbme2tDP/BoxkZwyT
12I90c/hzGUyKs4XszmAQtbrBIAOmf6KkYaNEcjk4yfjfy5X8eBHpCcuhxdEFHYU
nUQuOLm6pn2zNBPQ9UJUpU+fX0HSFI/3WHbkvDYzzdhjbMMnJgonoMb8XGhQHxHS
77AJv3Mj7dPCq07HDCoaDX5jQ8jwIzt+IuQCZ0WMuhbVpXVQ/s2UUeQqDPMqngOK
tgUCoEWv0X+5K6gQ/WQhlBURj7NqkFyjQ05xThAHW3muGfH+ii9aE9SRh9riLXca
b7e1PsooMVzh4RQOM7f5
=iT2i
-----END PGP SIGNATURE-----

[Grzesiek Chodzicki]

set pci_strictreset to false and try again.

[game...@googlemail.com]

Wow...yeah, thank you. That was a pointless fail by me.

Anyway: Now, i have the problem that connected usb-devices dont show in windows7. At first boot after pci-passthough-change, win7 showed that it couldnt find any driver for the "new" usb-controller. I tried to fix it with Xen PV Bus-Driver, but it didnt work.

[Grzesiek Chodzicki]

Check if You have VT-d enabled in BIOS/UEFI

[game...@googlemail.com]

Yes, it is.
But i installed Qubes with vt-d disabled und reenabled it like it is mentioned here: https://www.qubes-os.org/doc/thinkpad-troubleshooting/

[Grzesiek Chodzicki]

Can you paste the output of xl dmesg | grep -i vt-d ?

[game...@googlemail.com]

xl dmesg:
Xen 4.6.3-24.fc23
(XEN) Xen version 4.6.3 (user@) (gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6)) debug=n Wed Nov 23 00:15:57 UTC 2016
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta2
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009d000 (usable)
(XEN) 000000000009d000 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000099bb9000 (usable)
(XEN) 0000000099bb9000 - 00000000aca89000 (reserved)
(XEN) 00000000aca89000 - 00000000aca8a000 (ACPI NVS)
(XEN) 00000000aca8a000 - 00000000b7f7f000 (reserved)
(XEN) 00000000b7f7f000 - 00000000b7fcf000 (ACPI NVS)
(XEN) 00000000b7fcf000 - 00000000b7fff000 (ACPI data)
(XEN) 00000000b7fff000 - 00000000b8100000 (reserved)
(XEN) 00000000b8600000 - 00000000bc800000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fd000000 - 00000000fe800000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed00000 - 00000000fed01000 (reserved)
(XEN) 00000000fed10000 - 00000000fed1a000 (reserved)
(XEN) 00000000fed84000 - 00000000fed85000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff800000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000242800000 (usable)
(XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO)
(XEN) ACPI: XSDT B7FD0188, 00D4 (r1 LENOVO TP-N1C 0 PTEC 2)
(XEN) ACPI: FACP B7FF4000, 00F4 (r5 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: DSDT B7FDD000, 12331 (r2 LENOVO TP-N1C 1150 INTL 20141107)
(XEN) ACPI: FACS B7FAA000, 0040
(XEN) ACPI: TCPA B7FFC000, 0032 (r2 LENOVO TP-N1C 2 PTEC 2)
(XEN) ACPI: SSDT B7FFB000, 03A2 (r2 LENOVO TcgTable 1000 INTL 20141107)
(XEN) ACPI: UEFI B7FC1000, 0042 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: SSDT B7FF6000, 4E0A (r2 LENOVO SaSsdt 3000 INTL 20141107)
(XEN) ACPI: SSDT B7FF5000, 05C5 (r2 LENOVO PerfTune 1000 INTL 20141107)
(XEN) ACPI: ECDT B7FF3000, 0052 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: HPET B7FF2000, 0038 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: APIC B7FF1000, 00BC (r3 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: MCFG B7FF0000, 003C (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: SSDT B7FDB000, 18D2 (r1 LENOVO SataAhci 1000 INTL 20141107)
(XEN) ACPI: DBGP B7FDA000, 0034 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: DBG2 B7FD9000, 0054 (r0 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: BOOT B7FD8000, 0028 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: BATB B7FD7000, 0046 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: SSDT B7FD6000, 0E73 (r2 LENOVO CpuSsdt 3000 INTL 20141107)
(XEN) ACPI: SSDT B7FD5000, 0403 (r2 LENOVO CtdpB 1000 INTL 20141107)
(XEN) ACPI: POAT B7FD4000, 0055 (r3 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: DMAR B7FD3000, 00A8 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: ASF! B7FD2000, 00A5 (r32 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: FPDT B7FD1000, 0044 (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) ACPI: UEFI B7FA8000, 013E (r1 LENOVO TP-N1C 1150 PTEC 2)
(XEN) System RAM: 7619MB (7802200kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - b7faa000/0000000000000000, using 32
(XEN) Processor #0 6:14 APIC version 21
(XEN) Processor #2 6:14 APIC version 21
(XEN) Processor #1 6:14 APIC version 21
(XEN) Processor #3 6:14 APIC version 21
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Not enabling x2APIC (upon firmware request)
(XEN) xstate_init: using cntxt_size: 0x440 and states: 0x1f
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2408.707 MHz processor.
(XEN) Initing memory sharing.
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) Platform timer is 23.999MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - VM Functions
(XEN) - Virtualisation Exceptions
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 4 CPUs
(XEN) Dom0 has maximum 696 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2055000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000234000000->0000000238000000 (1027061 pages to be allocated)
(XEN) Init. ramdisk: 00000002413f5000->00000002427ff938
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff82055000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff82055000->ffffffff820554b4
(XEN) Page tables: ffffffff82056000->ffffffff8206b000
(XEN) Boot stack: ffffffff8206b000->ffffffff8206c000
(XEN) TOTAL: ffffffff80000000->ffffffff82400000
(XEN) ENTRY ADDRESS: ffffffff81d521f0
(XEN) Dom0 has maximum 4 VCPUs
(XEN) [VT-D]BIOS did not enable IGD for VT properly. Disabling IGD VT-d engine.
(XEN) Scrubbing Free RAM on 1 nodes using 2 CPUs
(XEN) .....................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 308kB init memory.
(XEN) No CPU ID for APIC ID 0x5

grep -i vt-d: brought up nothing after 10 minutes while being still in progress

[a user]

Basically it would be interesting to know if the problem is based on the fact that some vt-d features are obviously not enabled(?) and how to enable them if it is the problem.