On Sat, Nov 20, 2021 at 06:10:58PM -0500, Dave Voutila wrote: > To me the below is the fix to the actual issue: not properly sending > guest state back to vmd so it can provide the correct state (updated or > not) when re-running the vcpu. I'm going to share with tech@ with pretty > much the same writeup to see if others can test it out. > > The yield() thing I previously shared is an area I'm working on > separately.
I've replaced your old patch with this new one. I also have Philip's patch still in place. Everything is operating for me correctly. Latest VMM_DEBUG log: vm_impl_init_vmx: created vm_map @ 0xfffffd81b901d890 vm_resetcpu: resetting vm 1 vcpu 0 to power on defaults Guest EPTP = 0x1db94301e vmm_alloc_vpid: allocated VPID/ASID 1 vmm_handle_cpuid: function 0x0a (arch. perf mon) not supported vmx_handle_cr: mov to cr0 @ 100149e, data=0x80010031 vmx_handle_wrmsr: wrmsr exit, msr=0x8b, discarding data written from guest=0x0:0x0 vmx_handle_wrmsr: wrmsr exit, msr=0x8b, discarding data written from guest=0x0:0x0 vmm_handle_cpuid: unsupported rax=0x40000100 vmm_handle_cpuid: function 0x06 (thermal/power mgt) not supported vmm_handle_cpuid: function 0x0a (arch. perf mon) not supported
