New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to grow the AppVM's private storage? #5

Closed
marmarek opened this Issue Mar 8, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 6 Apr 2010 17:08 UTC
Research options for automatically or semi-automatically handling a situation when a given AppVM needs more storage (private.img) than originally assigned.

Currently if a user wants to extend private storage for an AppVM, the user must do something like this:

cd /var/lib/qubes/appvms/XXX/
mkdir mnt mnt.new
mount -o loop,ro private.img mnt
truncate -s <new_max_size> private-new.img
mkfs.ext4 private-new.img
mount -o loop private-new.img mnt.new
cp -pr mnt/* mnt.new/
umount mnt mnt.new
rm -f private.img mnt mnt.new
mv private-new.img private.img

... which is a bit, well, not user-friendly ;)

Migrated-From: https://wiki.qubes-os.org/ticket/5

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 14 Mar 2011 21:27 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 14 Mar 2011 21:27 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 15 Mar 2011 00:24 UTC
There is easier way:
Dom0 (AppVM can be running):

cd /var/lib/qubes/appvms/XXX/
truncate -s <new_max_size> private.img

if AppVM is running (still in Dom0):

losetup -a # find loop device connected with private.img
losetup -c /dev/loopX

in AppVM:

resize2fs /dev/xvdb

Tested :)

This can be easly automated with simple qvm-* tool and/or qubes-manager.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 15 Mar 2011 00:24 UTC
There is easier way:
Dom0 (AppVM can be running):

cd /var/lib/qubes/appvms/XXX/
truncate -s <new_max_size> private.img

if AppVM is running (still in Dom0):

losetup -a # find loop device connected with private.img
losetup -c /dev/loopX

in AppVM:

resize2fs /dev/xvdb

Tested :)

This can be easly automated with simple qvm-* tool and/or qubes-manager.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 15 Mar 2011 18:08 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 15 Mar 2011 18:08 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 16 Mar 2011 22:25 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 16 Mar 2011 22:25 UTC

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 23 Mar 2011 23:51 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 23 Mar 2011 23:51 UTC

@marmarek marmarek closed this Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 28 Mar 2011 13:02 UTC
Wait for resize device in AppVM before resize2fs.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 28 Mar 2011 13:02 UTC
Wait for resize device in AppVM before resize2fs.

@marmarek marmarek reopened this Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment