Skip to content
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

macOS host crashes and reboots when launching Windows ARM VM. #6919

Open
duck09 opened this issue Dec 23, 2024 · 11 comments
Open

macOS host crashes and reboots when launching Windows ARM VM. #6919

duck09 opened this issue Dec 23, 2024 · 11 comments
Labels
crash Application crashes

Comments

@duck09
Copy link

duck09 commented Dec 23, 2024

Describe the issue
macOS host occasionally crashes, the screen flickers purple and then a reboot of my entire device occurs when launching a Windows VM (24H2). The issue is not always reproducible. Will attach a debug log when the issue occurs again but I have a crash log. Maybe related to the latest fix regarding the GPU driver for Windows 24H2.

Configuration

  • UTM Version: 4.6.4
  • macOS Version: 15.2
  • Mac Chip (Intel, M1, ...): M2

Crash log
QEMULauncher.txt

@duck09
Copy link
Author

duck09 commented Dec 23, 2024

macOS didn't crash this time around but this error happened when I tried to launch a Windows VM:

QEMU error: QEMU exited from an error: Assertion failed: (isv), function hvf_vcpu_exec, file hvf.c, line 2065.

debug.log

@osy
Copy link
Contributor

osy commented Dec 23, 2024

Can you attach your config.plist?

@osy osy added the crash Application crashes label Dec 23, 2024
@duck09
Copy link
Author

duck09 commented Dec 23, 2024

config.txt

@ghostplant
Copy link

The same to me. The image I am using is Windows 11 ARM64 .iso

@drweasel
Copy link

I've observed this as well (OS X 15.2, M2 Max) - Darwin 24.2.0 kernel panics and reboots. It seems to be related to the update to arm64-Windows 11 24H2.

@ghostplant
Copy link

I prefer using Win10 22H2 Arm64, may I know if someone successfully installed that one?

@brucekapp
Copy link

brucekapp commented Dec 29, 2024

I've observed this as well (OS X 15.2, M2 Max) - Darwin 24.2.0 kernel panics and reboots. It seems to be related to the update to arm64-Windows 11 24H2.

Also on 15.2 and M2 Max and having the same issue as you with the new 24H2 ISO.

Would you be able to show your kernel panic logs? Just curious because when I looked up mine, I saw stuff about hardware issues. (Multi-hit Error on L1-iTLB-MainArray)

However, I wasn't able to trigger any instability with stress tests nor have I experienced any issues (other than this) with months of daily use, so I'm confused.

Edit: using the latest ISO from CrystalFetch instead of MS website results in QEMULauncher process crash instead of whole system kernel panic

@drweasel
Copy link

drweasel commented Dec 30, 2024

I've observed this as well (OS X 15.2, M2 Max) - Darwin 24.2.0 kernel panics and reboots. It seems to be related to the update to arm64-Windows 11 24H2.

Also on 15.2 and M2 Max and having the same issue as you with the new 24H2 ISO.

Would you be able to show your kernel panic logs? Just curious because when I looked up mine, I saw stuff about hardware issues. (Multi-hit Error on L1-iTLB-MainArray)

sure (it contains the same "Multi-hit Error ..."):
panic-full-2024-12-24-132008.0002.panic.gz

@dyl421421
Copy link

I got the same error message, but was able to resolve this by going into System and manually changing the core count from Default to 4 on an M1 Mac.

@kylematoba
Copy link

seeing this as well on M2, 13.4 host with Win 11.

@turnipsoup
Copy link

I get this exact error when trying to run NetBSD aarch64 (evbarm64) under virtualization on an M2 MacOS 15.2 with UTM 4.6.4 (107) so this is not limited to just Windows. For what it is worth this same VM works on the previous release of UTM.

QEMU error: QEMU exited from an error: Assertion failed: (isv), function hvf_vcpu_exec, file hvf.c, line 2065.

I already have my CPU count set manually to 4 so the fix above does not resolve for me. Changing the CPU type from "Default" to something like Cortex-a53 does not resolve the issue either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crash Application crashes
Projects
None yet
Development

No branches or pull requests

8 participants