On 06/07/2015 09:54, zhanghailiang wrote: > > From host, we found that QEMU vcpu1 thread and vcpu7 thread were not > consuming any cpu (Should be in idle state), > All of VCPUs' stacks in host is like bellow: > > [<ffffffffa07089b5>] kvm_vcpu_block+0x65/0xa0 [kvm] > [<ffffffffa071c7c1>] __vcpu_run+0xd1/0x260 [kvm] > [<ffffffffa071d508>] kvm_arch_vcpu_ioctl_run+0x68/0x1a0 [kvm] > [<ffffffffa0709cee>] kvm_vcpu_ioctl+0x38e/0x580 [kvm] > [<ffffffff8116be8b>] do_vfs_ioctl+0x8b/0x3b0 > [<ffffffff8116c251>] sys_ioctl+0xa1/0xb0 > [<ffffffff81468092>] system_call_fastpath+0x16/0x1b > [<00002ab9fe1f99a7>] 0x2ab9fe1f99a7 > [<ffffffffffffffff>] 0xffffffffffffffff > > We looked into the kernel codes that could leading to the above 'Stuck' > warning, > and found that the only possible is the emulation of 'cpuid' instruct in > kvm/qemu has something wrong. > But since we can’t reproduce this problem, we are not quite sure. > Is there any possible that the cupid emulation in kvm/qemu has some bug ? Can you explain the relationship to the cpuid emulation? What do the traces say about vcpus 1 and 7? Paolo -- 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
