My best guess is that you forgot the -f parameter to qemu-img.
this post was submitted on 30 Nov 2023
9 points (100.0% liked)
Linux
48216 readers
701 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Hmm. Maybe? This would be a virt-manager but though, as I stopped bothering with CLI and just use that again
I did not use virt-manager for a while, but probably it allocates the whole virtual disk by default (i don't remember for sure). Try to create it manually and ensure that checkbox "allocate the whole volume" is disabled. You can also do this with qemu-img create command (see man qemu-img for options).
BTW it is possible to compress existing qcow2 images. Before that I recommend to run fstrim -a inside the VM. Then shut it down and execute qemu-img convert -cp old_image.qcow2 new_image.qcow2 && mv -f new_image.qcow2 old_image.qcow2.
Thanks!
I think qcow2 images are always a fixed size (but I could be wrong on that) however I saw some threads explaining how you could relatively easy modify the size of the qcow2 image :)