Bug#570382: more datapoints on vserver start failure

[Dan Gardner <dan@chaotica.org.uk>]

On Thu, Mar 11, 2010 at 10:17:40PM +0100, Tomas Pospisek wrote:
> So once again I had to upgrade kernels and I noticed:
> 
> * that only my -686 kernel based machines failed to start the vservers
>   (guests) correctly. The amd64 machine started them without problems. I
>   see that Florian.Dufour@inria.fr also has an 686 machine. I'm Cc:ing Dan
>   to see whether that's also the case for him.

Yes, also the case for me. I haven't tried an amd64 vserver kernel.

> * on one of the machines the *first* of the vserver actually did start
>   all others not and on the other machine all vservers did not start
>   correctly. So it's not either all vservers fail to start or none. Might
>   a ressource pressure problem?

I found the same thing - it wasn't reproducible 100% of the time.

> * stopping and starting the vservers one after the other "fixed" the
>   problem, the vservers started correctly

Again, my findings were similar. The problem only seemed to exhibit
itself using "/etc/init.d/vserver start" - starting vservers with
"vserver foo start" would always work.

-dan