Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On 05/22/2018 01:53 PM, Paul O'Rorke wrote: 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

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

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

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On 04/05/2018 10:26, Kashyap Chamarthy wrote: Yes, you still have to clean up external snapshot metadata manually, as the link below indicates. Deleting external snapshots is a non-trivial problem. For example, if you have a disk image chain like: [A] <-- [B] <-- [C] <-- [D] Now if

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On Wed, May 02, 2018 at 02:45:05PM +0200, Gionatan Danti wrote: > On 01/05/2018 22:49, Gionatan Danti wrote: > > Ok, I think I'll continue to use RAW images + filesystem snapshots + > > external snapshot when required. > > It is unfortunate that we have no GUI to manage external snapshots. I > > ev

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On 01/05/2018 22:49, Gionatan Danti wrote: Ok, I think I'll continue to use RAW images + filesystem snapshots + external snapshot when required. It is unfortunate that we have no GUI to manage external snapshots. I even remember that external snapshot remove was not supported - I had to use the

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

Thanks for the suggestions Eric, great stuff and most appreciated. I will have a play in my sandbox... *Paul O'Rorke* *Tracker Software Products (Canada) Limited * www.tracker-software.com Tel: +1 (250) 324 1621 Fax: +1 (250) 324 1623

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

Thanks for the suggestions Eric, great stuff and most appreciated. I must play in my sandbox... *Paul O'Rorke* *Tracker Software Products (Canada) Limited * www.tracker-software.com Tel: +1 (250) 324 1621 Fax: +1 (250) 324 1623

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On 05/01/2018 04:17 PM, Paul O'Rorke wrote: I have been using internal snapshots on production qcow2 images for a couple of years, admittedly as infrequently as possible with one exception and that exception has had multiple snapshots taken and removed using virt-manager's GUI. I was unaware

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

I have been using internal snapshots on production qcow2 images for a couple of years, admittedly as infrequently as possible with one exception and that exception has had multiple snapshots taken and removed using virt-manager's GUI. I was unaware of this: There are some technical downsides

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

Il 01-05-2018 22:25 Eric Blake ha scritto: That's fairly accurate. Also, mixing internal and external snapshots at the same time is likely to trigger some known data-loss problems, if you are not extremely careful, so for now, just pick one or the other and stick to it (I hope to someday enhance

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On 05/01/2018 03:11 PM, Gionatan Danti wrote: Il 01-05-2018 10:56 Daniel P. Berrangé ha scritto: qcow2 is widely used in production at large scale in general. Just not with internal snapshots - almost everything uses external snapshots, aka backing file chains. The QEMU community still tends to

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

Il 01-05-2018 10:56 Daniel P. Berrangé ha scritto: qcow2 is widely used in production at large scale in general. Just not with internal snapshots - almost everything uses external snapshots, aka backing file chains. The QEMU community still tends to discourage use of internal snapshots. There ar

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On Tue, May 01, 2018 at 12:35:05PM +0200, Gianluca Cecchi wrote: > On Tue, May 1, 2018 at 10:45 AM, Daniel P. Berrangé > wrote: > > > On Tue, 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: > > > > > >

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On Tue, May 1, 2018 at 10:45 AM, Daniel P. Berrangé wrote: > On Tue, 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 > >

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On Mon, Apr 30, 2018 at 08:42:56PM +0200, Gionatan Danti wrote: > Another question: how reliable are qcow2 ver2/3 files nowadays? Are you > using them in production environments? qcow2 is widely used in production at large scale in general. Just not with internal snapshots - almost everything uses

Re: [libvirt-users] Create qcow2 v3 volumes via libvirt

On Tue, 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@gdanti-lenovo vmi

Re: [libvirt-users] 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 d

[libvirt-users] 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 --