hi,
I have Linux hangs since kvm-77, the guest is not reachable by any means and do
not react to sysrq keys. On the host the process is using 100% CPU.
Marcelot told me to try oos_shadow=off, after 2 days, now I have a Linux guest
which behave very strange.
- uses 100+% CPU on the host
23638 root 20 0 465m 391m 1032 S 104 6.5 136:49.91 kvm -name
builder -vnc 192.168.0.254:2 -smp 2 -m 384 -d
- load avg does not change:
12:21:18 up 2 days, 13:20, 1 user, load average: 0.53, 2.49, 3.10
12:21:18 up 2 days, 13:25, 1 user, load average: 0.53, 2.49, 3.10
- some command can not be executed
top does not work, strace top output:
open("/proc/12490/statm", O_RDONLY) = 4
read(4, "557 250 193 12 0 85 0\n"..., 1023) = 22
close(4) = 0
stat64("/proc/18149", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
open("/proc/18149/stat", O_RDONLY) = 4
read(4, "18149 (smbd) S 4383 4383 4383 0 -"..., 1023) = 197
close(4) = 0
open("/proc/18149/statm", O_RDONLY) = 4
read(4, "1829 630 503 867 0 350 0\n"..., 1023) = 25
close(4) = 0
stat64("/proc/19957", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
open("/proc/19957/stat", O_RDONLY) = 4
read(4, "19957 (smbd) S 4383 4383 4383 0 -"..., 1023) = 193
close(4) = 0
open("/proc/19957/statm", O_RDONLY) = 4
read(4, "1827 438 331 867 0 350 0\n"..., 1023) = 25
close(4) = 0
getdents(3, /* 0 entries */, 1024) = 0
close(3) = 0
select(0, NULL, NULL, NULL, {0, 500000}
- crazy context switching in the guest
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 65184 173604 16280 106052 0 0 12 3 27 19 0 1 99 0
0 0 65184 173604 16280 106052 0 0 0 0 1008 371774 0 0 100 0
1 0 65184 173604 16280 106052 0 0 0 0 1010 371734 0 0 100 0
0 0 65184 173604 16280 106052 0 0 0 0 1010 372163 0 0 100 0
0 0 65184 173604 16280 106052 0 0 0 0 1011 371414 0 0 100 0
1 0 65184 173604 16280 106052 0 0 0 0 1001 371930 0 0 100 0
1 0 65184 173604 16280 106052 0 0 0 0 994 370698 0 0 100 0
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
