-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qvm-block allows attaching the same device to multiple qubes #4692
Comments
Seems this has become a duplicate of #6396 which also discusses whether to allow attaching the same device readonly. |
My setup is similiar, with persistence:
and it is intended, so this should be possible and not blocked.
See also discussion @ #6396 |
At a minimum, it should be possible to attach the same device read-only to as many qubes as one wishes. There is no risk of corruption there! |
Is this still a problem in 4.1? |
yes |
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
To properly report attachments or detachments of block devices, the logic has been moved to the extension. As a bonus, the following issue is fix: QubesOS/qubes-issues#4692
Qubes OS version:
R4.0
Steps to reproduce the behavior:
Expected behavior:
The second command fails as the device is already attached to
vm1
.Actual behavior:
Both commands succeed, and device is available in both VMs, possibly leading to data corruption at least, security issues at worst.
Related issues:
Similar issue for R2.0: #950
The text was updated successfully, but these errors were encountered: