----- On Mar 13, 2017, at 6:15 PM, Dan McDonald [email protected] wrote:
[...]
> Tobias:  Try this:
> 
>       dtrace -n 'gfn_to_memslot_unaliased:entry { printf("\nKVM 0x%p, number 
> of
>       memslots: %d\n", arg0, ((struct kvm_memslots *)((struct kvm
>       *)arg0)->memslots)->nmemslots); stack(); exit(0);}'
> 
> If your system is still running the same KVM instances, check for
> 0xfffffea4320ef000 as the KVM pointer.


when run repeatedly I mostly get

CPU     ID                    FUNCTION:NAME
  0  72630   gfn_to_memslot_unaliased:entry 
KVM 0xfffffea38c8e3000, number of memslots: 35

              kvm`gfn_to_hva+0x27
              kvm`kvm_read_guest_page+0x29
              kvm`kvm_read_guest+0x43
              kvm`paging64_walk_addr+0xef
              kvm`paging64_gva_to_gpa+0x43
              kvm`kvm_read_guest_virt_helper+0x3e
              kvm`kvm_fetch_guest_virt+0x62
              kvm`do_fetch_insn_byte+0x70
              kvm`do_insn_fetch+0x5e
              kvm`x86_decode_insn+0x102
              kvm`emulate_instruction+0xce
              kvm`handle_apic_access+0x38
              kvm`vmx_handle_exit+0x16a
              kvm`vcpu_enter_guest+0x3ea
              kvm`__vcpu_run+0x8b
              kvm`kvm_arch_vcpu_ioctl_run+0x112
              kvm`kvm_ioctl+0x466
              genunix`cdev_ioctl+0x39
              specfs`spec_ioctl+0x60
              genunix`fop_ioctl+0x55


sometimes I also get

CPU     ID                    FUNCTION:NAME
 27  72630   gfn_to_memslot_unaliased:entry 
KVM 0xfffffea38c8e3000, number of memslots: 35

              kvm`gfn_to_memslot+0x1c
              kvm`mapping_level+0x29
              kvm`tdp_page_fault+0x89
              kvm`kvm_mmu_page_fault+0x2c
              kvm`handle_ept_violation+0x111
              kvm`vmx_handle_exit+0x16a
              kvm`vcpu_enter_guest+0x3ea
              kvm`__vcpu_run+0x8b
              kvm`kvm_arch_vcpu_ioctl_run+0x112
              kvm`kvm_ioctl+0x466
              genunix`cdev_ioctl+0x39
              specfs`spec_ioctl+0x60
              genunix`fop_ioctl+0x55
              genunix`ioctl+0x9b
              unix`sys_syscall+0x196

On a further note, about an hour ago most users have stopped using that 
omnios-kvm instance
for interactive work as the hangs were getting too disruptive (before the vm 
was running
5 xvnc servers with chrome and all the trimmings)

when I now run my 'testscript' on the machine, the long waits do not occur 
anymore ... 
which would indicate that the problem is somehow related to the load on the vm 
... 


chers
tobi

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch [email protected] +41 62 775 9902


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to