MacPro 3,1 hibernating

[deathwish]

First time setting up proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve).
I installed proxmox to an external SSD on a Lenovo Mq90.
After it said Installation successful! and rebooted I shutdown the system and installed the SSD in a Mac Pro 3,1.
It boots up Proxmox.
After some help from dj423, I was able to login to the web interface and everything seems to be working great - until it goes to sleep.
It goes to sleep after ~15min of inactivity. The web interface is unresposive, the monitor ges black and the power LED pulses on and off. But I can not seem to get it to wake up so I have to long press the power button on the MacPro to get it to shut down.

After reading this article : https://forum.proxmox.com/threads/my-proxmox-ve-occasionally-crashes-or-goes-into-sleep-mode.139933/ I did the following in the Shell:

systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

and

/etc/systemd/sleep.conf:

[...]

[Sleep]

AllowSuspend=no

AllowHibernation=no

AllowSuspendThenHibernate=no

AllowHybridSleep=no

[...]

I restarted the MacPro and I could have sworn it worked. I high fived myself only to find the MacPro in sleep mode several minutes later.

Does anyone have any ideas on how to prevent a MacPro 3,1 from going to sleep though Proxmox VE ?

I don't understand the System Log but here is part of it, fyi:

Feb 19 19:06:23 host1 systemd[12377]: Startup finished in 198ms.
Feb 19 19:06:23 host1 systemd[1]: Started user@0.service - User Manager for UID 0.
Feb 19 19:06:23 host1 systemd[1]: Started session-9.scope - Session 9 of User root.
Feb 19 19:06:23 host1 login[12393]: ROOT LOGIN on '/dev/pts/0'
Feb 19 19:06:38 host1 systemd[1]: session-9.scope: Deactivated successfully.
Feb 19 19:06:38 host1 systemd-logind[709]: Session 9 logged out. Waiting for processes to exit.
Feb 19 19:06:38 host1 systemd-logind[709]: Removed session 9.
Feb 19 19:06:38 host1 pvedaemon[1049]: <root@pam> end task UPID:host1:00003050:00061272:67B671FF:vncshell::root@pam: OK

At Feb 19 15:47:46 the Log Panel states Description: Shell Status: Error: unexpected status

Feb 19 19:06:48 host1 systemd[1]: Stopping user@0.service - User Manager for UID 0...
Feb 19 19:06:48 host1 systemd[12377]: Activating special unit exit.target...
Feb 19 19:06:48 host1 systemd[12377]: Stopped target default.target - Main User Target.
Feb 19 19:06:48 host1 systemd[12377]: Stopped target basic.target - Basic System.
Feb 19 19:06:48 host1 systemd[12377]: Stopped target paths.target - Paths.
Feb 19 19:06:48 host1 systemd[12377]: Stopped target sockets.target - Sockets.
Feb 19 19:06:48 host1 systemd[12377]: Stopped target timers.target - Timers.
Feb 19 19:06:48 host1 systemd[12377]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Feb 19 19:06:48 host1 systemd[12377]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 19 19:06:48 host1 systemd[12377]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Feb 19 19:06:48 host1 systemd[12377]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Feb 19 19:06:48 host1 systemd[12377]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Feb 19 19:06:48 host1 systemd[12377]: Removed slice app.slice - User Application Slice.
Feb 19 19:06:48 host1 systemd[12377]: Reached target shutdown.target - Shutdown.
Feb 19 19:06:48 host1 systemd[12377]: Finished systemd-exit.service - Exit the Session.
Feb 19 19:06:48 host1 systemd[12377]: Reached target exit.target - Exit the Session.
Feb 19 19:06:48 host1 systemd[1]: user@0.service: Deactivated successfully.
Feb 19 19:06:48 host1 systemd[1]: Stopped user@0.service - User Manager for UID 0.
Feb 19 19:06:48 host1 systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Feb 19 19:06:48 host1 systemd[1]: run-user-0.mount: Deactivated successfully.
Feb 19 19:06:48 host1 systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Feb 19 19:06:48 host1 systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Feb 19 19:06:48 host1 systemd[1]: Removed slice user-0.slice - User Slice of UID 0.

 

[fireon]

I'll just say it like it is. Proxmox is not designed to run on Macs. Please use hardware that is designed for it.

I imagine that you might have to disable all energy-saving functions in the Mac's BIOS (if possible)?

 

[ghusson]

I am not a mac user. Maybe this can help (after rebooting on MacOS) : https://osxdaily.com/2015/02/03/set...tem-inactivity-from-the-command-line-in-os-x/

 

[deathwish]

I am not a mac user. Maybe this can help (after rebooting on MacOS) : https://osxdaily.com/2015/02/03/set...tem-inactivity-from-the-command-line-in-os-x/

Thanks for the response. I never thought about logging in to OS X.
Unfortunately when I checked the current Mac system sleep status by entering sudo systemsetup -getcomputersleep the response I got was Computer Sleep: Never.
I did change it from Never to Off. It seemed to accept it but it still states Computer Sleep: Never. so I do not expect that it changed the behavior. I'm glad I checked that off the list though.