Skip to content
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

Improve usability of manipulating various VMs disk sizes #1441

Open
1 of 2 tasks
bnvk opened this issue Nov 19, 2015 · 3 comments
Open
1 of 2 tasks

Improve usability of manipulating various VMs disk sizes #1441

bnvk opened this issue Nov 19, 2015 · 3 comments
Labels
help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: minor Priority: minor. The lowest priority, below "default." T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@bnvk
Copy link

bnvk commented Nov 19, 2015

Earlier today I encountered the following error message upon booting up a StandaloneVM

low-disk-space

It was perplexing as I was only using 21GB of the 26GB allotted, but I figured it was something like I encountered with /tmp directory in issue #1191

After searching the mailing list and the docs, I first thought "Resizing Disk Image" was the right thing. I tried a couple of the steps in there to no avail. Then I tried "
Resizing root.img Size"
steps and issue fixed. All told this took me about 30 minutes. So, couple ideas:

  • Make the wording in the notification and the documentation better match (i'm doing this right now)
  • Make it relatively intuitive to explain & do these things from the VM's GUI settings
marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue Dec 8, 2015
_doc:
    tag mm_b079a3b7
    tagger Marek Marczykowski-Górecki <[email protected]> 1449588545 +0100

    Tag for commit b079a3b70547039980289dc780e49cde4fc405a8
    gpg: Signature made Tue 08 Dec 2015 04:29:07 PM CET using RSA key ID 9684938A
    gpg: Good signature from "Marek Marczykowski-Górecki (Qubes Documentation Signing Key) <[email protected]>"

    b079a3b Merge remote-tracking branch 'origin/pr/62'
    1ae209a moved Getting Started & Research to site repo QubesOS/qubes-issues#1460
    40c1312 fixed Privacy Guides heading QubesOS/qubes-issues#1202
    84c1a0c fixed merge conflict QubesOS/qubes-issues#1202
    c956a2c saved changes to Doc index as QubesOS/qubes-issues#1202
    c7aa41b started porting over Whonix documentation QubesOS/qubes-issues#1201 QubesOS/qubes-issues#1202
    554e5fd harmonized names for 'Resizing' things and improved Root Disk Size (QubesOS/qubes-issues#1441)
    015758b fixed link to Template Whonix and Doc ToC
    763abfb added Privacy section, moved TorVM & VPN there
    25a2fc0 Merge branch 'upstream'
    fb107c1 fixed markdown on resize-root-disk-image
@marmarek marmarek added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: minor Priority: minor. The lowest priority, below "default." ux User experience labels Jan 6, 2016
@marmarek
Copy link
Member

marmarek commented Jan 6, 2016

Actually this notification is nothing Qubes specific. It is just standard (gnome?) application installed by default in template.

@marmarek marmarek added this to the Far in the future milestone Jan 6, 2016
@bnvk bnvk mentioned this issue Feb 17, 2016
20 tasks
andrewdavidwong added a commit that referenced this issue Jun 7, 2016
@marmarek
Copy link
Member

We have both "private" and "system" (aka "root") volume sizes configurable in GUI qube settings. The "system" one is active only for qubes having own system volume (templates, standalone).
I see two possible improvements here:

  • for template-based qubes, add some info that "system" volume size can be changed in template's settings
  • add info about current usage

The second one may be slightly misleading, as it would be from the time the settings are open, not updated in real-time. So, if qube is writing a lot of data, the number will be outdated. But IMO it's very minor issue.

@marmarta do we want this, or leave it as it is?

@marmarta
Copy link
Member

We have both "private" and "system" (aka "root") volume sizes configurable in GUI qube settings. The "system" one is active only for qubes having own system volume (templates, standalone).
I see two possible improvements here:

* for template-based qubes, add some info that "system" volume size can be changed in template's settings

This is done by QubesOS/qubes-manager#141. Also, I made a pull request to improve the documentation to make it less intimidating ( QubesOS/qubes-doc#765 ) because honestly, when I looked at it myself I really did not think "oh nice just use the GUI to resize" but more like "so many steps, so much can go wrong")

* add info about current usage

Maybe this should rather be added to the Qube Manager? We have current usage but not maximum size; maybe it would be a good idea to add something like % used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: minor Priority: minor. The lowest priority, below "default." T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

4 participants