On Fri, Mar 16, 2012 at 04:42:42PM -0500, Serge Hallyn wrote:
> On 03/16/2012 03:52 PM, Jim Paris wrote:
> >Serge Hallyn wrote:
> >>On 03/16/2012 11:50 AM, Eric Blake wrote:
> >>>On 03/16/2012 10:36 AM, Serge Hallyn wrote:
> Hi,
>
> It seems I've run into quite the heisenbug, reported
On 03/16/2012 03:52 PM, Jim Paris wrote:
Serge Hallyn wrote:
On 03/16/2012 11:50 AM, Eric Blake wrote:
On 03/16/2012 10:36 AM, Serge Hallyn wrote:
Hi,
It seems I've run into quite the heisenbug, reported at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/922628
It manifests itself as
Serge Hallyn wrote:
> On 03/16/2012 11:50 AM, Eric Blake wrote:
> >On 03/16/2012 10:36 AM, Serge Hallyn wrote:
> >>Hi,
> >>
> >>It seems I've run into quite the heisenbug, reported at
> >>https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/922628
> >>
> >>It manifests itself as virPidWait return
On 03/16/2012 11:50 AM, Eric Blake wrote:
On 03/16/2012 10:36 AM, Serge Hallyn wrote:
Hi,
It seems I've run into quite the heisenbug, reported at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/922628
It manifests itself as virPidWait returning status=4 for iptables (which
should never
On 03/16/2012 10:36 AM, Serge Hallyn wrote:
> Hi,
>
> It seems I've run into quite the heisenbug, reported at
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/922628
>
> It manifests itself as virPidWait returning status=4 for iptables (which
> should never exit with status=4).
Maybe ipt
Hi,
It seems I've run into quite the heisenbug, reported at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/922628
It manifests itself as virPidWait returning status=4 for iptables (which
should never exit with status=4). But it's only been seen on two (very
different) machines, and the s