similar to: Temporary use of disk space when deploying KVM with qcow2?

Hello, I'm using libvirt to deploy a series of 7 KVM (in qcow2 format) sequentially. The base image of the qcow2 is an ubuntu server of around 1.6GB. The environment where i am doing this is a Live USB Ubuntu with a persistence file (so that changes made remain). So, the problem: * If the persistence file (i.e. free disk space in the live ubuntu) is up to around 1.6GB, the qemu process of

Hi all. I have a few questions regarding the qcow2 format. 1/ Allocated size vs. file size When creating a VM, I indicated a size of 10 G. $ls -lsh 7,7G -rw------- 1 libvirt-qemu libvirt-qemu 11G oct. 14 10:04 prod.qcow2 The allocated size is lesser than max size. Alright. I think I more or less grab the difference between allocated size and file size, but I'm not sure I get the point

Hi Eric and list, I had another production VM start pausing itself.  This one had been running for more than 4 years on a 60G LVM volume.  It has had the occasional snapshot during that time though all have been "removed" using the virt-manager gui so I used qemu-img as you suggested. # qemu-img convert /dev/trk-kvm-02-vg/rt44 -O qcow2 /mnt/scratch/rt44.qcow2 dd'd the qcow2

Hi there. I can't understand why I am having this different values: proxmox01:/vms/images# df Sist. Arq. Tam. Usado Disp. Uso% Montado em udev 252G 0 252G 0% /dev tmpfs 51G 9,4M 51G 1% /run /dev/sda4 433G 20G 413G 5% / tmpfs 252G 63M 252G 1% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock efivarfs 496K 335K

On Wed, Sep 11, 2013 at 10:33:06AM +0800, bigclouds wrote: > hi,all > images of qcow2 format with backing files, its backing files have > two path infos (absolute path and relative path), This is not true. The file format only contains the relative path. qemu-img info will print an absolute path, but it's not stored inside the file. > how to let > libguestfs use absolute path

Am 09.05.2015 um 23:19 schrieb Paul R. Ganci <ganci at nurdog.com>: > On 05/08/2015 11:41 PM, James Hogarth wrote: >> was wondering if this procedure might work to do what I desire: >> >> 1.) Shutdown the VMs >> 2.) Archive the VM image directory /home/vmimages to a network drive >> 3.) Use parted or fdisk to delete present /home partition >> 4.) Use

On 05/08/2015 11:41 PM, James Hogarth wrote: > was wondering if this procedure might work to do what I desire: > > 1.) Shutdown the VMs > 2.) Archive the VM image directory /home/vmimages to a network drive > 3.) Use parted or fdisk to delete present /home partition > 4.) Use parted or fdisk to re-create smaller/home partition and new vm-images > 5.) Create XFS file system on

thanks . now i know qcow2 only store relative path. look at my error message, 6a3256bb-b247-4fb5-9f75-8ffa7151eeda i a symlink to a LV. it is the backing_file of several images(LV).. i have no idea of the reason of the error. # virt-win-reg 6a3256bb-b247-4fb5-9f75-8ffa7151eeda 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' 'Productname' hivex:

I guess I need the list again. I try to install my first KVM guest. Here is what I do, and finally, what I stumble on. First I created a qcow2 img: # qemu-img create -f qcow2 /var/lib/libvirt/images/test1.img 15G And I created a network bridge (not essential here) To get a text-based install, I followed this how-to:

On Thursday, 2 April 2020 17:30:39 CEST Richard W.M. Jones wrote: > On Thu, Apr 02, 2020 at 03:21:14PM +0200, Pino Toscano wrote: > > On Thursday, 2 April 2020 14:49:18 CEST Richard W.M. Jones wrote: > > > Previously we placed large files in g#get_cachedir () (usually > > > /var/tmp). However the problem is this ties the libguestfs appliance > > > and the

On Mon, Aug 11, 2014 at 02:06:54PM -0500, Andrew Martin wrote: > Hello, > > I am running several virtualization servers with QEMU 1.4.x and > libvirt 1.0.2 on Ubuntu 12.04 and am working on optimizing the cache= > and aio= options for the virtual machines. These VM images are mostly > qcow2, and are served both from a local ext4 filesystem (with > data=ordered,barrier) and

When using oVirt >= 4.3, we can enable the NBD based backend in imageio by specifying that we transfer raw data when creating a transfer. With   the NBD backend, we can import to disks using qcow2 format. To make it work, we override output#transfer_format to return always raw format, but we create the disk on RHV side using qcow2 format. The pipeline looks like this: qemu-img convert

On Thu, Apr 02, 2020 at 05:51:32PM +0200, Pino Toscano wrote: > On Thursday, 2 April 2020 17:30:39 CEST Richard W.M. Jones wrote: > > On Thu, Apr 02, 2020 at 03:21:14PM +0200, Pino Toscano wrote: > > > On Thursday, 2 April 2020 14:49:18 CEST Richard W.M. Jones wrote: > > > > Previously we placed large files in g#get_cachedir () (usually > > > > /var/tmp).

On 12/09/2013 09:03 PM, lyz_pro@163.com wrote: > Hi all > > I have a problem when I use `virsh attach` to attach a qcow2 disk to vm without argument --subdirver=qcow2 > and this makes the qcow2 disk become a raw format disk, and the data in this disk is missing in guest os > and also I have used guestmout to confirm this, the same result. The format of a file is important. By

On 11/06/2014 03:45 PM, Francesco Morosinotto wrote: > Hi everybody, > > I'm trying to implement in the non profit organization where I work a > backup strategy for our VMs. > > At the moment I weekly backup the machine (on sunday nights) by stopping > the vm, making a snapshot, exporting the xml descriptor file and syncing > these files to a remote backup server.

Occasionally this test will choose a random seed which results in an all-zeroes disk. The test tries to convert this to a compressed qcow2 file, and fails because no compressed clusters are detected in the resulting file. This happens because qcow2 stores zero clusters with a special sparse representation, they are never stored compressed, so a disk with only zeroes in it will never contain

On 8/8/23 00:28, Richard W.M. Jones wrote: > Occasionally this test will choose a random seed which results in an > all-zeroes disk. The test tries to convert this to a compressed qcow2 > file, and fails because no compressed clusters are detected in the > resulting file. This happens because qcow2 stores zero clusters with > a special sparse representation, they are never stored

Hi all I have a problem when I use `virsh attach` to attach a qcow2 disk to vm without argument --subdirver=qcow2 and this makes the qcow2 disk become a raw format disk, and the data in this disk is missing in guest os and also I have used guestmout to confirm this, the same result. Is there any way to let me find back the data in this disk ? the version of libvirt and kvm is : Compiled

On Monday, 6 April 2020 19:45:44 CEST Daniel P. Berrangé wrote: > On Thu, Apr 02, 2020 at 05:51:32PM +0200, Pino Toscano wrote: > > On Thursday, 2 April 2020 17:30:39 CEST Richard W.M. Jones wrote: > > > On Thu, Apr 02, 2020 at 03:21:14PM +0200, Pino Toscano wrote: > > > > On Thursday, 2 April 2020 14:49:18 CEST Richard W.M. Jones wrote: > > > > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you a lot for your reply; > You should really consider using libvirt live snapshots. With new > enough libvirt and qemu, you can even get optimal behavior with no guest > downtime. This topic comes up frequently on the list; for example, a > quick search found this in the archives: > >