qvm-block by UUID?

[johny...@sigaint.org]

Most standard Linux utilities that refer to block devices, allow you to
specify by uuid as well (mount, cryptsetup are two examples).

The documentation for qvm-block is sparse, but probably because it's a
striaght-forward utility.

There's no support in qvm-block to assign a device to a VM by UUID, is there?

Could be handy for some of the automation I'd like to put in place on
firing up the system.

One can always lsblk|grep|sed|cut|whatever in a sh script, and then use
the resulting block device for qvm-block, but it'd be a lot cleaner and
less error-prone if one could say

"qvm-block -a Florp UUID=kasdjflaksjdfaklsdf"
or "qvm-block -a FLorp --uid asdfkasjdlfkajsd"

Just a suggestion. (And for any other qvm-* that refer to block devices,
perhaps.)

Cheers.

JJ

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-25 18:06, johny...@sigaint.org wrote:
> Most standard Linux utilities that refer to block devices, allow you to
> specify by uuid as well (mount, cryptsetup are two examples).
>
> The documentation for qvm-block is sparse, but probably because it's a
> striaght-forward utility.
>
> There's no support in qvm-block to assign a device to a VM by UUID, is
> there?
>

Not that I'm aware of.

> Could be handy for some of the automation I'd like to put in place on
> firing up the system.
>
> One can always lsblk|grep|sed|cut|whatever in a sh script, and then use the
> resulting block device for qvm-block, but it'd be a lot cleaner and less
> error-prone if one could say
>
> "qvm-block -a Florp UUID=kasdjflaksjdfaklsdf" or "qvm-block -a FLorp --uid
> asdfkasjdlfkajsd"
>
> Just a suggestion. (And for any other qvm-* that refer to block devices,
> perhaps.)
>

Thanks. Tracking:

https://github.com/QubesOS/qubes-issues/issues/2272

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXwQAaAAoJENtN07w5UDAwMZwQAKrq5sIjoFQkeZBZBx5+4GFe
Pu+HThioVfOcu9uhtRZmsEi20S1slzxle3mG5nICmx7zoBArI3P7zY7/4ip7yGJd
ZGvZDZmxQ0pGAO51U1k3tBlr2Y48WU+jRZtP9RF5v9iSwWrfHzsDjq8qhAXKGAYt
tjMlyGhcSdBBaBU6C0eyW1KOrVpUZhEfpTz9QkY0TWO0uxF0Fa4tVkM5Thn/TFCT
i3rjj78KdsKR1V2SPO5lIKoijDAdcKI96VINgu1NzeAEUEkf8w7LNK8IlEB0u/8a
Adb2/Gyur3dn5ptNtz0miPYhjY/Mz0alIubh2vs/ZCzr46Kdc5hsnlGTrw++fiNe
6AymvPOmcXP1Eneax5stJayh+7ZZx60HX/x6j/nAb9ev86l8hIYeW62iuh0m9mfE
/mcm6ZlXXIHNBHhMDmU43PoFIxKulB+86JUI2Zv0/yfF1U5rEgOct7pdaHn6Bx+d
y94G5mXWJ6khKd2+Vv2HOaVqgiSxRHIIIxzYF/VXXeSnhEhS0d2Xw68+ve0K0d0z
x31RSYN5k8ak1jfisYmncYda+dhCZHjlY5kAdf686ehpeiBVR25urCikEI7auXZ1
nz5hel6G7Ra8KGJpVNXUBzCbrE8dXB5swUxBw/x9GVEQ8ApmC+pK9tPjPeoXNBdx
syPzdtRHFJ2S+qKmmVvt
=wi/F
-----END PGP SIGNATURE-----