I know this comment doesn't help much -- but I want to add my $0.02.

We had a virtual machine host which went unresponsive on April 4th (10
days ago). All of the hosted virtual machines were behaving correctly.
Today while diagnosing the unresponsive virtual host I saw >3MB worth of
the error message the OP posted spammed in my /var/log/kern.log. That's
one symptom...
Early last March the same problem (unresponsive, no ssh, no virsh, etc)
was affecting the same virtual machine host. When we went to diagnose
the afflicted virtual machine host we discovered it's primary hard drive
(/dev/sda) had failed. Might just be a correlation.

I'm hope I'm not just adding static to the signal with these comments.

Here's some system specs: virtual machine host: Ubuntu Hardy Heron
(Customized system profile). 4 GB ram. Dual AMD Opteron 2216s.

r...@elep:~# uname -a
Linux elep 2.6.24-23-server #1 SMP Mon Jan 26 00:55:21 UTC 2009 i686 GNU/Linux

r...@elep:~# apt-cache policy kvm
kvm:
  Installed: 1:62+dfsg-0ubuntu8
  Candidate: 1:62+dfsg-0ubuntu8
  Version table:
 *** 1:62+dfsg-0ubuntu8 0
        500 http://mirror.lcsee.wvu.edu hardy-updates/main Packages
        100 /var/lib/dpkg/status
     1:62+dfsg-0ubuntu7 0
        500 http://mirror.lcsee.wvu.edu hardy/main Packages


And to be thorough: here's one of the thousands of Warnings:

Apr  4 06:55:01 elep kernel: [1360059.684667] WARNING: at 
/build/buildd/linux-2.6.24/arch/x86/kvm/mmu.c:378 account_shadowed()
Apr  4 06:55:01 elep kernel: [1360059.684671] Pid: 6427, comm: kvm Not tainted 
2.6.24-23-server #1
Apr  4 06:55:01 elep kernel: [1360059.684679]  [<f8aa570f>] 
kvm_mmu_get_page+0x2ef/0x440 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684703]  [<f8aa7f1e>] 
paging32_page_fault+0x3de/0x4b0 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684717]  [<f8aa806e>] 
do_insn_fetch+0x7e/0xc0 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684730]  [machine_kexec+0xf02/0x10c0] 
machine_kexec+0xf02/0x10c0
Apr  4 06:55:01 elep kernel: [1360059.684748]  [<f8aa0750>] 
emulate_instruction+0x1f0/0x2e0 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684764]  [<f8aa7073>] 
kvm_mmu_page_fault+0x13/0x90 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684780]  [<f8a85c69>] 
handle_exit+0x159/0x210 [kvm_amd]
Apr  4 06:55:01 elep kernel: [1360059.684786]  [<f8aacf4f>] 
apic_update_ppr+0x1f/0x50 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684800]  [<f8a85ff3>] 
svm_vcpu_run+0x1d3/0x290 [kvm_amd]
Apr  4 06:55:01 elep kernel: [1360059.684809]  [<f8aa32dd>] 
kvm_arch_vcpu_ioctl_run+0x13d/0x5e0 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684823]  [<f8a9ebfd>] 
kvm_vcpu_ioctl+0x34d/0x360 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684833]  [bridge:nf_hook_slow+0x98/0x100] 
nf_hook_slow+0x98/0xd0
Apr  4 06:55:01 elep kernel: [1360059.684844]  [enqueue_entity+0x2b/0x60] 
enqueue_entity+0x2b/0x60
Apr  4 06:55:01 elep kernel: [1360059.684849]  [enqueue_task_fair+0x27/0x30] 
enqueue_task_fair+0x27/0x30
Apr  4 06:55:01 elep kernel: [1360059.684853]  [enqueue_task+0x12/0x30] 
enqueue_task+0x12/0x30
Apr  4 06:55:01 elep kernel: [1360059.684860]  [try_to_wake_up+0x4e/0x350] 
try_to_wake_up+0x4e/0x350
Apr  4 06:55:01 elep kernel: [1360059.684863]  [enqueue_task_fair+0x27/0x30] 
enqueue_task_fair+0x27/0x30
Apr  4 06:55:01 elep kernel: [1360059.684872]  [core_sys_select+0x1e3/0x2d0] 
core_sys_select+0x1e3/0x2d0
Apr  4 06:55:01 elep kernel: [1360059.684883]  [dm_mod:__wake_up+0x3e/0x1f10] 
__wake_up+0x3e/0x60
Apr  4 06:55:01 elep kernel: [1360059.684890]  [wake_futex+0x3b/0x50] 
wake_futex+0x3b/0x50
Apr  4 06:55:01 elep kernel: [1360059.684898]  [__dequeue_signal+0x12/0x170] 
__dequeue_signal+0x12/0x170
Apr  4 06:55:01 elep kernel: [1360059.684905]  [recalc_sigpending+0xb/0x40] 
recalc_sigpending+0xb/0x40
Apr  4 06:55:01 elep kernel: [1360059.684909]  [read_hpet+0xa/0x10] 
read_hpet+0xa/0x10
Apr  4 06:55:01 elep kernel: [1360059.684912]  [getnstimeofday+0x34/0xf0] 
getnstimeofday+0x34/0xf0
Apr  4 06:55:01 elep kernel: [1360059.684919]  [enqueue_hrtimer+0x72/0x100] 
enqueue_hrtimer+0x72/0x100
Apr  4 06:55:01 elep kernel: [1360059.684927]  [hrtimer_start+0xc7/0x140] 
hrtimer_start+0xc7/0x140
Apr  4 06:55:01 elep kernel: [1360059.684936]  [<f8a9e8b0>] 
kvm_vcpu_ioctl+0x0/0x360 [kvm]
Apr  4 06:55:01 elep kernel: [1360059.684948]  [do_ioctl+0x2b/0x90] 
do_ioctl+0x2b/0x90
Apr  4 06:55:01 elep kernel: [1360059.684953]  [vfs_ioctl+0x22e/0x2b0] 
vfs_ioctl+0x22e/0x2b0
Apr  4 06:55:01 elep kernel: [1360059.684961]  [sys_ioctl+0x56/0x70] 
sys_ioctl+0x56/0x70
Apr  4 06:55:01 elep kernel: [1360059.684966]  [sysenter_past_esp+0x6b/0xa1] 
sysenter_past_esp+0x6b/0xa1

** Attachment added: "output from lsmod"
   http://launchpadlibrarian.net/25468152/mods

-- 
dmesg is flooded with warnings in kvm/mmu.c
https://bugs.launchpad.net/bugs/243393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to