qemu-system-aarch64 crash on qemu 6.0 - Windows 10
I experience App crashes of qemu-system-aarch64 while booting up an ARM64 VM on Qemu 6.0 on Windows 10. It boots up the actual Windows 10 ARM64 Insider Build 21390 ISO with the following VM Config (which was working already before on older Qemu Versions):
qemu-system-aarch64.exe
-M virt,virtualization=true
-accel tcg,thread=multi
-cpu cortex-a57
-smp 2
-m 4G
-bios edk2-aarch64-code.fd
-device ramfb
-device qemu-xhci
-device usb-kbd
-device usb-tablet
-netdev user,id=net0,hostfwd=tcp::5555-:3389 -device virtio-net,netdev=net0,disable-legacy=on
-drive file=E:\VM\Qemu\21390.iso,media=cdrom,if=none,id=cdrom -device usb-storage,drive=cdrom
-drive file=E:\VM\Qemu\virtio-win-0.1.190.iso,media=cdrom,if=none,id=drivers -device usb-storage,drive=drivers
-drive file=E:\VM\Qemu\sys.qcow2,if=virtio
Before i can get into the Windows 10 Setup GUI the whole VM crashes with following infos in Application Log:
Faulting application name: qemu-system-aarch64.exe, version: 6.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000001b70a3dc
Faulting process ID: 0x2064
Faulting application start time: 0x01d75463c94196c8
Faulting application path: C:\Program Files\qemu\qemu-system-aarch64.exe
Faulting module path: unknown
Report ID: d3583c85-34ee-4578-86e2-4a448bd85b6c
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1580701298148875373, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: qemu-system-aarch64.exe
P2: 6.0.0.0
P3: 00000000
P4: StackHash_4eea
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_88_FROM_unknown+0x0000000000000000
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F98.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2035.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2056.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2054.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2074.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_qemu-system-aarc_fe2188121c5fd6118af7d44df9d4f16aba2411_1e5ecaa8_11d68632-c584-4a03-902d-a78acbf1b709
Analysis symbol:
Rechecking for solution: 0
Report Id: d3583c85-34ee-4578-86e2-4a448bd85b6c
Report Status: 268435456
Hashed bucket: be6a5e9837e73d5fa5efc774ac299c6d
Cab Guid: 0
Unfortunatly i cannot get more infromations because i cannot access the mentioned files. I tried some small adaptions on the VM Config like changing the CPU to Cortex-A72 and older Virt Versions with "virt-5.2". I also adjusted the RAM to 8GB and SMP to 4.
For sure it could also be the Insider Build itself (older versions worked also), i will test older builds maybe.. Do you have any suggestions or infos? Thanks!