search for: gdanti

Displaying 4 results from an estimated 4 matches for "gdanti".

Did you mean: danti
2018 Jan 30
4
Create qcow2 v3 volumes via libvirt
Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file zzz.qcow2 zzz.qcow2: QEMU QCOW Image (v2), has backing file (path /mnt/vmimages/centos6.img), 8589934592 bytes [root@...
2018 Apr 30
0
Re: Create qcow2 v3 volumes via libvirt
Il 30-01-2018 13:17 Gionatan Danti ha scritto: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file > is a qcow2 version 2 (compat=0.10) file. Example: > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img > Vol zzz.qcow2 created > [root@gdanti-lenovo vmimages]# file zzz.qcow2 > zzz.qcow2: QEMU QCOW Image (v2), has backing file (path > /mnt/vmimages/centos6.img),...
2018 May 01
1
Re: Create qcow2 v3 volumes via libvirt
...Gionatan Danti wrote: > > Hi all, > > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > > > - when creating a new volumes using vol-create-as, the resulting file is > a > > qcow2 version 2 (compat=0.10) file. Example: > > > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > > 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img > > Vol zzz.qcow2 created > > Yes, for sake of backcompat we default to v2 unless something > requires v3. You can't use vol-create-as to create a v...
2018 May 01
0
Re: Create qcow2 v3 volumes via libvirt
..., Jan 30, 2018 at 01:17:21PM +0100, Gionatan Danti wrote: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file is a > qcow2 version 2 (compat=0.10) file. Example: > > [root at gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img > Vol zzz.qcow2 created Yes, for sake of backcompat we default to v2 unless something requires v3. You can't use vol-create-as to create a v3 image, you need to use...