> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Wednesday, February 03, 2016 5:35 PM > > (XEN) nvmx_handle_vmwrite: 0 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 0 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 0 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 2008 > > (XEN) nvmx_handle_vmwrite: 800 > > (XEN) nvmx_handle_vmwrite: 804 > > (XEN) nvmx_handle_vmwrite: 806 > > (XEN) nvmx_handle_vmwrite: 80a > > (XEN) nvmx_handle_vmwrite: 80e > > (XEN) nvmx_update_virtual_apic_address: vCPU1 0xffffffffffffffff(vAPIC) > > 0x0(APIC), > 0x0(TPR) ctrl=b5b9effe sec=0 > > Assuming the field starts out as other than all ones, could you check > its value on each of the intercepted VMWRITEs, to at least narrow > when it changes. > > Kevin, Jun - are there any cases where the hardware would alter > this field's value? Like during some guest side LAPIC manipulations? > (The same monitoring as suggested during VMWRITEs could of > course also be added to LAPIC accesses visible to the hypervisor, > but I guess there won't be too many of those.) >
No such case in my knowledge. But let me confirm with hardware team. Thanks Kevin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
