git: 3c1326a472 - main - handbook/virtualization: add note on workaround for Parallels

Mike Karels <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by karels:

URL: https://cgit.FreeBSD.org/doc/commit/?id=3c1326a472ca67ff6159d644589ab5e5bfc1258c

commit 3c1326a472ca67ff6159d644589ab5e5bfc1258c
Author:     Mike Karels <[email protected]>
AuthorDate: 2024-05-07 22:09:06 +0000
Commit:     Mike Karels <[email protected]>
CommitDate: 2024-05-07 22:09:06 +0000

    handbook/virtualization: add note on workaround for Parallels
    
    A user reported high CPU utilization on a fresh install of 14.0
    on Parallels (MacOS, M1/Apple Silicon).  Disabling the new ACPI
    ged(4) device worked around the problem.  Document this (for now).
    
    Reviewed by:    pauamma_gundo.com
    Differential Revision:  https://reviews.freebsd.org/D45103
---
 documentation/content/en/books/handbook/virtualization/_index.adoc | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/documentation/content/en/books/handbook/virtualization/_index.adoc b/documentation/content/en/books/handbook/virtualization/_index.adoc
index c567bd9c76..4084bfc73c 100644
--- a/documentation/content/en/books/handbook/virtualization/_index.adoc
+++ b/documentation/content/en/books/handbook/virtualization/_index.adoc
@@ -136,6 +136,13 @@ kern.hz=100
 +
 Without this setting, an idle FreeBSD Parallels guest will use roughly 15% of the CPU of a single processor iMac(R).
 After this change the usage will be closer to 5%.
++
+If installing FreeBSD 14.0 or later, and CPU utilization is still high, add the following additional line to [.filename]#/boot/loader.conf#:
++
+[.programlisting]
+....
+debug.acpi.disabled="ged"
+....
 . Create a New Kernel Configuration File
 +
 All of the SCSI, FireWire, and USB device drivers can be removed from a custom kernel configuration file.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.