Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-block / qvm-device broken in 4.0 -- no frontend-dev options like doc says #4119
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
In 4.0, it's |
andrewdavidwong
added
C: doc
task
labels
Jul 22, 2018
andrewdavidwong
added this to the Ongoing milestone
Jul 22, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@t4777sd, care to help us update the documentation? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
t4777sd commentedJul 21, 2018
Qubes OS version:
4.0
Affected component(s):
qvm-block / qvm-device
Steps to reproduce the behavior:
Run any of the various commands that should be valid and you will see an error:
qvm-block attach --ro --frontend=xtest test-vm dom0:loop1
qvm-device block attach --ro --frontend-dev=xtest test-vm dom0:loop1
For qvm-block you can see the documentation lists valid options: https://www.qubes-os.org/doc/tools/3.2/dom0/qvm-block/
The "frontend" command is not being recognized in 4.0. There is no correspodning documentation for 4.0, so 3.2 documentation is the only available documentation for the 4.0 commands that I could find.
Regarding qvm-device, the latest documentation is here: https://dev.qubes-os.org/projects/core-admin-client/en/latest/manpages/qvm-device.html
frontend-dev is listed as an option, but when it is utilized it fails complaining of unrecognized option
Expected behavior:
Commands succeed and frontend dev is set accordingly. Or the documentation is updated with the proper way to set the frontend dev
Actual behavior:
Command fails complaining of unrecognized arguments