From: Hang Yuan
Add ROM and ROM device memory region support in HAX. Their memory region is
read only and write access will generate EPT violation. The violation will be
handled in the HAX kernel with the following patch.
https://github.com/intel/haxm/commit
In summary, sounds all non-register guest states in VMCS structure are
not saved in snapshot. I don't understand why they don't need to save in
snapshot and load from snapshot to construct VMCS. Does anyone have any
idea?
Thanks,
Henry
On 7/30/19 5:05 PM, Hang Yuan wrote:
Hello al
Hello all,
When I read QEMU and KVM codes on saving/loading snapshot, I don't find
the interruptibility state in x86 VMCS structure is saved and loaded in
QEMU though KVM supports getting/setting this field from/into VMCS. (No
"env.interrupt.shadow" in QEMU vmstate_x86_cpu.fields.) I understan
From: Hang Yuan
Add ROM and ROM device memory region support in HAX. Their memory region is
read only and write access will generate EPT violation. The violation will be
handled in the HAX kernel with the following patch.
https://github.com/intel/haxm/commit
From: Hang Yuan
Add ROM and ROM device memory region support in HAX. Their memory region is
read only and write access will generate EPT violation. The violation will
be handled in the HAX kernel with the following patch.
https://github.com/intel/haxm/commit
