From e5cc989e1e6b0dd80a6180bb0ff49e4871ec8291 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Wed, 28 Sep 2016 10:19:12 +0200 Subject: [PATCH] Add error messages to `pci_strictreset` description --- basics_user/user-faq.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/basics_user/user-faq.md b/basics_user/user-faq.md index 457b24d9..11b2827f 100644 --- a/basics_user/user-faq.md +++ b/basics_user/user-faq.md @@ -253,6 +253,19 @@ A device that does not support reset is not safe and generally should not be ass Most likely the offending controller is a USB3.0 device. You can remove this controller from the usbVM, and see if this allows the VM to boot. 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) +``` + - during `qvm-start sys-usb`: + +``` +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: `qvm-prefs usbVM -s pci_strictreset false`