From 6d4d94524383be4d2ae44920a34824b2049238e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Wed, 28 Sep 2016 13:06:24 +0200 Subject: [PATCH] fix formatting --- basics_user/user-faq.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/basics_user/user-faq.md b/basics_user/user-faq.md index 11b2827f..b6f5c822 100644 --- a/basics_user/user-faq.md +++ b/basics_user/user-faq.md @@ -254,16 +254,15 @@ Most likely the offending controller is a USB3.0 device. You can remove this con Alternatively you may be able to disable USB 3.0 in the BIOS. 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 using qvm-prefs in dom0: