Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-14 Thread Yaniv Kaul
On Wed, Jan 13, 2016 at 2:28 PM, Justin Clift wrote: > On 2016-01-13 10:18, Richard W.M. Jones wrote: > > >> I would be good if libvirt could routinely test the case of multiple >> parallel launches of qemu:///session, since it still contains bugs >> even after Cole's

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-14 Thread Richard W.M. Jones
On Wed, Jan 13, 2016 at 03:50:47PM +, Richard W.M. Jones wrote: > On Wed, Jan 13, 2016 at 04:25:14PM +0100, Martin Kletzander wrote: > > For each of the kernels, libvirt labels them (with both DAC and selinux > > labels), then proceeds to launching qemu. If this is done parallel, the > > race

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-14 Thread Jiri Denemark
On Wed, Jan 13, 2016 at 16:25:14 +0100, Martin Kletzander wrote: > On Wed, Jan 13, 2016 at 10:18:42AM +, Richard W.M. Jones wrote: > >As people may know, we frequently encounter errors caused by libvirt > >when running the libguestfs appliance. > > > >I wanted to find out exactly how

[libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Richard W.M. Jones
As people may know, we frequently encounter errors caused by libvirt when running the libguestfs appliance. I wanted to find out exactly how frequently these happen and classify the errors, so I ran the 'virt-df' tool overnight 1700 times. This tool runs several parallel qemu:///session libvirt

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Justin Clift
On 2016-01-13 10:18, Richard W.M. Jones wrote: I would be good if libvirt could routinely test the case of multiple parallel launches of qemu:///session, since it still contains bugs even after Cole's fixes. Sounds like this testing script would be useful as a (weekly?) cronjob or similar.

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Cole Robinson
On 01/13/2016 05:18 AM, Richard W.M. Jones wrote: > As people may know, we frequently encounter errors caused by libvirt > when running the libguestfs appliance. > > I wanted to find out exactly how frequently these happen and classify > the errors, so I ran the 'virt-df' tool overnight 1700

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Cole Robinson
On 01/13/2016 06:45 PM, Cole Robinson wrote: > On 01/13/2016 05:18 AM, Richard W.M. Jones wrote: >> As people may know, we frequently encounter errors caused by libvirt >> when running the libguestfs appliance. >> >> I wanted to find out exactly how frequently these happen and classify >> the

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Richard W.M. Jones
On Wed, Jan 13, 2016 at 04:25:14PM +0100, Martin Kletzander wrote: > For each of the kernels, libvirt labels them (with both DAC and selinux > labels), then proceeds to launching qemu. If this is done parallel, the > race is pretty obvious. Could you remind me why you couldn't use > or or

Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

2016-01-13 Thread Martin Kletzander
On Wed, Jan 13, 2016 at 10:18:42AM +, Richard W.M. Jones wrote: As people may know, we frequently encounter errors caused by libvirt when running the libguestfs appliance. I wanted to find out exactly how frequently these happen and classify the errors, so I ran the 'virt-df' tool overnight