qvm-grow-private not growing /rw

[Alex Dubois]

Hi,

I have a VM that I restaured from a Q2B2 backup.
I issued from Dom0 terminal a qvm-grow-private vmName 4096MB
I started the VM and the /rw is still at default value.
Shutdown VM. Check value in Qubes Manager, value is set correctly.

I tested with a new testVM, booted it, shutdown...
issued from Dom0 terminal qvm-grow-private testVM 4096MB
booted it. df -h still show 2GB.

Did the same set of tests using the Qubes Manager GUI to grow the partition, same results.

I suspect the qvm-grow-private command worked and set the value in the qubes.xml file. I am not sure what is the process to effectively increase the size... Is it on next boot?

Thanks,
Alex

[Alex Dubois]

/var/lib/qubes/appvms/myappvm/private.img is of the right size. (8GB now has I tried to increase the size via another method).
I have a volatile.img of 11GB...
I have tried to move it away as it is suppose to be temporary and destroyed on shutdown... but it is recreated on next boot and not discarded on shutdown.

 

[Marek Marczykowski-Górecki]

On 19.12.2013 23:14, Alex Dubois wrote:
>
>
> On Thursday, 19 December 2013 19:51:05 UTC, Alex Dubois wrote:
>>
>> Hi,
>>
>> I have a VM that I restaured from a Q2B2 backup.
>> I issued from Dom0 terminal a qvm-grow-private vmName 4096MB
>> I started the VM and the /rw is still at default value.
>> Shutdown VM. Check value in Qubes Manager, value is set correctly.
>>
>> I tested with a new testVM, booted it, shutdown...
>> issued from Dom0 terminal qvm-grow-private testVM 4096MB
>> booted it. df -h still show 2GB.
>>
>> Did the same set of tests using the Qubes Manager GUI to grow the
>> partition, same results.
>>
>> I suspect the qvm-grow-private command worked and set the value in the
>> qubes.xml file. I am not sure what is the process to effectively increase
>> the size... Is it on next boot?
>>
>> Thanks,
>> Alex
>>
>
> /var/lib/qubes/appvms/myappvm/private.img is of the right size. (8GB now
> has I tried to increase the size via another method).

Try "resize2fs /dev/xvdb" in VM. It should be called automatically, but
perhaps for some reason it isn't

> I have a volatile.img of 11GB...
> I have tried to move it away as it is suppose to be temporary and destroyed
> on shutdown... but it is recreated on next boot and not discarded on
> shutdown.

Yes, but it is sparse file, check the real size with "ls -lsh"

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Alex Dubois]

Great thanks fixed. Let me know if you want me to check something on my system. (Brand new install R2B3 with restaure of R2B2 VMs (using existing R2B3 template).

Thanks,
Alx

[cprise]

Terrible lack of consistency here. We need some way to handle the condition of user resizing when the VM is not running (or not allowing resize when VM not running). I just spent a chunk of time trying to figure out why /rw was running out of space when I was sure I had already expanded the image size.

[Marek Marczykowski-Górecki]

As said earlier in this thread - this is supposed to to work now. When did you
resized private VM store? What version of qubes-core-vm do you have in this
VM? Anything interesting in /var/log/messages in this VM regarding resize2fs?

[cprise]

Its version 2.1.25.1. There are no messages that indicate resize
failure... no messages from the times I tried to resize when the VM was
down.

It /has/ worked for me thus far... it just so happens I had the VM
running whenever I resized in the past. That one time it failed (but
seemed to work) was when the VM was down.

Sigh.... I am using VM Manager BTW!

[Marek Marczykowski-Górecki]

I can't reproduce it - it just works for me. Perhaps this have something to do
with exact values - from what size to what size did you resized?

> Sigh.... I am using VM Manager BTW!

This doesn't matter, the same code is called from there.

[cprise]

I can't remember the values exactly. It was starting from somewhere in
the neighborhood of 25GB and I tried to set it to 40GB. VM Manager and
the image size kept reflecting the changes (also subsequently to 41GB
and 42GB), but the filesystem stayed the same until I bumped it up to
45GB while the vm was running.

This is a vm that's using a template which I converted over from R2b2
(if you recall...) and that's the only odd thing about it I can think of.