Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread david ahern
It appears to be a problem with the kernel proper (ie., not a Red Hat patch). I hit the soft lockup problem with kvm-48 and the 2.6.18.4 kernel which is the base for RHEL5. That suggests a delivery between 2.6.18.4 (November 2006) and 2.6.23.1 fixed it. david Avi Kivity wrote: > david ahern w

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread Avi Kivity
david ahern wrote: > The issue appears to be with the RHEL5 kernel (host OS is rhel5). I tried > your suggestions below -- no effect; still hit the softlockup. > > I then moved the host to the 2.6.23.1 kernel but with the kvm-48 code base. > Surprisingly, I had no issues starting my guest with '-

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread david ahern
The issue appears to be with the RHEL5 kernel (host OS is rhel5). I tried your suggestions below -- no effect; still hit the softlockup. I then moved the host to the 2.6.23.1 kernel but with the kvm-48 code base. Surprisingly, I had no issues starting my guest with '-smp 4'. david Avi Kivity

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread david ahern
I'll give your suggestions I try. I need to move to a server that I can forcibly reboot remotely (to recover), so it will be a while. david Avi Kivity wrote: > david ahern wrote: >> As a quick test I added a printk to the loop, right after the while(): >> >> while (atomic_read(&completed)

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread Avi Kivity
david ahern wrote: > As a quick test I added a printk to the loop, right after the while(): > > while (atomic_read(&completed) != needed) { > printk("kvm_flush_remote_tlbs: completed = %d, needed = %d\n", > atomic_read(&completed), needed); > cpu_relax(); > barrier(

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-25 Thread david ahern
As a quick test I added a printk to the loop, right after the while(): while (atomic_read(&completed) != needed) { printk("kvm_flush_remote_tlbs: completed = %d, needed = %d\n", atomic_read(&completed), needed); cpu_relax(); barrier(); } This is the output r

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-24 Thread Avi Kivity
david ahern wrote: > I am trying, unsuccessfully so far, to get a vm running with 4 cpus. It is > failing with a soft lockup: > > BUG: soft lockup detected on CPU#3! > [] softlockup_tick+0x98/0xa6 > [] update_process_times+0x39/0x5c > [] smp_apic_timer_interrupt+0x5c/0x64 > [] apic_timer_inter

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-24 Thread david ahern
I saw that in the latest git tree, but RHEL5 kernel does not have that function. I guess I'll have to evaluate my options -- upgrading kernels, or backporting code. thanks, david Laurent Vivier wrote: > david ahern a écrit : >> I am trying, unsuccessfully so far, to get a vm running with 4 cp

Re: [kvm-devel] soft lockup in kvm_flush_remote_tlbs

2007-10-24 Thread Laurent Vivier
david ahern a écrit : > I am trying, unsuccessfully so far, to get a vm running with 4 cpus. It is > failing with a soft lockup: > > BUG: soft lockup detected on CPU#3! > [] softlockup_tick+0x98/0xa6 > [] update_process_times+0x39/0x5c > [] smp_apic_timer_interrupt+0x5c/0x64 > [] apic_timer_i