-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
QEMULauncher uses 200% CPU #5833
Comments
Hit the issue again today. In sampling report call stack goes through |
This is happening to me, too. I'm running 4.4.4, though, on a MBP running an M2 chip. I have four different VMs and it doesn't matter which one I use, the launcher peaks at over 200% CPU. Then, after a moment, it will calm back down to "normal" readings. However the VM is unstable -- the mouse and keyboard are jittery and slow to respond. This happens even at the login screen. |
Still an issue on MacOS 14.2 / UTM 4.4.4 |
Turns out that issue doesn't tied to host suspend/resume cycle. The issue happened online during normal workload. Interestingly, |
[SOLVED may be] The problem appears when one of the network interfaces is not configured. 2 interfaces configured for VM, only one UP in VM (/etc/network/interfaces not configured with 1 interface) Other is DOWN 2 interfaces configured for VM, only one UP in VM (/etc/network/interfaces not configured with 1 interface) hope this will help somebody. |
I'm having the same issue with one Linux install. 200% CPU when the Linux guest is idling. Another distro shows 20% when idle. Both too high! Since someone mentioned network, the one at 200% is using host-only networking if that matters. |
I have the same problem (QEMULauncher at 200% in addition to the activity of the VM), with a Windows 11 ARM64 VM on a MacBook Air M2, in the case where I start the VM with the network card disabled (at OS level), or after a suspend / resume, always with the network card disabled. When disabling the network card without suspending or shutting down, the problem occurs after a random duration. Simply re-enabling the network card fixes the problem. I hadn't made the report with the network until I came across this issue (I noticed the problem during offline testing). The problem therefore seems to occur when the network part is no longer functional.
|
I've tried some workarounds, in particular to change emulated network card, in hope that problem specific to some card-dependent emulation code. First I've tried different flavours of
Essentially driver performed automatically Now I've switched to If someone posses a knowledge about codebase and can suggest better candidate to test will be glad to hear. |
I also met this issue after host suspend/resume on Mac OS 14.4. |
Describe the issue
After host suspend/resume, without stopping VM, sometimes QEMULauncher uses 200% CPU and network in VM doesn't work. It feels like issues less reproducible after upgrade to Sonoma and UTM 4.3/4.4 but it is still there.
I believe it is closely related to #4803
I use VM as headless but have serial terminal connected. To work around this issue I log in to the guest over serial, it works perfectly fine, no CPU usage reported but network is completely dead. Simple turn off/on of the network interface(using something like
ip link set enp0s1 down && ip link set enp0s1 up
) lead to the interface reinitialisation and online fix of the QEMU network stack.Configuration
Crash log
N/A
Debug log
Sampling taken during the issue: QEMULauncher-4.4.3.txt
Upload VM
Was unable to reproduce this issue on general, fresh, VM. But, maybe I just need more patience.
The text was updated successfully, but these errors were encountered: