Ubuntu
linux package

  1. Precise (12.04)
  2. Bug #1021471
  3. Comment #4

Comment 4 for bug 1021471

Revision history for this message
Bryan Wu (cooloney) wrote : Re: stuck on mutex_lock creating a new network namespace when starting a container

hmmm, that's very hard for us to analyze. We did meet a similar oops before because of the heavy workload and CFQ block IO scheduler. Could you a test for us? change your default Block IO scheduler from CFQ to deadline and run LXC as usual to verify this issue is gone. I'm just guess and hope this can do some help.

-Bryan