Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Suspending the VM requires "sudo setenforce 0". If SELinux is left enabled, suspend fails. Version-Release number of selected component (if applicable): open-vm-tools-10.2.5-2 How reproducible: Reproducable Steps to Reproduce: 1. Enable SELinux "sudo setenforce 1" 2. Suspend VM. (fails) Actual results: VMWare attempts to suspend the VM, and gives up after some time. Expected results: The VM should suspend, as it does without open-vm-tools enabled, or with SELinux disabled. Additional info: This is a fully up-to-date F28 installation. I couldn't find anything relevant in the syslog, but I'm not super familiar with the current logging setup. If anyone would like more information, just tell me where to look.
This might be related to bug reported here: https://github.com/vmware/open-vm-tools/issues/258 With SELinux set to "enforcing", can you spot a message similar to the following in your journalctl? Jun 26 10:00:42 xxxxxx audit[807]: USER_AVC pid=807 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.77 spid=1026 tpid=2556 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:vmtools_unconfined_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?' If so, does the proposed workaround from the GitHub issue work for you (while SELinux is still set to "enforcing")?
I had the same problem with a Fedora 29 VM. The proposed workaround from the GitHub issues works for me.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Hi Tomase, Do you install fedora on ESXi or Workstation,Fusion? which version do you use? Thanks, Lili Du
The guest is Fedora 28 Workstation; the host is Mac OS (10.13 then 10.14) running VMWare Fusion 10, then later 11.
(In reply to Thomas Burdick from comment #5) > The guest is Fedora 28 Workstation; the host is Mac OS (10.13 then 10.14) > running VMWare Fusion 10, then later 11. Thanks for your reply! I test on ESXi with Fedora 28, not meet this issue!
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.