Resizing template vm works, but doesn't fix running out of space -- because updates use something called disp-mgmt

[bill...@gmail.com]

I got a ping saying there was an update for my fedora-30 template VM,  So, I started the Qubes updater.  I then get the error that it needs an additional 34 MB to install the kernel image.  No problem, I think.  So I go to the documentation and look up how to increase the size of the template VMs.  Easy peasy -- I increase the size of the Fedora-30 template by a couple of gigs, and reboot-- and the new space shows up.  Great I think.  I start the updater and get the same error.  I then watch it happen, and when I start the updater, it opens something called the  "disp-mgmt-fedora-30" vm, which I didn't even know existed.  Obviously, changing the size of the fedora template vm didn't change the size of this.

How do I change the size of the "disp-mgmt-fedora-30" vm -- and is it safe to to?  I assume it's hidden from me for a reason...

Thanks!

billo

[Cody Gardner]

>I got a ping saying there was an update for my fedora-30 template VM,  So, I started the Qubes updater.  I then get the error that it needs an additional 34 MB to install the kernel image.  No problem, I think.  So I go to the documentation and look up how to increase the size of the template VMs.  Easy peasy -- I increase the size of the Fedora-30 template by a couple of gigs, and reboot-- and the new space shows up.  Great I think.  I start the updater and get the same error.  I then watch it happen, and when I start the updater, it opens something called the  "disp-mgmt-fedora-30" vm, which I didn't even know existed.  Obviously, changing the size of the fedora template vm didn't change the size of this.

>

>How do I change the size of the "disp-mgmt-fedora-30" vm -- and is it safe to to?  I assume it's hidden from me for a reason...

I had a similar issue, but more space was required. I increased the "System storage max. size" by a couple GB on the Fedora-30 template, attempted the update install again, and it was successful.

To do this, go to the "Qube Settings" of the fedora-30 template, and under the "Disk storage" section of the "Basic" settings tab, increase the "System storage max. size:" by whatever amount you need.

I'm not sure if it is a requirement for the Qube (the fedora-30 template in this case) to be powered off, but I doubled checked and made sure mine was before making this change.

I apologize in advance if the formatting of this isn't correct, and a second apology for forgetting to copy the mailing list the first time. 

--Cody

[bill...@gmail.com]

Well, I tried again and the upgrade worked.  I don't get it.  I changed the size of the template yesterday, and it didn't work.  Today, I didn't change anything, and it did.  The only thing that changed this time was that I hard-power-cycled the machine, where before I had merely shut down the vms, and then brought them up again.  So, I think you are right -- after changing the size of the template vm, I had to "really" power cycle everything instead of just shutting it down using the qubes manager.  Go figure.

Thanks

billo