On 12/11/2016 01:20 AM, Peter Grehan wrote:
 Looks like a possibly lost interrupt.

 Can you check to see if this system is using APIC virtualization ?

# sysctl -a hw.vmm.vmx.cap
...
hw.vmm.vmx.cap.posted_interrupts: 1
hw.vmm.vmx.cap.virtual_interrupt_delivery: 1

(these will be zero if APIC virtualization not in use)

If so, one thing to try is disabling these and see if that helps. This can be done by setting the tunable hw.vmm.vmx.use_apic_vid to 1 (e.g. in /boot/loader.conf, or unloading vmm.ko, setting the value with kenv, and the reloading vmm.ko)

later,

Peter.


I don't seem to have that sysctl on my system. Should i create one?

# sysctl -a |grep vmm
kern.proc_vmmap_skip_resident_count: 0
kern.coredump_pack_vmmapinfo: 1
hw.vmm.npt.pmap_flags: 0
hw.vmm.svm.num_asids: 0
hw.vmm.svm.disable_npf_assist: 0
hw.vmm.svm.features: 4294967295
hw.vmm.svm.vmcb_clean: 959
hw.vmm.vmx.vpid_alloc_failed: 0
hw.vmm.vmx.posted_interrupt_vector: 252
hw.vmm.vmx.cap.posted_interrupts: 1
hw.vmm.vmx.cap.virtual_interrupt_delivery: 1
hw.vmm.vmx.cap.invpcid: 1
hw.vmm.vmx.cap.monitor_trap: 1
hw.vmm.vmx.cap.unrestricted_guest: 1
hw.vmm.vmx.cap.pause_exit: 1
hw.vmm.vmx.cap.halt_exit: 1
hw.vmm.vmx.initialized: 1
hw.vmm.vmx.cr4_zeros_mask: 18446744073705920512
hw.vmm.vmx.cr4_ones_mask: 8192
hw.vmm.vmx.cr0_zeros_mask: 18446744071025197056
hw.vmm.vmx.cr0_ones_mask: 32
hw.vmm.ept.pmap_flags: 1531
hw.vmm.vrtc.flag_broken_time: 1
hw.vmm.ppt.devices: 2
hw.vmm.iommu.initialized: 1
hw.vmm.bhyve_xcpuids: 72
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.topology.cores_per_package: 1
hw.vmm.topology.threads_per_core: 1
hw.vmm.create: beavis
hw.vmm.destroy: beavis
hw.vmm.force_iommu: 0
hw.vmm.trace_guest_exceptions: 0
hw.vmm.ipinum: 251
hw.vmm.halt_detection: 1


Thanks,
Rajil
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to