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 upMore informative error message for `qvm-pci a` on halted VMs #3195
Comments
3hhh
changed the title from
qvm-pci a doesn't work
to
qvm-pci a doesn't work for stopped VMs
Oct 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
You need |
marmarek
closed this
Oct 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
3hhh
commented
Oct 19, 2017
|
Ok, my bad then, sorry. The error was quite misleading though... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Oct 19, 2017
Member
Reopening as a UX issue for the error message, if it's OK with @marmarek.
|
Reopening as a UX issue for the error message, if it's OK with @marmarek. |
andrewdavidwong
reopened this
Oct 19, 2017
andrewdavidwong
changed the title from
qvm-pci a doesn't work for stopped VMs
to
More informative error message for `qvm-pci a` on halted VMs
Oct 19, 2017
andrewdavidwong
added
bug
C: core
UX
P: minor
labels
Oct 19, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 20, 2017
Member
What about "VM not running, can only attach device with persistent flag"?
|
What about "VM not running, can only attach device with persistent flag"? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Sounds good to me. |
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Oct 20, 2017
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Oct 21, 2017
marmarek
closed this
in
marmarek/qubes-core-admin@4334308
Oct 21, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 21, 2017
Automated announcement from builder-github
The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubesos-bot
commented
Oct 21, 2017
|
Automated announcement from builder-github The package |
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Oct 21, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Oct 21, 2017
Closed
core-admin v4.0.11 (r4.0) #284
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 30, 2017
Automated announcement from builder-github
The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
qubesos-bot
commented
Oct 30, 2017
|
Automated announcement from builder-github The package Or update dom0 via Qubes Manager. |
3hhh commentedOct 19, 2017
•
edited
Edited 1 time
-
3hhh
edited Oct 19, 2017 (most recent)
Qubes OS version:
4.0rc1, current testing repo updates
Steps to reproduce the behavior:
Shutdown [AppVM]
Expected behavior:
[device] is permanently attached to [AppVM]
Actual behavior:
Output of
Devices can only be attached non-persistent to a running vmand no action.General notes:
Starting the VM and then attaching it tends to work, but only for the runtime of the VM.
Was tested with an AppVM and a DispVM, both were affected.
Using qubes-vm-settings to attach a device works (even though that tends to segfault on exit quite often).