<?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>shibu_nyc Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>shibu_nyc Tracker</description>
    <pubDate>Tue, 21 Nov 2023 13:26:09 GMT</pubDate>
    <dc:date>2023-11-21T13:26:09Z</dc:date>
    <item>
      <title>Re: Workstation 16.2.1: vmmon &amp; vmnet not compiling on Pop!_OS 21.10, kernel 5.18.8</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16-2-1-vmmon-amp-vmnet-not-compiling-on-Pop-OS-21-10/m-p/2891219#M173887</link>
      <description>&lt;P&gt;It took a while but once &lt;FONT color="#0000FF"&gt;sabennett&lt;/FONT&gt; spelled out the steps line by line, I finally got WS Pro 16.2.1 up and running for the first time in nearly a month.&amp;nbsp;&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2885277/highlight/false#M173211" target="_blank"&gt;https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2885277/highlight/false#M173211&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This is a production machine. That was the last time I upgrade a kernal without verifying that WS Pro will work first. I am setting up a second popOS machine now.&lt;/P&gt;&lt;P&gt;Thanks again &lt;FONT color="#0000FF"&gt;DigitalDude&lt;/FONT&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 23:29:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16-2-1-vmmon-amp-vmnet-not-compiling-on-Pop-OS-21-10/m-p/2891219#M173887</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2022-01-31T23:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: VM Workstation 16.1-&gt;16.2.1 on Ubuntu 21.10 broke everything</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2891218#M173886</link>
      <description>&lt;P&gt;Thank you so much &lt;FONT color="#0000FF"&gt;sabennett&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Just got VMware WS Pro 16.2.1 working for the first time in &lt;U&gt;nearly a month&lt;/U&gt;!&lt;/P&gt;&lt;P&gt;It will be a long time before I upgrade to the next linux kernal. Maybe I'll get a second popOS system just to verify that WS Pro will work with any new kernal before upgrading on my production machine in the future.&lt;/P&gt;&lt;P&gt;I gave you a Kudo, If I could support you on patreon or something for your time I would.&lt;/P&gt;&lt;P&gt;Great detailed tutorial that a 5yo could understand - which is exactly what I needed.&lt;/P&gt;&lt;P&gt;BTW, even though I need things spelled out I prefer the command line over the graphic interface. I just don't know all of the commands but when you spell out all the lines verbatim it is much easier to cp and paste than It is to look for different settings in windows.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 23:19:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2891218#M173886</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2022-01-31T23:19:35Z</dc:date>
    </item>
    <item>
      <title>Re: VM Workstation 16.1-&gt;16.2.1 on Ubuntu 21.10 broke everything</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2885220#M173204</link>
      <description>&lt;P&gt;Can you or anyone post step by step instruction on how to build vmnet and vmmon yourself along with how to comment out the ASSERT_ON_COMPILE macro in vm_asm_x86.h?&lt;/P&gt;&lt;P&gt;Please assume I am an idiot former Windows user.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Dec 2021 19:50:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2885220#M173204</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-12-24T19:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation 16.2.1: vmmon &amp; vmnet not compiling on Pop!_OS 21.10, kernel 5.18.8</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16-2-1-vmmon-amp-vmnet-not-compiling-on-Pop-OS-21-10/m-p/2884959#M173175</link>
      <description>&lt;P&gt;I was surprised to see that VMware WS 16.2.1 was running fine for you in&amp;nbsp; Pop!_OS 21.10.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was unable to boot up VMware Workstation Pro as soon as I updated to Pop!_OS 21.10. Made me wish I waited before upgrading.&lt;/P&gt;&lt;P&gt;When I attempt to launch&amp;nbsp;WS Pro 16.2.1 the "VMware Kernal Module Updater" comes up with a message stating "Before you can run VMware, several modules must be compiled and loaded into the running kernel." When I click the "Install" button, the "VMware Kernal Module Updater" window pops up stating that it is "Compiling and installing following kernal modules..."&amp;nbsp;&lt;/P&gt;&lt;P&gt;vmmon&lt;/P&gt;&lt;P&gt;vmnet&lt;/P&gt;&lt;P&gt;Then I always get the same error window which states "Unable to installl all modules. See log for details (Exit code 1)&lt;/P&gt;&lt;P&gt;I was planning on just waiting for VMware to release a new version to fix the issue but if WS 16.2.1 was working fine for you under Pop!_OS 21.10, i guess we both have to figure this out on our own.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Dec 2021 21:37:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16-2-1-vmmon-amp-vmnet-not-compiling-on-Pop-OS-21-10/m-p/2884959#M173175</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-12-22T21:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: VM Workstation 16.1-&gt;16.2.1 on Ubuntu 21.10 broke everything</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2884735#M173157</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I'm in the same boat with &lt;STRONG&gt;popOS 21.10&lt;/STRONG&gt;... After the upgrade to 21.10, VMWare workstation build for the new kernel fails.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 22:37:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Workstation-16-1-gt-16-2-1-on-Ubuntu-21-10-broke-everything/m-p/2884735#M173157</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-12-21T22:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation Pro 16.0 stopped booting in PopOS</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-0-stopped-booting-in-PopOS/m-p/2839511#M169449</link>
      <description>&lt;P&gt;I upgraded workstation Pro 16.0 to 16.1 and it is launching again!&lt;/P&gt;&lt;P&gt;I did not realize the new version was released.&lt;/P&gt;&lt;P&gt;Thank you Willa.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 08:49:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-0-stopped-booting-in-PopOS/m-p/2839511#M169449</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-04-02T08:49:34Z</dc:date>
    </item>
    <item>
      <title>Workstation Pro 16.0 stopped booting in PopOS</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-0-stopped-booting-in-PopOS/m-p/2839453#M169442</link>
      <description>&lt;P&gt;I use Workstation Pro 16.0 every day on a Pop!_OS 20.10 host (similar to Ubuntu).&amp;nbsp; Yesterday when I tried to launch Workstation Pro 16.0, I got a "VMware Kernal&amp;nbsp; Module Updater" window stating "Before you can run VMware, sever modules must be compiled and loaded into the running kernal.".&lt;/P&gt;&lt;P&gt;Then another window with a red exclamation mark appears stating:&lt;/P&gt;&lt;P&gt;Unable to install all modules. See log /tmp/vmware-drk/-vmware4287.log for details. (Exit code 1)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;It was working fine the previous day. I'm not sure what happened. I did have a minor OS update but I get those 2-3 times per week. I was worried about something like this happening when I upgraded from Pop OS 20.0 to 20.1 but i wouldn't have thought a minor OS update would cause this.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 20:38:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-0-stopped-booting-in-PopOS/m-p/2839453#M169442</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-04-01T20:38:55Z</dc:date>
    </item>
    <item>
      <title>Workstation Pro 16 on Ubuntu 20.10 ?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-on-Ubuntu-20-10/m-p/2826196#M168500</link>
      <description>&lt;P&gt;I installed Workstation Pro 16 on a Pop!_OS 20.10 host and it seems to be working fine with both Win7 &amp;amp; Win10 guest machines.&lt;/P&gt;&lt;P&gt;If it works on a Pop!_OS 20.10 host, can I assume it will also work with an Ubuntu 20.10 host?&lt;/P&gt;&lt;P&gt;Has anyone used Workstation Pro 16 on an Ubuntu 20.10 host?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2021 22:50:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-Pro-16-on-Ubuntu-20-10/m-p/2826196#M168500</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2021-01-28T22:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation 12 USB 3.0 / 3.1 support ?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-12-USB-3-0-3-1-support/m-p/1387457#M79662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;UPDATE: I just found this KB: &lt;A href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=2041591#usbdevicework" title="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;docTypeID=DT_KB_1_1&amp;amp;externalId=2041591#usbdevicework"&gt;VMware KB:&amp;nbsp;&amp;nbsp;&amp;nbsp; Host and guest OS USB 3.0 and virtual xHCI support with Workstation 9&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It says that o&lt;SPAN&gt;n Windows 7 and Windows XP hosts, USB 3.0 support of Workstation in the guest operating system is experimental and limited to specific configurations of USB 3.0 hardware and drivers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;A USB 3.0 device attached to the host is only known to work in guest operating systems with specific configurations of USB 3.0 host controllers using the NEC/RENESAS chipset and driver on the host. To support USB 3.0 device functionality in a guest operating system, the NEC USB 3.0 host controller and driver must be properly installed on the Windows host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Known supported USB 3.0 xHCI controller host configurations:&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;NEC/RENESAS μPD720200 chipset:&lt;UL&gt;&lt;LI&gt;Driver: Renesas Electronics USB 3.0 Host Controller&lt;/LI&gt;&lt;LI&gt;Driver Version: 2.1.19.0&lt;/LI&gt;&lt;LI&gt;Firmware Version: 3028&lt;/LI&gt;&lt;LI&gt;The NEC/RENESAS is used in the majority of PCI Express USB 3.0 extension cards and on laptop and desktop motherboards for USB 3.0 support.&lt;/LI&gt;&lt;LI&gt;For more information, see:&lt;UL&gt;&lt;LI&gt;&lt;A href="http://am.renesas.com/products/soc/usb_assp/product/index.jsp" name="&amp;amp;amp;amp;amp;lpos=apps_scodevmw : 13" target="_blank"&gt;http://am.renesas.com/products/soc/usb_assp/product/index.jsp&lt;/A&gt;&lt;A class="jive-link-external-small" href="http://am.renesas.com/products/soc/usb_assp/product/index.jsp" rel="nofollow"&gt;http://am.renesas.com/products/soc/usb_assp/product/index.jsp&lt;/A&gt;&lt;A class="jive-link-external-small" href="http://am.renesas.com/products/soc/usb_assp/product/index.jsp" rel="nofollow"&gt;http://am.renesas.com/products/soc/usb_assp/product/index.jsp&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="http://www.station-drivers.com/page/renesas.htm" name="&amp;amp;amp;amp;amp;lpos=apps_scodevmw : 14" target="_blank"&gt;http://www.station-drivers.com/page/renesas.htm&lt;/A&gt;&lt;A class="jive-link-external-small" href="http://www.station-drivers.com/page/renesas.htm" rel="nofollow"&gt;http://www.station-drivers.com/page/renesas.htm&lt;/A&gt;&lt;A class="jive-link-external-small" href="http://www.station-drivers.com/page/renesas.htm" rel="nofollow"&gt;http://www.station-drivers.com/page/renesas.htm&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;PCI Express USB 3.0 cards used in testing:&lt;UL&gt;&lt;LI&gt;StarTech.com PEXUSB3S2 - PCI Express - 2 ports&lt;/LI&gt;&lt;LI&gt;Buffalo IFC-PCIE2U3S2 - PCI Express - 2 ports&lt;/LI&gt;&lt;LI&gt;Western Digital 4060-705065-002 - PCI Express - 2 ports&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Other configurations of the NEC/RENESAS chipset, driver, and firmware are not sufficiently tested and may not function as expected.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Known unsupported USB 3.0 xHCI controller host configurations:&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Any USB 3.0 host controller Chipset other than the&lt;/STRONG&gt; NEC/RENESAS chipset mentioned above.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Apparently my StarTech PEXUSB311A1C PCIe USB and any USB 3.0 host controller Chipset other than the NEC/RENESAS chipset card is unsupported. I wish that this issue was made well known. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does anyone know if there is a way I can get the NEC/RENESAS driver to work with my Asmedia / Startech PEXUSB311A1C USB 3.1 host controller? Even if it would only work at USB 3.0 speeds, I would be willing to install it to get my VMs 3.0 capable.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there any USB 3.1 PCIe card at all that works in VMware on Windows 7 hosts?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 00:50:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-12-USB-3-0-3-1-support/m-p/1387457#M79662</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2016-01-27T00:50:07Z</dc:date>
    </item>
    <item>
      <title>Workstation 12 USB 3.0 / 3.1 support ?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-12-USB-3-0-3-1-support/m-p/1387456#M79661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been using USB 3.0 ports in my Debian Linux (clonezilla) VMs on a mac-mini under Fusion 8. It works great &amp;amp; I need the speed bc I am P2Ving some large HDs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I finally added an AsMedia / Startech USB 3.1 PCI card to my Win 7 host &amp;amp; was surprised to see it was not working in Workstation 12 Pro. Has anyone been able to connect a USB 3.0 / 3.1 port under Workstation 12 Pro?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Workstation Pro 12 Trial&lt;/LI&gt;&lt;LI&gt;Host: Win7 Pro 64 bit&lt;/LI&gt;&lt;LI&gt;Guest: Debian linux (Clonezilla)&lt;/LI&gt;&lt;LI&gt;USB Card: Startech 2 Port USB 3.1 (10Gbs) Card - 1x USB-C, 1xUSB-A - PCIe (part# PEXUSB311A1C) (Asmedia USB Host&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Controller)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My current workaround is to use a USB 2.0 port but some HDs are over 250GB &amp;amp; can take a whole day to clone. Even worse, I am currently cloning a couple of failing HDs with Bad Sectors &amp;amp; would like to get the data off of them asap. They tend to get hot which makes me think USB 2.0 is not really a viable workaround in this case. Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jan 2016 20:31:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-12-USB-3-0-3-1-support/m-p/1387456#M79661</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2016-01-26T20:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: Black screen VMWare workstation 12 pro</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Black-screen-VMWare-workstation-12-pro/m-p/1367352#M78322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had this problem with workstation for the first time today in Workstation 12 iwith a windows VM. Sending a Ctrl+Alt+Del seemed to restore the normal screen instantly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Jan 2016 17:45:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Black-screen-VMWare-workstation-12-pro/m-p/1367352#M78322</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2016-01-02T17:45:29Z</dc:date>
    </item>
    <item>
      <title>WinXP VM will not start if I assign it more than 512KB of RAM</title>
      <link>https://communities.vmware.com/t5/Windows-Discussions/WinXP-VM-will-not-start-if-I-assign-it-more-than-512KB-of-RAM/m-p/2705899#M742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I P2V'd a Physical XM Pro machine that had 1GB of physical RAM installed. &lt;/P&gt;&lt;P&gt;I am using Fusion 8 on a mac mini (El Capitan) with 16GB of RAM to play the XP Pro VM but it will not start if I assign it any more than 512KB of RAM. The machine is very slow. It crawls. How do I fix this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Dec 2015 19:59:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Windows-Discussions/WinXP-VM-will-not-start-if-I-assign-it-more-than-512KB-of-RAM/m-p/2705899#M742</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2015-12-31T19:59:46Z</dc:date>
    </item>
    <item>
      <title>Virtual Serial Port</title>
      <link>https://communities.vmware.com/t5/Windows-Discussions/Virtual-Serial-Port/m-p/1367829#M224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I P2V'd a Windows 7 machine in a doctor's office that has a serial port which is needed to connect to a proprietary Healthcare instrument. The instrument works fine &amp;amp; would be expensive for the office to replace. At the same time it connects to the workstation via a serial port. The Virtual machine appears to connect to the network &amp;amp; most software works great, but in the event the Physical machine fails or we want to upgrade it, I understand that I should order a new machine with a serial port but how to I get the serial port on the virtual machine to know it is supposed to connect to the serial port on the new physical machine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would this be different if I played the VM on VM Workstation Player on a new physical machine as opposed to keeping the VM on a Network drive? If I kept the VM on a Network drive would it still be possible to 'map' the serial port on the VM to the serial port on the new Physical machine? Would the process be easier if I just kept the VM on the HD of the new physical machine that has a serial pot on it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Dec 2015 19:55:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Windows-Discussions/Virtual-Serial-Port/m-p/1367829#M224</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2015-12-31T19:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: Browser Appliance</title>
      <link>https://communities.vmware.com/t5/Virtual-Appliances-Discussions/Browser-Appliance/m-p/296644#M2009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have the same issue with the appliance. I have installed the browser appliance on both VMware Workstation (Win7 host) &amp;amp; on Fusion8 (OsX 10.11 host) &amp;amp; I have no sound on either machines. Both machines can play other VMs with sound without issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Dec 2015 18:02:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Appliances-Discussions/Browser-Appliance/m-p/296644#M2009</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2015-12-26T18:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: Browser Appliance</title>
      <link>https://communities.vmware.com/t5/Virtual-Appliances-Discussions/Browser-Appliance/m-p/296643#M2008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you explain to me how you manually connected the sound hardware so you could play sound on both guest and host simultaneously? I have installed the browser appliance on both VMware Workstation (Win7 host) &amp;amp; on Fusion8 (OsX 10.11 host) &amp;amp; I have no sound on either machines. Both machines can play other VMs with sound without issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Dec 2015 17:58:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Appliances-Discussions/Browser-Appliance/m-p/296643#M2008</guid>
      <dc:creator>shibu_nyc</dc:creator>
      <dc:date>2015-12-26T17:58:49Z</dc:date>
    </item>
  </channel>
</rss>

