<?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>tchung1970 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>tchung1970 Tracker</description>
    <pubDate>Thu, 23 Nov 2023 11:23:49 GMT</pubDate>
    <dc:date>2023-11-23T11:23:49Z</dc:date>
    <item>
      <title>Re: I can't start any virtual machine after updating to 17.5.0</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/I-can-t-start-any-virtual-machine-after-updating-to-17-5-0/m-p/2994194#M183552</link>
      <description>&lt;P&gt;I'm not sure if anyone already answered your question with command line fix.&lt;/P&gt;&lt;P&gt;I'm a Linux/UNIX guy. So I used "gnu sed" on macOS to fix the issue as following:&lt;/P&gt;&lt;PRE&gt;&lt;SPAN class=""&gt;1) Install gnu sed (gsed)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;% brew install gsed&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;2) Replace a value with gsed&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;% cd ~/Virtual\ Machines.localized &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;% grep ^serial0.present vmf-rhel7vm.vmwarevm/vmf-rhel7vm.vmx&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;serial0.present = "TRUE"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;% gsed -i '/^serial0.present/ s/TRUE/FALSE/' vmf-rhel7vm.vmwarevm/vmf-rhel7vm.vmx&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;% grep ^serial0.present vmf-rhel7vm.vmwarevm/vmf-rhel7vm.vmx&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;serial0.present = "FALSE"&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;That's it. This should get rid of the message when you launch the VM.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Nov 2023 03:11:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/I-can-t-start-any-virtual-machine-after-updating-to-17-5-0/m-p/2994194#M183552</guid>
      <dc:creator>tchung1970</dc:creator>
      <dc:date>2023-11-04T03:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Fusion 12 Big Sur - Unable to create installation medium</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-12-Big-Sur-Unable-to-create-installation-medium/m-p/2809504#M170020</link>
      <description>&lt;P&gt;create_macos_vm_install_dmg.sh (from&amp;nbsp;&lt;A href="https://github.com/rtrouton/create_macos_vm_install_dmg" target="_blank" rel="noopener"&gt;https://github.com/rtrouton/create_macos_vm_install_dmg&lt;/A&gt;)&amp;nbsp; created two files:&lt;BR /&gt;+&amp;nbsp;macOS_1101_installer.dmg&lt;BR /&gt;+&amp;nbsp;macOS_1101_installer.iso&lt;/P&gt;&lt;P&gt;I used&amp;nbsp;macOS_1101_installer.dmg with VMWare Fusion 12 Pro and I'm able to install macOS Big Sur (11.0.1)&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2020 06:06:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-12-Big-Sur-Unable-to-create-installation-medium/m-p/2809504#M170020</guid>
      <dc:creator>tchung1970</dc:creator>
      <dc:date>2020-11-16T06:06:36Z</dc:date>
    </item>
  </channel>
</rss>

