search for: alitk

...half way through the VM’s when removing the snapshots so we have a good chance that it comes up again. Also the libvirt logs to the journal not to libvirtd.log, i would send the journal directly to you and Eric via our data exchange servers Soeren On 04/06/15 16:17, "Adam Litke" <alitke@redhat.com> wrote: >On 04/06/15 13:08 +0000, Soeren Malchow wrote: >>Hi Adam, Hi Eric, >> >>We had this issue again a few minutes ago. >> >>One machine went down exactly the same way as described, the machine had >>only one snapshot and it was the only sn...

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> Hi all! >> >> We're debating the design of the balloon for the OASIS spec. >> Noone likes the current one, but there are fundamental usage pattern >> questions whi...

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> Hi all! >> >> We're debating the design of the balloon for the OASIS spec. >> Noone likes the current one, but there are fundamental usage pattern >> questions whi...

...ne") > api.disconnect() >except Exception as e: > print ("Something went wrong when deleting the snapshots\n%s") % >str(e) > > > ><― snip ―> > > >Cheers >Soeren > > > > > >On 03/06/15 15:20, "Adam Litke" <alitke@redhat.com> wrote: > >>On 03/06/15 07:36 +0000, Soeren Malchow wrote: >>>Dear Adam >>> >>>First we were using a python script that was working on 4 threads and >>>therefore removing 4 snapshots at the time throughout the cluster, that >>>sti...

...ving the snapshots so we have a good chance that it comes up >again. > >Also the libvirt logs to the journal not to libvirtd.log, i would send the >journal directly to you and Eric via our data exchange servers > > >Soeren > >On 04/06/15 16:17, "Adam Litke" <alitke@redhat.com> wrote: > >>On 04/06/15 13:08 +0000, Soeren Malchow wrote: >>>Hi Adam, Hi Eric, >>> >>>We had this issue again a few minutes ago. >>> >>>One machine went down exactly the same way as described, the machine had >>>only one...

On 03/06/15 07:36 +0000, Soeren Malchow wrote: >Dear Adam > >First we were using a python script that was working on 4 threads and >therefore removing 4 snapshots at the time throughout the cluster, that >still caused problems. > >Now i took the snapshot removing out of the threaded part an i am just >looping through each snapshot on each VM one after another, even with

...n for %s done") % vm.name print ("Deletion of snapshots done") api.disconnect() except Exception as e: print ("Something went wrong when deleting the snapshots\n%s") % str(e) <― snip ―> Cheers Soeren On 03/06/15 15:20, "Adam Litke" <alitke@redhat.com> wrote: >On 03/06/15 07:36 +0000, Soeren Malchow wrote: >>Dear Adam >> >>First we were using a python script that was working on 4 threads and >>therefore removing 4 snapshots at the time throughout the cluster, that >>still caused problems. >>...

On 20/02/14 14:53 +1030, Rusty Russell wrote: >Adam Litke <alitke at redhat.com> writes: >>> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >>> Hi all! >>> >>> We're debating the design of the balloon for the OASIS spec. >>> Noone likes the current one, but there are fundamental usage pattern &gt...

...gt;> print ("Something went wrong when deleting the snapshots\n%s") % >>str(e) >> >> >> >><― snip ―> >> >> >>Cheers >>Soeren >> >> >> >> >> >>On 03/06/15 15:20, "Adam Litke" <alitke@redhat.com> wrote: >> >>>On 03/06/15 07:36 +0000, Soeren Malchow wrote: >>>>Dear Adam >>>> >>>>First we were using a python script that was working on 4 threads and >>>>therefore removing 4 snapshots at the time throughout the clust...

...ber of VMS because we had this on hosts with only 3 or 4 Vms running I will try restarting the libvirt and see what happens. We are not using RHEL 7.1 only CentOS 7.1 Is there anything else we can look at when this happens again ? Regards Soeren On 02/06/15 18:53, "Adam Litke" <alitke@redhat.com> wrote: >Hello Soeren. > >I've started to look at this issue and I'd agree that at first glance >it looks like a libvirt issue. The 'cannot acquire state change lock' >messages suggest a locking bug or severe contention at least. To help >me bette...

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

Hello Soeren. I've started to look at this issue and I'd agree that at first glance it looks like a libvirt issue. The 'cannot acquire state change lock' messages suggest a locking bug or severe contention at least. To help me better understand the problem I have a few questions about your setup. >From your earlier report it appears that you have 15 VMs running on the

> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: > Hi all! > > We're debating the design of the balloon for the OASIS spec. > Noone likes the current one, but there are fundamental usage pattern > questions which we're fumbling with. > > So if you know anyone who is using it in production? If, so, how? In > particular, would you be happy with