From: Thomas Huth <1923648@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1923648] Re: macOS App Nap feature gradually freezes QEMU process
Date: Mon, 17 May 2021 18:39:05 -0000 [thread overview]
Message-ID: <162127674601.2101.371955905639261887.malone@wampee.canonical.com> (raw)
In-Reply-To: 161833605825.22256.5828075734668933155.malonedeb@soybean.canonical.com
Moved here:
https://gitlab.com/qemu-project/qemu/-/issues/334
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #334
https://gitlab.com/qemu-project/qemu/-/issues/334
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1923648
Title:
macOS App Nap feature gradually freezes QEMU process
Status in QEMU:
Fix Released
Bug description:
macOS version: 10.15.2
QEMU versions: 5.2.0 (from MacPorts)
5.2.92 (v6.0.0-rc2-23-g9692c7b037)
If the QEMU window is not visible (hidden, minimized or another
application is in full screen mode), the QEMU process gradually
freezes: it still runs, but the VM does not respond to external
requests such as Telnet or SSH until the QEMU window is visible on the
desktop.
This behavior is due to the work of the macOS App Nap function:
https://developer.apple.com/library/archive/documentation/Performance/Conceptual/power_efficiency_guidelines_osx/AppNap.html#//apple_ref/doc/uid/TP40013929-CH2-SW1
It doesn't matter how the process is started -- as a background job or
as a foreground shell process in case QEMU has a desktop window.
My VM does not have a display output, only a serial line, most likely
if the VM was using OpenGL, or playing sound (or any other App Nap
triggers), then the problem would never have been detected.
In my case only one starting way without this problem:
sudo qemu-system-x86_64 -nodefaults \
-cpu host -accel hvf -smp 1 -m 384 \
-device virtio-blk-pci,drive=flash0 \
-drive file=/vios-adventerprisek9-m.vmdk.SPA.156-1.T.vmdk,if=none,format=vmdk,id=flash0 \
-device e1000,netdev=local -netdev tap,id=local,ifname=tap0,script=no,downscript=no \
-serial stdio -display none
The typical way from the internet to disable App Nap doesn't work:
defaults write NSGlobalDomain NSAppSleepDisabled -bool YES
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1923648/+subscriptions
prev parent reply other threads:[~2021-05-17 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 17:47 [Bug 1923648] [NEW] macOS App Nap feature gradually freezes QEMU process Vasiliy Nikonov
2021-05-15 10:22 ` [Bug 1923648] " Thomas Huth
2021-05-17 17:38 ` Vasiliy Nikonov
2021-05-17 18:39 ` Thomas Huth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162127674601.2101.371955905639261887.malone@wampee.canonical.com \
--to=1923648@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).