I installed Proxmox VE 8.2 on an HP EliteDesk 805 G8 Desktop Mini PC (AMD Ryzen 7 5700G with Radeon Graphics, 64GB DDR4-3200 memory).
I passed the AMD Ryzen 7 5700G's integrated graphics to the VM via PCIe passthrough, and everything worked fine on Windows 11 and macOS 14 VMs after disabling hibernation, although HP's conservative BIOS policy only allows 512MB of VRAM.
I'm used to running VMs 24/7 and accessing them headlessly via Remote Desktop.
Only one VM that needs the integrated graphics is running at a time.
Recently I found that after using a newer version (since October 2024) of NootedRed kext, macOS 15 VMs cannot be activated after being in inactive state and remaining for a while (remote desktop cannot be connected, screen is black, keyboard and mouse are unresponsive).
For example, the macOS 15 VM went into inactive state after I went to bed at night, and I woke up in the morning to find that the macOS 15 VM could no longer be activated. Checking the gpuRestart log, I found panic information.
This problem was found in both macOS 15.0 and macOS 15.1 VMs, but not in macOS 14 VM using the same kext.
What should've happened instead?
The macOS 15 VMs should be able to be activated normally after entering an inactive state, even after a long time.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
macOS Version
Sequoia
What is your CPU's model?
AMD Ryzen 7 5700G with Radeon Graphics
Please describe the behaviour in detail.
I installed Proxmox VE 8.2 on an HP EliteDesk 805 G8 Desktop Mini PC (AMD Ryzen 7 5700G with Radeon Graphics, 64GB DDR4-3200 memory).
I passed the AMD Ryzen 7 5700G's integrated graphics to the VM via PCIe passthrough, and everything worked fine on Windows 11 and macOS 14 VMs after disabling hibernation, although HP's conservative BIOS policy only allows 512MB of VRAM.
I'm used to running VMs 24/7 and accessing them headlessly via Remote Desktop. Only one VM that needs the integrated graphics is running at a time.
Recently I found that after using a newer version (since October 2024) of NootedRed kext, macOS 15 VMs cannot be activated after being in inactive state and remaining for a while (remote desktop cannot be connected, screen is black, keyboard and mouse are unresponsive). For example, the macOS 15 VM went into inactive state after I went to bed at night, and I woke up in the morning to find that the macOS 15 VM could no longer be activated. Checking the gpuRestart log, I found panic information.
This problem was found in both macOS 15.0 and macOS 15.1 VMs, but not in macOS 14 VM using the same kext.
What should've happened instead?
The macOS 15 VMs should be able to be activated normally after entering an inactive state, even after a long time.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.