On Mon, 2011-05-30 at 14:36 +0200, Ingo Molnar wrote:
> Right now i can produce something similar to it: 42 vcpus on a single
> CPU:
>
> $ taskse 1 kvm run --cpus 42
>
> And that hangs early on during bootup, around:
>
> [ 0.236000] Disabled fast string operations
> [ 0.242000] #4
> [ 0.270000] Disabled fast string operations
> [ 0.275000] #5
> [ 0.317000] Disabled fast string operations
> [ 0.322000] #6
> [ 0.352000] Disabled fast string operations
> [ 0.358000] #7
> [ 0.414000] Disabled fast string operations
>
> The threads seem to be livelocked:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 22227 mingo 20 0 471g 95m 904 R 12.9 0.8 0:06.39 kvm
> 22230 mingo 20 0 471g 95m 904 R 12.9 0.8 0:06.36 kvm
> 22226 mingo 20 0 471g 95m 904 R 11.9 0.8 0:07.04 kvm
> 22228 mingo 20 0 471g 95m 904 R 11.9 0.8 0:06.38 kvm
> 22229 mingo 20 0 471g 95m 904 R 11.9 0.8 0:06.37 kvm
> 22231 mingo 20 0 471g 95m 904 R 11.9 0.8 0:06.37 kvm
> 22232 mingo 20 0 471g 95m 904 R 11.9 0.8 0:06.36 kvm
> 22233 mingo 20 0 471g 95m 904 R 11.9 0.8 0:06.33 kvm
> 7 root -2 19 0 0 0 S 2.0 0.0 1:12.53 rcuc0
>
> with no apparent progress being made.
Since it's something that worked in 2.6.37, I've looked into it to find
what might have caused this issue.
I've bisected guest kernels and found that the problem starts with:
a26ac2455ffcf3be5c6ef92bc6df7182700f2114 is the first bad commit
commit a26ac2455ffcf3be5c6ef92bc6df7182700f2114
Author: Paul E. McKenney <paul.mckenney@xxxxxxxxxx>
Date: Wed Jan 12 14:10:23 2011 -0800
rcu: move TREE_RCU from softirq to kthread
Ingo, could you confirm that the problem goes away for you when you use
an earlier commit?
--
Sasha.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
