Got around to checking and this issue has been open for over
a year: https://github.com/QubesOS/qubes-issues/issues/3437
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
Yes qvm-block does not accept any symlink, (mapper/...,
disk/by-uuid/... or -L , -U flags like mount) so will open
the issue and there is a *possible* related issue that a non
existent device fail of qube start may happen if the device
is not up yet, since they obviously happen in parallel.
Can't
On Tuesday, January 22, 2019 at 2:26:16 PM UTC-5, Eric wrote:
> qvm-block does not accept a UUID (not documented
> and gives an error: not exposed) I suspect that
> should be added as an issue.
[Out of curiosity, I ask, since I am away from the Qubes systems at the moment:]
By "qvm-block does
