On 12/17/2010 05:24 PM, Avi Kivity wrote:
On 12/17/2010 12:14 AM, Lok Kwong Yan wrote:
Thanks for the reply and it makes a lot of sense.
I am not seeing any EPT tables being zapped after the guest has fully
started up although the value of EPTP continuously changes as the
guest is running.
Really strange, this is likely a bug.
I tried to reproduce, the only times I see eptp changes are when the
guest reprograms the vga adapter:
qemu-system-x86-20944 [033] 1327.151819: kvm_pio:
pio_write at 0x3ce size 2 count 1
qemu-system-x86-20944 [033] 1327.151819: kvm_userspace_exit: reason
KVM_EXIT_IO (2)
qemu-system-x86-20944 [033] 1327.152405: kvm_mmu_prepare_zap_page:
[FAILED TO PARSE] gfn=237568 role=122881 root_count=0 unsync=0
...
qemu-system-x86-20944 [033] 1327.153230: kvm_mmu_prepare_zap_page:
[FAILED TO PARSE] gfn=0 role=253956 root_count=2 unsync=0
qemu-system-x86-20944 [033] 1327.153339: kvm_mmu_get_page: sp gfn
0 0/4 q0 direct --- !pge !nxe root 0sync
qemu-system-x86-20944 [033] 1327.153344: print:
a0265cde vmx_set_cr3: eptp fef14101
Under what scenario do you see eptp changing?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
