From 1a421c412b117c1a1b1aeacd77700d25b00f5f66 Mon Sep 17 00:00:00 2001
From: Enjeck Cleopatra <32180937+PROTechThor@users.noreply.github.com>
Date: Thu, 15 Oct 2020 08:44:39 +0100
Subject: [PATCH] Add new section about PCI devices

---
 user/troubleshooting/resume-suspend-troubleshooting.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/user/troubleshooting/resume-suspend-troubleshooting.md b/user/troubleshooting/resume-suspend-troubleshooting.md
index fec66d85..5acacc81 100644
--- a/user/troubleshooting/resume-suspend-troubleshooting.md
+++ b/user/troubleshooting/resume-suspend-troubleshooting.md
@@ -123,3 +123,12 @@ iwlwifi
 This problem is related to the software method used to disable sibling threads and how it interacts with suspend/resume. 
 To solve the problem, disable hyper-threading in the BIOS. This [external guide](https://www.pcmag.com/news/how-to-disable-hyperthreading) explains how to disable hyper-threading. 
 Since Qubes does disable hyperthreading by default (by not using secondary threads), you won't pay any performance cost.
+
+## Attached devices in HVM stop working on suspend/resume ##
+
+After the whole system gets suspended into S3 sleep and subsequently resumed, some attached devices may stop working. To make the devices work, they should be restarted within the VM.
+This can be achieved under a Windows HVM by opening the Device Manager, selecting the actual device (such as a USB controller), 'Disabling' the device, and then 'Enabling' the device again.
+This is illustrated on the screenshot below:
+
+![r2b1-win7-usb-disable.png](/attachment/wiki/HvmCreate/r2b1-win7-usb-disable.png)
+