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
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
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
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
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.
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
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
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
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