<?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>MaxBurn Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>MaxBurn Tracker</description>
    <pubDate>Fri, 17 Nov 2023 18:16:19 GMT</pubDate>
    <dc:date>2023-11-17T18:16:19Z</dc:date>
    <item>
      <title>Re: Repeated /dev/vmmon and failure to update VMware player under Linux Mint.</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2994183#M41066</link>
      <description>&lt;P&gt;And we are back with the same problem. Try re-importing the mok der file again but it says it is already there.&amp;nbsp;&lt;/P&gt;&lt;P&gt;but still, no /dev/vmmon. Make sure kernel module vmmon is loaded. How? Why does this keep happening?&lt;/P&gt;&lt;P&gt;I am locked out of this VM again...&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2023 22:47:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2994183#M41066</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2023-11-03T22:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Repeated /dev/vmmon and failure to update VMware player under Linux Mint.</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2992177#M41007</link>
      <description>&lt;P&gt;For reasons I do not understand I had to redo mok signing and import keys again to get rid of the first error and now my virtual machine can run again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not going to have to keep doing that am I?&lt;/P&gt;&lt;P&gt;Still have the 100% download and update pending issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Oct 2023 14:08:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2992177#M41007</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2023-10-22T14:08:30Z</dc:date>
    </item>
    <item>
      <title>Repeated /dev/vmmon and failure to update VMware player under Linux Mint.</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2992175#M41006</link>
      <description>&lt;P&gt;Background at the bottom but bottom line I had VMware working last week on a new linux mint install.&amp;nbsp;This week after not really doing anything in VMware I'm faced with these new problems and I'm wondering if this is worth continuing with VMware? Is VMware reliable under linux? Are these easy fixes?&lt;/P&gt;&lt;P&gt;Launching my VM that worked fine last week I now get a similar error to what I originally saw (I think), why is this happening again?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2023-10-22 08-53-54.png" style="width: 304px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/104098iBCAA453CAD1DB819/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2023-10-22 08-53-54.png" alt="Screenshot from 2023-10-22 08-53-54.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;VMware let me know there was a new version available, so I told it to do it. The download gets to 100% and then nothing. I've left it in this state for fifteen minutes and TOP says it isn't busy so I don't know what the issue here is. Cancel says cancel the download, cancel the download that is 100% complete?? Reboot and do the same thing and get same results.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot from 2023-10-22 08-51-15.png" style="width: 505px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/104099i41689080D9ED8DC1/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot from 2023-10-22 08-51-15.png" alt="Screenshot from 2023-10-22 08-51-15.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;VMware Player 17.0.2 build-21581411 on &lt;SPAN&gt;Linux Mint 21.2 Victoria&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Background;&amp;nbsp;I'm moving a windows VM from a personal mac (fusion) to my linux mint machine. New install of mint and I grabbed latest VMware player. I initially had some problems because I do have secure boot enabled and&amp;nbsp; I didn't understand what was happening the first time the MOH screen came up. &lt;A href="https://kb.vmware.com/s/article/2146460" target="_self"&gt;This article got me running&lt;/A&gt; and I was able to run my windows machine no problem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Oct 2023 13:17:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Repeated-dev-vmmon-and-failure-to-update-VMware-player-under/m-p/2992175#M41006</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2023-10-22T13:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: Keyboard and Mouse not working in VMWare Fusion guests</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Keyboard-and-Mouse-not-working-in-VMWare-Fusion-guests/m-p/2952534#M181744</link>
      <description>&lt;P&gt;Mouse works, keyboard still does not. Now what?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Feb 2023 01:03:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Keyboard-and-Mouse-not-working-in-VMWare-Fusion-guests/m-p/2952534#M181744</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2023-02-04T01:03:22Z</dc:date>
    </item>
    <item>
      <title>Ubuntu P2V: kernel panic not syncing vfs unable to mount root fs on unknown-block 0,0</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Ubuntu-P2V-kernel-panic-not-syncing-vfs-unable-to-mount-root-fs/m-p/1377204#M21426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a 16.04LTS running on an intel NUC that seems happy there. I'm trying to P2V to my ESXi6.5u1 machine. The machine is up to date with apt-get update etc. Conversion seems to go fine though I did make the memory and disk sizes a little smaller, but still way bigger than it needs. Booting that VM gets me kernel panic not syncing vfs unable to mount root fs on unknown-block 0,0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Tried to boot advanced options and it shows one for upstart and another for recovery mode. They all boot to the same error. Following some guides online I hit C to go to command line and for example "df -h" results in error: can't find command 'df'. Every command I'm finding online to troubleshoot this is not found. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; What should I do?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other things I have tried:&lt;/P&gt;&lt;P&gt;Deleted the VM and converted it again, only this time selecting SATA disks instead of the suggested SCSI, which would match the source machine. Same exact problem.&lt;/P&gt;&lt;P&gt;Third time through I found a warning message about resizing boot, set that to the same size but still got same error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[img]&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://i.imgur.com/ubdTOoc.png[/img]" rel="nofollow"&gt;https://i.imgur.com/ubdTOoc.png[/img]&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Apr 2018 19:05:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Ubuntu-P2V-kernel-panic-not-syncing-vfs-unable-to-mount-root-fs/m-p/1377204#M21426</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2018-04-07T19:05:51Z</dc:date>
    </item>
    <item>
      <title>Windows 7 activation problems</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Windows-7-activation-problems/m-p/2624717#M162768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a windows activation error 0xc004c008 but only inside VMware Fusion. When I reboot into botcamp/windows activation says it is fine. I don't see how one copy of windows can be both activated and not activated at the same time unless VMware is interfering somehow??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The history is I did a bootcamp install of windows 7 a week or two ago and all went well, windows activated fine. I bought fusion and that brought the bootcamp version into OSX just great. About a week later I get the activation eror above, but again only when I am in the bootcamp partition through VMware. Booted into the bootcamp partition natively without vmware I can do updates and check activation and all looks good. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't called windows activation yet, am I going to have trouble with them?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Feb 2012 21:52:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Windows-7-activation-problems/m-p/2624717#M162768</guid>
      <dc:creator>MaxBurn</dc:creator>
      <dc:date>2012-02-10T21:52:53Z</dc:date>
    </item>
  </channel>
</rss>

