Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-06-06 22:19:09 -04:00
Code Issues Projects Releases Packages Wiki Activity

Add space

Browse source
This commit is contained in:
Enjeck Cleopatra 2020-10-30 07:34:01 +01:00 • committed by GitHub
parent 7f8266858e
commit d695bef4a1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
user/common-tasks/block-devices.md
View file

@ -123,7 +123,7 @@ To recover from this error state, in dom0 run
However, if the block device originated in dom0, you will have to refer to the next section. However, if the block device originated in dom0, you will have to refer to the next section.
### What if I removed the device before detaching it from the VM?### ### What if I removed the device before detaching it from the VM? ###
Currently (until issue [1082] gets implemented), if you remove the device before detaching it from the qube, Qubes OS (more precisely, `libvirtd`) will think that the device is still attached to the qube and will not allow attaching further devices under the same name. Currently (until issue [1082] gets implemented), if you remove the device before detaching it from the qube, Qubes OS (more precisely, `libvirtd`) will think that the device is still attached to the qube and will not allow attaching further devices under the same name.
The easiest way to recover from such a situation is to reboot the qube to which the device was attached. The easiest way to recover from such a situation is to reboot the qube to which the device was attached.