Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And when I looked at resulting image size, it is MUCH MUCH smaller!
But it runs fine.
Code:
root@server /var/lib/libvirt/images # ls -alh
total 38G
drwx--x--x 2 root root 4.0K Mar 28 12:55 .
drwxr-xr-x 7 root root 4.0K Mar 28 16:15 ..
-rw------- 1 libvirt-qemu kvm 1.5G Mar 29 11:44 centos7-1024ram-minimal-clone0.qcow2
-rw------- 1 root root 2.2G Mar 20 12:52 centos7-1024ram-minimal-clone.qcow2
-rw------- 1 root root 15G Mar 14 10:07 centos7-1024ram-minimal.qcow2
My guess is that the original image was built with "Allocate entire disk now" checked for its 15GB image file. When the clone was made, only the space actually used was copied. If you run "qemu-img info" on that file, you'll see that its virtual size is 15GB, and it will grow up to that size as space is needed.
My guess is that the original image was built with "Allocate entire disk now" checked for its 15GB image file. When the clone was made, only the space actually used was copied. If you run "qemu-img info" on that file, you'll see that its virtual size is 15GB, and it will grow up to that size as space is needed.
Code:
# qemu-img info centos7-1024ram-minimal-clone0.qcow2
image: centos7-1024ram-minimal-clone0.qcow2
file format: qcow2
virtual size: 14G (15032385536 bytes)
disk size: 1.4G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
refcount bits: 16
corrupt: false
# virsh snapshot-list centos7-1024ram-minimal
Name Creation Time State
------------------------------------------------------------
# virsh snapshot-list centos7-1024ram-minimal-clone0
Name Creation Time State
------------------------------------------------------------
#
@fanoflq, rknichols is indicating at centos7-1024ram-minimal.qcow2 volume. You need to check for this volume. Check whether block.0.capacity and block.0.physical are same for centos7-1024ram-minimal.
@fanoflq, rknichols is indicating at centos7-1024ram-minimal.qcow2 volume. You need to check for this volume. Check whether block.0.capacity and block.0.physical are same for centos7-1024ram-minimal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.