<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Key was rejected by service in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827375#M168595</link>
    <description>&lt;P&gt;I have installed Workstation Pro 16.1 on Fedora 33.&amp;nbsp; It fails to start.&amp;nbsp; After some investigating it comes down to this&lt;/P&gt;&lt;P&gt;modprobe vmmon&lt;BR /&gt;modprobe: ERROR: could not insert 'vmmon': Key was rejected by service&lt;/P&gt;&lt;P&gt;The same happens for the vmnet module.&lt;/P&gt;&lt;P&gt;running dmesg shows&lt;/P&gt;&lt;P&gt;vmmon: Loading of unsigned module is rejected&lt;/P&gt;&lt;P&gt;I have Workstation Pro 16.1 running on Fedora 31 and Fedora 32 and it works fine there.&amp;nbsp; So obviously something has changed in Fedora 33 to cause this problem.&amp;nbsp; So what do I need to do to fix the problem?&lt;/P&gt;&lt;P&gt;Any help is appreciated&lt;/P&gt;&lt;P&gt;Paolo&lt;/P&gt;</description>
    <pubDate>Wed, 03 Feb 2021 18:31:35 GMT</pubDate>
    <dc:creator>pgaltieri</dc:creator>
    <dc:date>2021-02-03T18:31:35Z</dc:date>
    <item>
      <title>Key was rejected by service</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827375#M168595</link>
      <description>&lt;P&gt;I have installed Workstation Pro 16.1 on Fedora 33.&amp;nbsp; It fails to start.&amp;nbsp; After some investigating it comes down to this&lt;/P&gt;&lt;P&gt;modprobe vmmon&lt;BR /&gt;modprobe: ERROR: could not insert 'vmmon': Key was rejected by service&lt;/P&gt;&lt;P&gt;The same happens for the vmnet module.&lt;/P&gt;&lt;P&gt;running dmesg shows&lt;/P&gt;&lt;P&gt;vmmon: Loading of unsigned module is rejected&lt;/P&gt;&lt;P&gt;I have Workstation Pro 16.1 running on Fedora 31 and Fedora 32 and it works fine there.&amp;nbsp; So obviously something has changed in Fedora 33 to cause this problem.&amp;nbsp; So what do I need to do to fix the problem?&lt;/P&gt;&lt;P&gt;Any help is appreciated&lt;/P&gt;&lt;P&gt;Paolo&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2021 18:31:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827375#M168595</guid>
      <dc:creator>pgaltieri</dc:creator>
      <dc:date>2021-02-03T18:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: Key was rejected by service</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827591#M168606</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The kernel module is not signed with a certificate and if you want to use it on fedora 33 then you -apparently- have to sign it.&lt;/P&gt;
&lt;P&gt;More info on how-to do that is here:&lt;BR /&gt;&lt;A href="https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html" target="_blank"&gt;https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck!&lt;BR /&gt;--&lt;BR /&gt;Wil&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2021 13:33:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827591#M168606</guid>
      <dc:creator>wila</dc:creator>
      <dc:date>2021-02-04T13:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: Key was rejected by service</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827664#M168609</link>
      <description>&lt;P&gt;Wila,&lt;/P&gt;&lt;P&gt;&amp;nbsp; thanks for the information.&amp;nbsp; I was wondering though how does it work on Windows?&amp;nbsp; This laptop boots to both Windows and Fedora and Workstation 16.1 runs fine on Windows?&lt;/P&gt;&lt;P&gt;Paolo&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2021 17:07:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827664#M168609</guid>
      <dc:creator>pgaltieri</dc:creator>
      <dc:date>2021-02-04T17:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Key was rejected by service</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827685#M168612</link>
      <description>&lt;P&gt;Paolo,&lt;/P&gt;
&lt;P&gt;On Windows signing kernel extensions is a thing for many years. It has been required to do since at least Windows Vista. On windows the kernel extensions come pre-built by VMware and are also signed by VMware.&lt;/P&gt;
&lt;P&gt;On Linux however, the kernel is not exactly stable in its programming interface and as a way to help you, VMware provides the source of the kernel modules. So you compile these yourself. As such they cannot provide the certificates from VMware to sign. &lt;BR /&gt;Over time I expect VMware to handle this as well, by generating the internal/local certificates on your host and use those to sign the kernel extensions after you built the modules.&lt;/P&gt;
&lt;P&gt;Long story short, this requirement for signing Linux kernel modules is fairly new and as such VMware does not have a "just click to upgrade" solution for this.&lt;/P&gt;
&lt;P&gt;The admin guide I pointed to basically holds you by the hand on how-to do this yourself over about 5 pages (click Next at the bottom to continue)&lt;/P&gt;
&lt;P&gt;I'm sure that there's some blog posts out there that explain this in more details as well.&lt;/P&gt;
&lt;P&gt;--&lt;BR /&gt;Wil&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2021 17:53:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2827685#M168612</guid>
      <dc:creator>wila</dc:creator>
      <dc:date>2021-02-04T17:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: Key was rejected by service</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2876452#M172246</link>
      <description>&lt;P&gt;Thanks for the info.&lt;BR /&gt;&amp;nbsp;Any links on how to get VMWARE player to work on OpenSUSE 15.3.&amp;nbsp; We followed the instructions for making MOK keys but get same error as the pgaltieri.&lt;/P&gt;&lt;P&gt;When we check the modprobe for vmmon, it shows &lt;SPAN&gt;&lt;BR /&gt;modprobe: ERROR: could not insert 'vmmon': Key was rejected by service&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We followed these steps -&amp;gt; vmware kb2146460&lt;/P&gt;&lt;P&gt;Any suggestions would be helpful....&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 04:58:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Key-was-rejected-by-service/m-p/2876452#M172246</guid>
      <dc:creator>Learner4</dc:creator>
      <dc:date>2021-11-05T04:58:57Z</dc:date>
    </item>
  </channel>
</rss>

