Storing AppVMs on Secondary Drives

Jörg Widmann

unread,

Apr 20, 2020, 11:56:51 PM4/20/20

to qubes...@googlegroups.com

Hello,

I'm trying to add a second HDD to my system. I followed the guide on https://www.qubes-os.org/doc/secondary-storage/, everything but the last step seems to work.

qvm-pool --add poolhd0_qubes lvm_thin -o volume_group=qubes,thin_pool=poolhd0,revision_to_keep=2

qvm-pool: error: failed to add pool poolhd0_qubes: Got empty response from qubesd. See journalctl in dom0 for details.

journalctl:

dom0 qubesd[31119]: permission denied for call b'admin.pool.Add'+b'lvm_thin' (b'dom0' → b'dom0') with payload of 75 bytes

sudo pvdisplay

...

--- Physical volume ---
PV Name /dev/mapper/luks-e3072cf6-a0a5-4dbb-84ce-740661c0db68
VG Name qubes
PV Size 931.51 GiB / not usable 3.71 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 238466
Free PE 0
Allocated PE 238466
PV UUID NCh0Av-HjOc-JJ2F-C5Wh-e7gP-XTYi-vsw7Wgsudo vgdisplay --- Volume group ---
VG Name qubes_dom0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 19261
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 68
Open LV 20
Max PV 0
Cur PV 1
Act PV 1
VG Size 222.57 GiB
PE Size 4.00 MiB
Total PE 56977
Alloc PE / Size 52929 / 206.75 GiB
Free PE / Size 4048 / 15.81 GiB
VG UUID 2M3Rnq-44Vw-hwsR-iutp-hWAo-7yq1-f34fK4

sudo vgdisplay

...

--- Volume group ---
VG Name qubes
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 931.51 GiB
PE Size 4.00 MiB
Total PE 238466
Alloc PE / Size 238466 / 931.51 GiB
Free PE / Size 0 / 0
VG UUID 6KF6Sh-EJXv-uZFY-E83O-iCYB-1tT9-g9ANSF

sudo lvdisplay

...

--- Logical volume ---
LV Name poolhd0
VG Name qubes
LV UUID 8jnL38-xi2m-lqKN-yUaf-z0zB-q0eN-O5fsmv
LV Write Access read/write
LV Creation host, time dom0, 2020-04-20 17:25:55 +0200
LV Pool metadata poolhd0_tmeta
LV Pool data poolhd0_tdata
LV Status available
# open 0
LV Size 931.27 GiB
Allocated pool data 0.00%
Allocated metadata 10.41%
Current LE 238406
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:75

Since I can't find anything online I guess I'm doing something wrong.

Many thanks in advance.

Regards
J0e

unman

unread,

Apr 21, 2020, 11:47:58 AM4/21/20

to qubes...@googlegroups.com

On Tue, Apr 21, 2020 at 05:56:33AM +0200, 'J??rg Widmann' via qubes-users wrote:
> Hello,
>
> I'm trying to add a second HDD to my system. I followed the guide on
> https://www.qubes-os.org/doc/secondary-storage/, everything but the last
> step seems to work.
>
> qvm-pool --add poolhd0_qubes lvm_thin -o
> volume_group=qubes,thin_pool=poolhd0,revision_to_keep=2
>
> usage: qvm-pool [--verbose] [--quiet] [--help] [-o options]
> [-l | -i POOLNAME | -a NAME DRIVER | -r NAME | -s POOLNAME
> | --help-drivers]
>
> qvm-pool: error: failed to add pool poolhd0_qubes: Got empty response from
> qubesd. See journalctl in dom0 for details.
>
> journalctl:
>
> dom0 qubesd[31119]: permission denied for call

> b'admin.pool.Add'+b'lvm_thin' (b'dom0' ??? b'dom0') with payload of 75 bytes
>

"permission denied" - try call with sudo ?

Jörg Widmann

unread,

Apr 21, 2020, 1:31:44 PM4/21/20

to qubes-users

yes I have tried with sudo, same error

dono...@unseen.is

unread,

Apr 21, 2020, 3:42:31 PM4/21/20

to qubes-users

--

Make sure you're not trying to use existing names for the new pool, vol, etc. That's probably not the issue - just tossing that out.

Jörg Widmann

unread,

Apr 23, 2020, 10:31:34 AM4/23/20

to qubes-users

i tried with different names but no luck same error

Jörg Widmann

unread,

Apr 24, 2020, 11:34:48 AM4/24/20

to qubes-users

i found the error its revisions_to_keep not revison_to_keep, i had to debug trough the source to figure out my typo *faceplam*

Peter Funk

unread,

Apr 29, 2020, 9:35:58 AM4/29/20

to 'Jörg Widmann' via qubes-users

Hello Jörg,

'Jörg Widmann' via qubes-users schrieb am Freitag, den 24.04.2020 um 08:34:
...

> >>> > volume_group=qubes,thin_pool=poolhd0,revision_to_keep=2
> >>> >
> >>> > usage: qvm-pool [--verbose] [--quiet] [--help] [-o options]
> >>> > [-l | -i POOLNAME | -a NAME DRIVER | -r NAME | -s

...

> i found the error its revisions_to_keep not revison_to_keep, i had to
> debug trough the source to figure out my typo *faceplam*

Then it was a least not totally your fault: The software could certainly
be improved in a way that unknown option keywords lead to error messages,
which give more hints. Would you care to share which portion of the
source code led you on the right track to discover your typo?

Best regards, Peter Funk
--
Peter Funk ✉:Oldenburger Str.86, 27777 Ganderkesee, Germany; 📱:+49-179-640-8878

Reply all

Reply to author

Forward