<?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>Bascisco Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Bascisco Tracker</description>
    <pubDate>Thu, 23 Nov 2023 11:21:55 GMT</pubDate>
    <dc:date>2023-11-23T11:21:55Z</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/2992581#M183294</link>
      <description>&lt;P&gt;For now not seen this on my&amp;nbsp; Ubuntu 22.04 VM's under the same Workstation Pro 17.5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2023 09:52:14 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/2992581#M183294</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2023-10-25T09:52:14Z</dc:date>
    </item>
    <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/2992580#M183293</link>
      <description>&lt;P&gt;Indeed on a VM windows 10 machine after upgrading to 17.5 I get exact this same warning.&lt;BR /&gt;&lt;STRONG&gt;serial0: Parameter "serial0.fileType" has an invalid value "thinprint"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;For the moment I ignore this. I trust this will be fixed in a next release and the vmx file modification is just a work-around.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2023 09:44:01 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/2992580#M183293</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2023-10-25T09:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation Pro 12.5.6 build-5528349 crashes on several Linux based software image</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219235#M132018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Darius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your remark of MTU 1600 triggered it for me. Indeed not the upgrade as such. Although IMHO VMware image shouldn't crash on it, but you mentioned that already ;-).&lt;/P&gt;&lt;P&gt;I had from a config template indeed mtu set to 1600.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I changed that to mtu 1536 and even with now again dot1q on it works. And no more VMWare crashes either.&lt;/P&gt;&lt;P&gt;I want to have a minimal payload of 1500 IP bytes + 20 bytes IP header + 8 bytes dot1q +&amp;nbsp; (2 * 4 bytes MPLS label) makes 1536 as minimum for the L2 Ethernet frame.&lt;/P&gt;&lt;P&gt;I changed that and even all works for the B2B directly connected working interface, redundancy interface &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@7651DD0E8772B3B5D93ADA9ABA2E067C/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; I will see later back for the other interfaces that will also run MPLS between each other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So for others remember this one regarding MTU Size do not pass beyond 1600 or VMware&amp;nbsp; Workstation crashes due the vmxnet3 driver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you again for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jun 2017 15:15:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219235#M132018</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2017-06-19T15:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation Pro 12.5.6 build-5528349 crashes on several Linux based software image</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219233#M132016</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Darius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for getting back to me. As others might still read the post. I have one question on the downgrade you suggested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; As my upgrade where till this point via&amp;nbsp; WS Workstation upgrade process. &lt;/P&gt;&lt;P&gt;I tried to downgrade using, VMware-workstation-full-12.5.5-5234757.exe that I downloaded from the VMware site. Then I got this message executing that file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/73244i6CE3280085938F5B/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please do not tell me that I have to uninstall VMware Workstation. Because Then I have to set up all my 19 vmnets again. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@5FC79C0032E597F6EC0C3A71500D7708/emoticons/1f61e.png" alt=":disappointed_face:" title=":disappointed_face:" /&gt;&lt;/P&gt;&lt;P&gt;Hence how can I save that and to remaining other settings. Then a downgrade isn't a pain. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for the fast response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bas.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jun 2017 12:48:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219233#M132016</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2017-06-19T12:48:49Z</dc:date>
    </item>
    <item>
      <title>Workstation Pro 12.5.6 build-5528349 crashes on several Linux based software image</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219231#M132014</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;As i can't log a support ticket to VMware I am reporting this via the community.&lt;/P&gt;&lt;P&gt;I have a Lenovo P50 machine with 1TB SSD and 64GB DRAMM.&lt;/P&gt;&lt;P&gt;I am running for a long while some company specific linux based software (we have OVA files)&lt;BR /&gt;Since the upgrade to 12.5.6 build-5528349 I experience crashes of the VMware instances.&lt;/P&gt;&lt;P&gt;I have log files of that which I can only share with VMware direct and not to a forum like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I would like to hear if others reported crash upgrading to 12.5.6 build-5528349.&lt;/P&gt;&lt;P&gt;I can from version 12.5.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brgds,&lt;/P&gt;&lt;P&gt;B&lt;/P&gt;&lt;P&gt;as.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jun 2017 11:19:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-12-5-6-build-5528349-crashes-on-several-Linux/m-p/2219231#M132014</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2017-06-19T11:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: Crash after upgrade to Workstation 10.0.6-2700073 having non-default VMnets</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Crash-after-upgrade-to-Workstation-10-0-6-2700073-having-non/m-p/1755255#M103206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Downgrade to 10.0.5 and rebuild vmnets. I have a Lenovo w530 with windows 7 64bit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 22:03:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Crash-after-upgrade-to-Workstation-10-0-6-2700073-having-non/m-p/1755255#M103206</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2015-05-20T22:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: Crash after upgrade to Workstation 10.0.6-2700073</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Crash-after-upgrade-to-Workstation-10-0-6-2700073/m-p/2228369#M132577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am wondering that too.&amp;nbsp; Also all My VMnets were gone. See other post I did on that when you add VMnets it crashes again. That was my main trigger causing the 10.0.0.6 crashes.&lt;/P&gt;&lt;P&gt;I am back on 10.0.5 and I had to rebuild a couple of things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brgds,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Bas.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2015 12:42:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Crash-after-upgrade-to-Workstation-10-0-6-2700073/m-p/2228369#M132577</guid>
      <dc:creator>Bascisco</dc:creator>
      <dc:date>2015-05-20T12:42:49Z</dc:date>
    </item>
  </channel>
</rss>

