Describe the issue
QEMULauncher appears to leak memory when launching a Debian Buster arm64 VM on M1 macOS. The test VM is configured to launch with 3GB of ram. After 5 minutes of operation QEMULauncher requires 826.0MB of ram. After several days QEMULauncher has allocated more than 20GB of ram which is significantly larger than the 8GB M1 host memory.
Configuration
- UTM Version: 4.0.6 (65)
- macOS Version: Big Sur 11.7
- Mac Chip: M1
- Memory: 8GB
- VM: Debian Buster 4.19.0-21-arm64 kernel
Crash log
There is no crash log. Eventually the host will run exhaust all memory and kill QEMULauncher. Before then the VM and the UTM UI become unresponsive due to paging to disk.
Debug log
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
I have been unsuccessful up to this point at exporting the debug log due to the UTM UI becoming unresponsive. I will attempt to capture a log sooner but wanted to be sure to file a report as 4.0.x is nearing release. Is there another way to trigger the export of the log when the UTM UI is unresponsive?
Upload VM
It is unclear that the problem is related to one specific VM.
Describe the issue
QEMULauncher appears to leak memory when launching a Debian Buster arm64 VM on M1 macOS. The test VM is configured to launch with 3GB of ram. After 5 minutes of operation QEMULauncher requires 826.0MB of ram. After several days QEMULauncher has allocated more than 20GB of ram which is significantly larger than the 8GB M1 host memory.
Configuration
Crash log
There is no crash log. Eventually the host will run exhaust all memory and kill QEMULauncher. Before then the VM and the UTM UI become unresponsive due to paging to disk.
Debug log
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the
QEMUpage isDebug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and selectExport Log...and attach it here.I have been unsuccessful up to this point at exporting the debug log due to the UTM UI becoming unresponsive. I will attempt to capture a log sooner but wanted to be sure to file a report as 4.0.x is nearing release. Is there another way to trigger the export of the log when the UTM UI is unresponsive?
Upload VM
It is unclear that the problem is related to one specific VM.