search for: cow2

Hello All, I am using Centos 6.3 with libvirt 0.910 and qemu-kvm 0.12 I had to resize a qcow2 disk, and came across several issues; I used this command to resize the image: sudo -i /usr/bin/qemu-img /var/lib/libvirt/images/mydisk.img resize +100G . The disk is attached using virtio. I then tried to use parted from within the guest to resize the partition. The first problem was that the...

...les "truncate -s 512M file.img". > 'du --apparent-size' and 'ls -l' are the same thing, so it's not > really surprising that you see the same numbers here. Indeed, I expected those to be the same, just figured I would show them both for completeness. > For qcow2 files, the virtual size is not related to the "apparent" > size, as you can easily prove: So you are saying when I do the virt-sparsify its converting the image from raw to cow2? I studied the man page for virt-sparsify and tried again with the flag "--format raw" (output2....

...virsh list Id Name State ---------------------------------- 1 nd-50f05b3-0 paused Additional notes ================ * The process seams to deadlock somewhere, CPU usage is near to 0% * The disk images are available on both hosts at the same location (I'm using a COW2 image based on another COW2 image, both are available) * The shared FS is mounted through fuse-sshfs * I just noticed that my clocks are skewed. I will rerun the whole test with a correctly setup ntp server, but I had the same problem last week with perfectly synchronized clocks, so I doubt this...

...ction on "IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to indicate what I would expect where "ls -lh" shows the full apparent size and "du -sh" shows the actual size. But my actual results from testing are different. In the following example input.qcow2 is before sparsify and output.qcow2 is after. Doing ls reports full size for input but a small size for the output: root@testingbox:/tmp/test # ls -lh total 3.1G -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 -rw-r--r-- 1 root root 790M Jun 1...

...ction on "IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to indicate what I would expect where "ls -lh" shows the full apparent size and "du -sh" shows the actual size. But my actual results from testing are different. In the following example input.qcow2 is before sparsify and output.qcow2 is after. Doing ls reports full size for input but a small size for the output: root@testingbox:/tmp/test # ls -lh total 3.1G -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img -rw-r--r-- 1 root root 51G Jun 14 22:30 input.qcow2 -rw-r--r-- 1 root root 790M Jun 1...

...pty'> ? <target type='virtio' name='org.linux-kvm.port.1'/> ?<address type='virtio-serial' controller='0' bus='0'/> </channel> ??? <disk type='file' device='disk'> ????? <driver name='qemu' type='qcow2'/> ????? <source file='/home/user1/linux_installed/image.cow2'/> ????? <target dev='hda' bus='ide'/> ????? <alias name='ide-disk0'/> ??????? <address type='drive' controller='0' bus='0' unit='0'/> ??? &lt...

...NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to > indicate what I would expect where "ls -lh" shows the full apparent size > and "du -sh" shows the actual size. But my actual results from testing > are different. > > In the following example input.qcow2 is before sparsify and output.qcow2 > is after. > > Doing ls reports full size for input but a small size for > the output: > root@testingbox:/tmp/test # ls -lh > total 3.1G > -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img > -rw-r--r-- 1 root root 51G Jun 14 22:30 input...

...NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to > indicate what I would expect where "ls -lh" shows the full apparent size > and "du -sh" shows the actual size. But my actual results from testing > are different. > > In the following example input.qcow2 is before sparsify and output.qcow2 > is after. > > Doing ls reports full size for input but a small size for > the output: > root@testingbox:/tmp/test # ls -lh > total 3.1G > -rw-r--r-- 1 root root 512M Jun 14 22:30 file.img > -rw-r--r-- 1 root root 51G Jun 14 22:30 input...

On Wed, Jun 22, 2016 at 12:40:40AM -0500, libvirt_users@skagitattic.com wrote: > So you are saying when I do the virt-sparsify its converting the image > from raw to [qcow2]? No. virt-sparsify will use the same input and output formats, unless you use the --convert option. > I studied the man page for virt-sparsify and tried again with > the flag "--format raw" (output2.cow2). This output files looks as I > first expected. > > # ls -lrh &...

...k size=50 --nographics -x "console=ttyS0" Starting install... Retrieving file MANIFEST... | 3.3 kB 00:00 ... Retrieving file linux... | 6.0 MB 00:03 ... Retrieving file initrd.gz... | 29 MB 00:09 ... Allocating 'testimage.qcow2' | 50 GB 00:00 Creating domain... | 0 B 00:00 Connected to domain testimage Escape character is [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Lin...

...u, bridge=virbr0, mac=' + _s_vm_mac ] device_model = '/usr/lib64/xen/bin/qemu-dm' boot = "c" sdl = 0 vnc = 1 vncunused = 0 vnclisten = '0.0.0.0' vncpasswd = '***' serial = 'pty' usb = 1 usbdevice = 'tablet' name = _s_name disk = [ 'tap:qcow2:/home/bruce/vm-check.img,hda,w!' ] vncdisplay = _s_vnc_display [3]qemu-dm log i: domid: 5310 qemu: the number of cpus is 1 config qemu network with xen bridge for tap5310.0 virbr0 Strip off blktap sub-type prefix to /home/malei/vm-check.img (drv 'qcow2') Watching /local/domain/0/d...