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 up"qvm-volume extend" fails calling qubes.ResizeDisk #3906
Comments
davex25
referenced this issue
May 17, 2018
Open
Apps do not open when starting VM from launcher #3533
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
davex25
May 17, 2018
I think I see what happened here. Also applies to the other issue I referenced (#3533)
The VM I'm working with is using an older template that I've upgraded multiple times. Somehow certain rpc scripts that are expected to exist on that template do not, including qubes.StartApp and qubes.ResizeDisk.
Is there a utility of some kind that ensures a specified VM has all the shell scripts the RPC system expects it to have?
davex25
commented
May 17, 2018
|
I think I see what happened here. Also applies to the other issue I referenced (#3533) The VM I'm working with is using an older template that I've upgraded multiple times. Somehow certain rpc scripts that are expected to exist on that template do not, including qubes.StartApp and qubes.ResizeDisk. Is there a utility of some kind that ensures a specified VM has all the shell scripts the RPC system expects it to have? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
davex25
May 17, 2018
For fun, tried copying those scripts from a VM that contained them, but seems there are other missing dependent executable scripts, e.g. /usr/lib/qubes/resize-rootfs. I copied that one to my problematic VM and the resize seemed to work.
But seems like there needs to be some way to automatically check that these kinds of scripts exist on the VM. I've made many modifications to this template VM and don't really want to throw it away.
davex25
commented
May 17, 2018
|
For fun, tried copying those scripts from a VM that contained them, but seems there are other missing dependent executable scripts, e.g. /usr/lib/qubes/resize-rootfs. I copied that one to my problematic VM and the resize seemed to work. But seems like there needs to be some way to automatically check that these kinds of scripts exist on the VM. I've made many modifications to this template VM and don't really want to throw it away. |
andrewdavidwong
added
bug
C: other
labels
May 18, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
May 18, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Is it a template imported from 3.2? |
marmarek
referenced this issue
May 27, 2018
Open
Test and publish template/standalonevm 3.2->4.0 migration instruction. #3934
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
davex25
commented
May 29, 2018
|
Yes it was. |
davex25 commentedMay 17, 2018
•
edited
Edited 2 times
-
davex25
edited May 17, 2018 (most recent)
-
davex25
edited May 17, 2018
Qubes OS version:
4.0 rc3 upgraded, and fully reinstalled 4.0 release version.
Affected component(s):
qvm-volume
Steps to reproduce the behavior:
Try to increase size of existing running VM root storage, e.g.
"sudo qvm-volume extend fedora-26:root 40GB"
In this case I'm doing an online resize, but have also tried offline and got similar results.
Expected behavior:
Root size increased.
Actual behavior:
Prints message:
"Online resize of volume qubes_dom0/vm-fedora-26-root failed (you need to resize filesystem manually): /bin/sh: /etc/qubes-rpc/qubes.ResizeDisk: No such file or directory"
VM root storage was not increased, but if I run "qvm-volume extend 40GB" again, I get:
"For your own safety, shrinking of root is disabled."
But this is also wrong, the disk wasn't actually resized to 40GB yet.
General notes:
Related issues: