Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upchanging VM system storage max. size via GUI not working (R4.0rc1) #3143
Comments
0spinboson
changed the title from
changing system storage max. size via GUI not working (R4.0rc1)
to
changing VM system storage max. size via GUI not working (R4.0rc1)
Oct 3, 2017
andrewdavidwong
added
bug
C: core
labels
Oct 4, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 4, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 6, 2017
Member
Fix already queued:
QubesOS/qubes-core-admin@6091bbb
marmarek/qubes-core-agent-linux@a59ac1b
|
Fix already queued: |
marmarek
closed this
Oct 6, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
0spinboson
Oct 7, 2017
This doesn't appear to have fixed the issue. When I try to increase a VM's System storage max size, I now get a warning that shrinking of the root is disabled.
0spinboson
commented
Oct 7, 2017
|
This doesn't appear to have fixed the issue. When I try to increase a VM's System storage max size, I now get a warning that shrinking of the root is disabled. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Have you installed qubes-core-dom0 4.0.8 (from testing repo)? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
0spinboson
commented
Oct 7, 2017
•
|
Yes, I've installed all of last night's updates, so I figured I'd test it. |
marmarek
reopened this
Oct 7, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
0spinboson
Oct 8, 2017
Precise error when I try to increase the size:
Oct 08 14:23:06 dom0 qubesd[2962]: StoragePoolException('For your own safety, shrinking of root is disabled. If you really know what you are doing, use truncate on appvms/w7/root manually.',) while calling src=b'dom0' meth=b'admin.vm.volume.Resize' dest=b'w7' arg=b'root' len(untrusted_payload)=10
0spinboson
commented
Oct 8, 2017
•
|
Precise error when I try to increase the size: |
marmarek
closed this
in
marmarek/qubes-manager@0c5a2b1
Oct 8, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 9, 2017
Automated announcement from builder-github
The package qubes-manager-4.0.6-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubesos-bot
commented
Oct 9, 2017
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Oct 9, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Oct 9, 2017
Closed
manager v4.0.6 (r4.0) #258
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
0spinboson
Oct 10, 2017
By the way: is it intentional that size increases no longer apply to running VMs? I seem to recall that in R3.2 you could just grow these while the VM was running, but now it doesn't seem to realize its size has been increased until the next boot.
0spinboson
commented
Oct 10, 2017
|
By the way: is it intentional that size increases no longer apply to running VMs? I seem to recall that in R3.2 you could just grow these while the VM was running, but now it doesn't seem to realize its size has been increased until the next boot. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 10, 2017
Member
You mean private storage or system storage? For private it should work immediately. If it doesn't, it's a bug.
|
You mean private storage or system storage? For private it should work immediately. If it doesn't, it's a bug. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
0spinboson
commented
Oct 10, 2017
|
okay, then it's bugged. :) |
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
added a commit
to marmarek/qubes-core-agent-linux
that referenced
this issue
Oct 18, 2017
marmarek
referenced this issue
in QubesOS/qubes-core-agent-linux
Oct 18, 2017
Merged
Handle resize of root filesystem with new partition layout #61
qubesos-bot
referenced this issue
in QubesOS/updates-status
Oct 19, 2017
Closed
core-agent-linux v4.0.12 (r4.0) #277
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 30, 2017
Automated announcement from builder-github
The package qubes-manager-4.0.8-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
qubesos-bot
commented
Oct 30, 2017
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
0spinboson commentedOct 3, 2017
•
edited
Edited 1 time
-
0spinboson
edited Oct 3, 2017 (most recent)
Qubes OS version (e.g.,
R3.2):R4.0-rc1, up to date with current-testing
Affected TemplateVMs (e.g.,
fedora-23, if applicable):dom0
Steps to reproduce the behavior:
open VM settings GUI for any VM, increase the system max. storage size, click OK.
Expected behavior:
increases storage size for the root.img
Actual behavior:
errors out, and appears to be trying to apply the private storage max size to the system storage max size. (E.g. in a VM with 3GB private 10gb system I get an error/warning that I can't decrease the size using this UI, and that I must use truncate if I really want this. In another VM the reported system storage max size has been increased to 68GB (the private max that was already set), though it didn't actually increase the system volume storage max size -- inside the VM it's still set at 10.5GB.
log3.txt