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] Drive-backup functions.

On 05/01/2018 02:08 PM, Matthew Schumacher wrote: List, Two years ago there was discussion on implementing QEMU's block-dirty-bitmap backup solution: https://www.redhat.com/archives/libvir-list/2016-June/msg00380.html https://www.redhat.com/archives/libvir-list/2016-April/msg00401.html But I

[libvirt-users] Drive-backup functions.

List, Two years ago there was discussion on implementing QEMU's block-dirty-bitmap backup solution: https://www.redhat.com/archives/libvir-list/2016-June/msg00380.html https://www.redhat.com/archives/libvir-list/2016-April/msg00401.html But I haven't seen anything since, and looking through g

Re: [libvirt-users] Server 2016 locked in paused state

Martin - thank you! `virsh domstate --reason $domain` was exactly what I was looking for. root@trk-kvm-01:~/scripts# virsh domstate --reason sharepoint_server paused (I/O error) Looks like running out of space? I had also thought about space and had done an lvextend but I also use DRBD and

Re: [libvirt-users] Server 2016 locked in paused state

Hi Francesc, thanks for the input. Paul, I experienced this when the server images partition filled. It may not be your case but it's worth to check it out. Indeed that was my first thought too.  I have them backed by LVM so I did an lvmextend but it didn't seem to work until I created new DR

Re: [libvirt-users] connecting host and guest vm using a dummy nic

Greetings Laine, > Sent: Tuesday, May 01, 2018 at 5:30 PM > From: "Laine Stump" > To: libvirt-users@redhat.com > Cc: daggs > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/30/2018 03:16 PM, daggs wrote: > > Greetings Laine, > > > >> Sent: Monday, April 30,

Re: [libvirt-users] connecting host and guest vm using a dummy nic

On 04/30/2018 03:16 PM, daggs wrote: > Greetings Laine, > >> Sent: Monday, April 30, 2018 at 8:31 PM >> From: "Laine Stump" >> To: libvirt-users@redhat.com >> Cc: daggs >> Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic >> >> On 04/27/2018 06:39 PM, daggs wrote: >>> G

Re: [libvirt-users] Server 2016 locked in paused state

On Mon, Apr 30, 2018 at 05:46:14PM +0200, Francesc Guasch wrote: On 30/4/18 16:59, Paul O'Rorke wrote: Hi all, I have a number of production Windows servers on KVM/DRBD and two of them are Server 2016.  Both these guests have started exhibiting the same behaviour where they enter a paused state

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