On Wed, Apr 12, 2017 at 09:11:12PM +0200, Jean Baptiste Guerraz wrote: > Hello, > > We're facing an issue with a Windows guest VM which runs quite well on > a laptop (Fedora 25 - Core I7 4720HQ - > https://www.asus.com/Notebooks/N551JX/specifications/ ) but not on 2 > different servers (one Debian 8 on > https://documentation.online.net/en/dedicated-server/offers/2015/server-dedibox-pro-2015-gen2#server_dedibox_pro_2015_gen2 > - and one Fedora 25 on > https://documentation.online.net/en/dedicated-server/offers/2016/server-dedibox-md-2016#server_dedibox_md_2016) > with the same symptom : Windows get stuck with CPU at 100% (from > services.exe process) a few "minute" after desktop is shown. > > Detailed informations (record / strace / qemu command / packages > versions...) available here : > https://gist.github.com/jbguerraz/faef292b48b2d0106d8d96ba0ddd943c > > Record tool shows a loop on such pattern (more on the linked gist) : > > qemu-system-x86 7420 [000] 28829.151596: kvm:kvm_exit: reason > EPT_MISCONFIG rip 0xfffff80001df7eea info 0 0 > qemu-system-x86 7420 [000] 28829.151596: kvm:kvm_emulate_insn: > 0:fffff80001df7eea: 44 8b 80 f0 00 00 00 > qemu-system-x86 7420 [000] 28829.151597: kvm:vcpu_match_mmio: gva > 0xffffffffffd090f0 gpa 0xfed000f0 Read GPA > qemu-system-x86 7420 [000] 28829.151597: kvm:kvm_mmio: mmio > unsatisfied-read len 4 gpa 0xfed000f0 val 0x0 > qemu-system-x86 7420 [000] 28829.151597: kvm:kvm_userspace_exit: > reason KVM_EXIT_MMIO (6) > qemu-system-x86 7420 [000] 28829.151598: kvm:kvm_fpu: unload > qemu-system-x86 7420 [000] 28829.151599: kvm:kvm_mmio: mmio read len > 4 gpa 0xfed000f0 val 0x5e3c5955 This is the physical address range of the HPET (timer). > qemu-system-x86 7420 [000] 28829.151600: kvm:kvm_fpu: load > qemu-system-x86 7420 [000] 28829.151600: kvm:kvm_entry: vcpu 0 > qemu-system-x86 7420 [000] 28829.151607: kvm:kvm_exit: reason > EPT_MISCONFIG rip 0xfffff80001df7eea info 0 0 > qemu-system-x86 7420 [000] 28829.151608: kvm:kvm_emulate_insn: > 0:fffff80001df7eea: 44 8b 80 f0 00 00 00 > qemu-system-x86 7420 [000] 28829.151609: kvm:vcpu_match_mmio: gva > 0xffffffffffd090f0 gpa 0xfed000f0 Read GPA > qemu-system-x86 7420 [000] 28829.151609: kvm:kvm_mmio: mmio > unsatisfied-read len 4 gpa 0xfed000f0 val 0x0 > qemu-system-x86 7420 [000] 28829.151609: kvm:kvm_userspace_exit: > reason KVM_EXIT_MMIO (6) > qemu-system-x86 7420 [000] 28829.151610: kvm:kvm_fpu: unload > qemu-system-x86 7420 [000] 28829.151611: kvm:kvm_mmio: mmio read len > 4 gpa 0xfed000f0 val 0x5e3c5e0d HPET access again. > qemu-system-x86 7420 [000] 28829.151612: kvm:kvm_fpu: load > qemu-system-x86 7420 [000] 28829.151612: kvm:kvm_entry: vcpu 0 > qemu-system-x86 7420 [000] 28829.151615: kvm:kvm_exit: reason > EPT_MISCONFIG rip 0xfffff80001df7eea info 0 0 > qemu-system-x86 7420 [000] 28829.151616: kvm:kvm_emulate_insn: > 0:fffff80001df7eea: 44 8b 80 f0 00 00 00 > qemu-system-x86 7420 [000] 28829.151616: kvm:vcpu_match_mmio: gva > 0xffffffffffd090f0 gpa 0xfed000f0 Read GPA > qemu-system-x86 7420 [000] 28829.151617: kvm:kvm_mmio: mmio > unsatisfied-read len 4 gpa 0xfed000f0 val 0x0 Here too. > qemu-system-x86 7420 [000] 28829.151617: kvm:kvm_userspace_exit: > reason KVM_EXIT_MMIO (6) > qemu-system-x86 7420 [000] 28829.151617: kvm:kvm_fpu: unload > qemu-system-x86 7420 [000] 28829.151618: kvm:kvm_mmio: mmio read len > 4 gpa 0xfed000f0 val 0x5e3c60f5 > qemu-system-x86 7420 [000] 28829.151619: kvm:kvm_fpu: load > qemu-system-x86 7420 [000] 28829.151619: kvm:kvm_entry: vcpu 0 > > If one of you have an idea about how to dig further, that would be super :) I looked at a few of the interrupts that were injected. An interrupt is interrupt delivered every 15 milliseconds. They were immediately acknowledged by the interrupt handler function inside the guest. This just looks like a running guest that's doing no I/O to me. Can anyone else spot something suspicious that indicates 100% guest CPU consumption? Stefan
Attachment:
signature.asc
Description: PGP signature
