resize of private volume: dvm vs. named dvm

[lik...@gmx.de]

Hi,

there seem to be a difference between a dvm and a named dvm.
By named dvm a mean a dvm created like explained here: https://github.com/Qubes-Community/Contents/blob/master/docs/common-tasks/opening-urls-in-vms.md#using-named-dispvms
e.g. qvm-create -C DispVM -t fedora-28-dvm -l red dstVM

By dvm I mean a vm which was created like explained here: https://www.qubes-os.org/doc/disposablevm-customization/#creating-a-new-dvm-template
e.g.
[user@dom0 ~]$ qvm-create --template debian-9 --label red custom-dvm
[user@dom0 ~]$ qvm-prefs custom-dvm template_for_dispvms True
[user@dom0 ~]$ qvm-features custom-dvm appmenus-dispvm 1

When I try to resize the private volume it works with a dvm but not in a named dvm. Resizing is ignored in a named dvm. Resizing is done by
qvm-volume resize dvm:private XGB

What am I doing wrong?

Thanks in advance, Pete

[unman]

In the first case you are creating a disposableVM, based on a a DVM
Template, fedora-28-dvm
In the second case you are creating a DVM Template, which will be used
as the basis for disposableVMs.

That is the difference, and it's why you cant resize the named dvm - the
named dvm takes its properties from the underlying DVM Template.

unman

[lik...@gmx.de]

On 3/30/19 2:56 AM, unman wrote:

> In the first case you are creating a disposableVM, based on a a DVM
> Template, fedora-28-dvm
> In the second case you are creating a DVM Template, which will be used
> as the basis for disposableVMs.
>
> That is the difference, and it's why you cant resize the named dvm - the
> named dvm takes its properties from the underlying DVM Template.
>
> unman
>

Thanks for the clarification, unman! :)

What's the reason that for creating a dvm, we have to go the way: template -> AppVm (dvm-template) -> dvm
Why is it conceptionally not possible to create a dvm directly from a template: template -> dvm?

[unman]

This used to be the norm, but as part of the move to multiple
disposableVMs that path has gone. Now a DVM Template has to be an appVM.
Does it have to be like this? I suppose not, but what is the issue?