thesword53

> > > What is the hypervisor used in AMD Ryzen Win10 Pro? gvm > > > AND for the Intel case, how can you run gvm on Intel with...

Windows 7 and Windows 10 don't work with SeaBIOS. I have to use OVMF UEFI. Your GVM hypervisor works better than WHPX on qemu, because I am not able to...

> Any special operations that can triggered the BSOD? Boot Windows 7 VM and trigger BSOD on guest (kill csrss.exe process for example). Your host will also get a BSOD.

Here is the crashdump: [https://drive.google.com/file/d/1Rrh4qH_-ki1PGLU-DVvajkUsNADPN4OA/view?usp=sharing](https://drive.google.com/file/d/1Rrh4qH_-ki1PGLU-DVvajkUsNADPN4OA/view?usp=sharing) > > > The host is not impacted. It is weird that the BSOD screen does not show inside the guest so it will look...

I share the memory dump (~700MB) [https://drive.google.com/file/d/1qTHQy2uQyN1KzqbJ4rutel9R8m8N9uzK/view?usp=sharing](https://drive.google.com/file/d/1qTHQy2uQyN1KzqbJ4rutel9R8m8N9uzK/view?usp=sharing). I found the stack trace with WinDBG but I don't have symbol names of gvm STACK_TEXT: fffff880`052d9520 fffff880`03b035da : fffffa80`080f5000 00000000`00000003 00000000`00000000 fffffa80`07d14aa0...

It seems to be caused by this instruction: https://github.com/google/android-emulator-hypervisor-driver-for-amd-processors/blob/c772caab541d0a7ede442f32c04b0c95aacba512/arch/x86/kvm/mmu.c#L2097

> https://1drv.ms/u/s!AljlID0ntVyugehxayBpYN3uOnXidw?e=ZQ1cuo > Can you try this build and see if it fixes the problem? I can't boot Windows 7 guest at all with this build. The "Starting Windows" shows...

> https://1drv.ms/u/s!AljlID0ntVyugehyHXoKYGgtriDJrA?e=1lAXXh > Can you try this one? This build is exactly v1.5 + intended fix, removing any other irrelevant patches from the former build. I have the same issue...

> I've tried to install and run a Windows 7 64 guest successfully with both builds. The commandline options are "-accel gvm -cpu host -m 8G -smp cores=8 -hda=win7.file -sdl"....

> I also used OVMF UEFI bios. So OVMF UEFI with Windows 7 can work with gvm v1.5, but cannot work with the two builds I sent. Right? Yes