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 upRoot image file parameter to qvm-create limited to free space in /tmp (2GiB) #3422
Comments
andrewdavidwong
added
bug
C: core
labels
Dec 23, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Dec 23, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Dec 23, 2017
Member
The file is not piped to /tmp, but to the target location (LVM volume in default installation). The problem is somewhere else - it does not check its size and by default root volume have 10G. It should resize it first to the size of source file.
|
The file is not piped to /tmp, but to the target location (LVM volume in default installation). The problem is somewhere else - it does not check its size and by default root volume have 10G. It should resize it first to the size of source file. |
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
daniel-ayers commentedDec 23, 2017
•
edited by andrewdavidwong
Edited 1 time
-
andrewdavidwong
edited Dec 23, 2017 (most recent)
Qubes OS version:
4.0RC3
Affected TemplateVMs:
dom0
Steps to reproduce the behavior:
in dom0:
Expected behavior:
New VM created using given root image file (in my example, 40GiB raw image).
Actual behavior:
qvm-create pipes root image file to a temp file in /tmp and therefore runs out of space on /tmp if root.img > 2GiB.
Same behaviour regardless for --root-copy-from and --root-move-from
General notes:
The root.img I am using was converted vdi -> raw using qemu-img -O raw.
Given the semantics implied by both --root-copy-from and --root-move-from it does not appear necessary to write any file to /tmp.
Related issues: