Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix code block syntax

Browse Source
This commit is contained in:
Andrew David Wong 2021-04-15 09:07:15 -07:00
parent ec2af6a488
commit 7060c4a6fa
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
user/troubleshooting/usb-troubleshooting.md
View File

@ -55,30 +55,30 @@ Errors suggesting this issue:
- in `xl dmesg` output:
```
(XEN) [VT-D] It's disallowed to assign 0000:00:1a.0 with shared RMRR at dbe9a000 for Dom19.
(XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom19 failed (-1)
```
```
(XEN) [VT-D] It's disallowed to assign 0000:00:1a.0 with shared RMRR at dbe9a000 for Dom19.
(XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom19 failed (-1)
```
- during `qvm-start sys-usb`:
```
internal error: Unable to reset PCI device [...] no FLR, PM reset or bus reset available.
```
```
internal error: Unable to reset PCI device [...] no FLR, PM reset or bus reset available.
```
Another solution would be to set the pci_strictreset option in dom0:
- In Qubes R4.x, when attaching the PCI device to the VM (where `<BDF>` can be obtained from running `qvm-pci`):
```
qvm-pci attach --persistent --option no-strict-reset=true usbVM dom0:<BDF>
```
```
qvm-pci attach --persistent --option no-strict-reset=true usbVM dom0:<BDF>
```
- In Qubes R3.x, by modifying the VM's properties:
```
qvm-prefs usbVM -s pci_strictreset false
```
```
qvm-prefs usbVM -s pci_strictreset false
```
These options allow the VM to ignore the error and the VM will start.
Please review the notes in the `qvm-prefs` man page and [here](/doc/device-handling/) and be aware of the potential risks.