-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BSOD SYSTEM_SERVICE_EXCEPTION gvm.sys with qemu #14
Comments
What is the hypervisor used in AMD Ryzen Win10 Pro? |
AND for the Intel case, how can you run gvm on Intel with Android Emulator? |
gvm
I didn't use Android Emulator, I used qemu with gvm acceleration: https://github.com/qemu-gvm/qemu-gvm #5 (qemu-system-x86_64 -accel gvm ...) with Windows 7 as guest. |
OK. I just realized that you are not using Android Emulator. |
Windows 7 and Windows 10 don't work with SeaBIOS. I have to use OVMF UEFI. |
Thanks for the tips. I tried UEFI and now I could install Win7 and Win10. Your information helped me a lot. Here is my result. |
Boot Windows 7 VM and trigger BSOD on guest (kill csrss.exe process for example). Your host will also get a BSOD. |
I tried but I could not reproduce. When I triggered a crash using NotMyFault from sysinternals, the guest got a crashdump and rebooted. The host is not impacted. It is weird that the BSOD screen does not show inside the guest so it will look like a hang. |
Here is the crashdump: https://drive.google.com/file/d/1Rrh4qH_-ki1PGLU-DVvajkUsNADPN4OA/view?usp=sharing
You need to wait a bit and the host will crash. |
Thanks for the crash dump. It does look like a "use-after-free" issue. I will come back when I find out the reason. |
I share the memory dump (~700MB) 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: |
Symbols for 1.5 can be downloaded here. FYI. |
I think #23 is probably the same issue, although I have not get that dump yet. |
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 |
I can't boot Windows 7 guest at all with this build. The "Starting Windows" shows up and the screen become black. |
OK. I will do another build for you, will be back later. |
https://1drv.ms/u/s!AljlID0ntVyugehyHXoKYGgtriDJrA?e=1lAXXh |
I have the same issue with this build. The guest seems to get a BSOD but the screen is black. |
Thanks. It is hard to guess the reason as this is actually one line change, which should not alter guest behavior. |
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". |
This issue only happened if I use OVMF UEFI with Windows 7. |
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 |
I tested GVM 1.6 and I can't boot any Windows OS.
With gvm 1.5 I was able to start Windows 7 (OVMF only) and Windows 10 I will look for Linux guests. |
I tested Linux (Ubuntu 16.04 and Ubuntu 19.10) and it works but I have lots of hardware errors (machine check exception) on guest. |
On your Intel or AMD, btw? |
Intel |
Perhaps I should find something a similar CPU and do a test. Are you still using nested virtualization with Arch Linux? |
Yes I am using nested virtualization with an Intel Core i7-4810MQ (Haswell). I can't test gvm with my AMD computer now because I'm not at home. |
I tested GVM 1.6 on AMD and it works. On Intel with OVMF, I get a BSOD on guest (system_thread_exception_not_handled) with Windows 7/8/10. I think it's related to 4edc540. |
I feel the same too, as the change may surprise the KVM. It is hard to tell whether this exposes a KVM bug as it does work natively on my Intel. But right now, I am too busy to work on this. |
I tried to compile GVM, and the Intel issue seems to be caused by c2693c9 |
If that's the case, I can safely revert the change in the next release.
Thanks!
Together with a fix for Windows insider build, I can release 1.7 very
quickly.
…On Fri, Sep 18, 2020 at 1:41 AM thesword53 ***@***.***> wrote:
I tried to compile GVM, and the Intel issue seems to be caused by c2693c9
<c2693c9>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2MOAN4HT7J2KOY5Q3C5JLSGMMLBANCNFSM4NS4QCBQ>
.
--
Haitao @google
|
This seems to break nested run on top of KVM. See #14 This reverts commit defbb8dbb2797ef76177ea5a188249225a0e8021.
Hi, 1.7 is released and c2693c9 is reverted. |
Hi Taogle2018, I was wrong. c2693c9 didn't solve the issue. I also tested an Arch Linux VM and i got kernel panic "MCA architectural violation!" I also tested GVM in a host Intel PC and Windows 7/10 and Arch Linux boot as guest. |
Host system gets BSOD when guest (Windows 7) also gets BSOD or during boot.
Systems tested:
cpu: AMD Ryzen 7 3700X
host: Windows 10 Pro
gest: Windows 7 Ultimate
cpu: Intel Core i7-4810MQ
host: Arch Linux (KVM with nested virtualization)
guest1: Windows 7 Ultimate (with gvm installed)
guest2: Windows 7 Ultimate
The text was updated successfully, but these errors were encountered: