VMware Workstation Pro Documents articles

How to configure VMs in VLAN

RDzz — Thu, 31 Aug 2023 07:20:55 GMT

I have a small network having Cisco Switch network, Fortinet firewall and Router.

All different VLANs (2001, 2002, 2003, 2004) are configured at Switch and then VLANs are passed through other switches. IP addresses are pushed through DHCP. All devices are getting IP.

I have a new Windows 11 machine with 128 GB Ram and 12 TB HDD having VM Workstation 16 Pro installed on it.

My requirement is setup new VMs on VMWare Workstation 16 and put VMs in VLAN 2001 and 2002.

Just wondering if it is possible. Please suggest possible solution.

Thank you.

configuring networks, interconnecting machines

ubuntu_cl — Sun, 27 Aug 2023 01:26:18 GMT

Hola comunidad, necesito aprender a configurar redes con wmware workstation pro 17, estoy consultando la documentación:

PDF:

https://docs.vmware.com/en/VMware-Workstation-Pro/17/workstation-pro-17-user-guide.pdf

En línea:

https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-0EE752F8-C159-487A-9159-FE1F646EE4CA.html

Por ser la versión que tengo instalada en el notebook, la idea es recrear una topología de red, máquinas y servicios, pero principalmente interconectar máquinas con un servidor DHCP en pfSence, Firewall con IPS y WAF y Vlans.

Correção de erro na implementação do VCenter 8 no VMWare Workstation

Marratti — Fri, 09 Jun 2023 19:22:50 GMT

Olá caros amigos!

Seguem um breve passo a passo para solução do erro que ocorre ao implementar o VCente 8 no VMWare Workstation.

Erros:

Solução:

1 - Monte imagem do VCenter em seu computador e converta o arquivo .ova para o formato .ovf:

*Execute os comandos abaixo em um prompt, a ferramenta ovftool pode ser acessada direto da mídia montada e definir o destino do arquivo convertido conforme o segundo comando abaixo, já sendo gerado no disco local.

cd d:\vcsa\ovftool

ovftool.exe d:\vcsa\VMware-vCenter-Server-Appliance-8.0.0.10000-20519528_OVF10.ova C:\LAB\VMware-vCenter-Server-Appliance-8.0.0.10000-20519528_OVF10.ovf

Após o término da conversão, pode deletar os arquivos .mf e .ova.

2 - Edite o arquivo .ovf:

Procure o parametro guestinfo.cis.upgrade.import.directory e altere seu valor de false para true e salve o arquivo.

3 - Importe o arquivo ovf em seu VMWare Workstation e seja feliz!

Shared folders between Win10 enterprise host and Win 11 Pro guest (VMWare 15.5)

ThomasLorenz — Mon, 22 Aug 2022 12:03:31 GMT

I enabled the netware sharing in the Win 11 VM but no network drives are present.

I the sharing feature still working with win 11?

Thomas

A garbled log text document always appears when creating a virtual machine

wakinx — Thu, 17 Dec 2020 03:45:42 GMT

HowTo: Recreating a .vmx from the vmware.log file

a_p_ — Fri, 27 Nov 2020 16:26:37 GMT

In case a virtual machine configuration (.vmx) file becomes corrupt for whatever reason, you may see error messages like "Not a valid virtual machine configuration file", or "... syntax error in line X" when you try to start the VM.

VMware KB article "Starting a virtual machine generates a syntax error" provides some options for how to resolve such an issue. However, manually recreating the configuration file is somewhat cumbersome. See https://kb.vmware.com/kb/1003597

The attached batch file automates the task of recreating the .vmx file by simply dragging the vmware.log file and dropping it on the log2vmx.cmd file. The script parses the .log file for the required configuration data, and - if this information is found - creates a new .vmx file in the script's folder. If a .vmx file with the same name already exists, it will be renamed to .vmx.bak.

Note: Please be careful if the VM has active snapshots, i.e. that the recreated .vmx file points to the current snapshot .vmdk !

Proper careful procedure to upgrade Workstation in a production system

Mits2020 — Fri, 19 Jun 2020 16:05:09 GMT

I always wondered where to find this information and in a recent discussion continuum provided a detailed workflow that imho deserves to be included in the Documents Section, especially now that we are in the transition period to WS 20H2:

Re: VMware Workstation upgrade misbehaviour.

SourceHandle of NetBufferList is set to NULL by vmxnet3.sys, which causes abnormal behavior..

gwgwnana — Mon, 16 Mar 2020 04:40:14 GMT

Please understand that my English is not good before starting...

I installed Windows 2019 server on VMWare Workstation.

And I found that there is an critical issue(maybe..?) where the network function is malfunctioning.

The cause is VMWare's vmxnet3.sys driver.

Look at the picture below..

The current state of the WFP layer is FWPM_LAYER_INBOUND_MAC_FRAME_ETHERNET.

The SourceHandle in NBL is NULL.

That is, the NIC information of the packet received from vmxnet3.sys cannot be obtained.

So I am requesting a review of the fix for this bug.

Thanks

Sound Blaster 16 on VMware Workstation 15.5 and VMware Fusion 11.5

dariusd — Fri, 20 Sep 2019 03:46:13 GMT

Emulation of the Creative Labs Sound Blaster 16 (SB16) sound card is now available on VMware Workstation for Windows hosts, VMware Workstation for Linux hosts, and VMware Fusion for macOS hosts. The Sound Blaster 16 emulation is vastly improved from Workstation releases prior to Workstation 15.5, and is entirely new for VMware Fusion 11.5.

Note: Despite these improvements, the Sound Blaster 16 is a legacy device; Ongoing development and support is not guaranteed.

Improvements in this Release

For the first time, VMware Fusion on macOS hosts can emulate the Sound Blaster 16.
Workstation has expanded capabilities on Linux hosts through the addition of ALSA and PulseAudio support to the Sound Blaster 16. OSS support has been deprecated.
The emulated Sound Blaster 16 is now capable of simultaneous PCM/Wave and Adlib FM music output on all supported hosts.
The emulated Sound Blaster 16 now includes an experimental MIDI output which is capable of passing MIDI messages through to the host and/or to an external MIDI synthesizer.

Activating any of these features requires the use of a configuration option (now quite inaccurately named):

sound.opl3.enabled = "TRUE"

Check if your VM already has a config option for sound.virtualDev. If one is not present, create it, otherwise edit the existing entry and set:

sound.virtualDev = "sb16"

Known Shortcomings

Please be aware that MS-DOS programs and games use a wide variety of techniques to detect and manage sound devices, and it is not possible to guarantee compatibility or functionality when used with the emulated Sound Blaster 16. Programs may vary in their support for hardware music and sound devices.

Shortcomings in PCM/Wave Playback and Recording

Some legacy/compatibility commands and formats used by the Sound Blaster, Sound Blaster Pro and Sound Blaster Pro 2 are not implemented in the emulated Sound Blaster 16; Programs which pre-date the SB16 or do not recognize the sound card as an SB16 might be unable to play audio or might fail in other ways.
- Known failures: Brøderbund Software's Prince of Persia.
The timing of internal events related to playback and recording might differ from that of a physical SB16. If this timing is wrong, the likely result will be sound playback/recording with repeating ticks or clicks throughout.
- Known failures: Future Crew's Unreal Demo, Windows 95 playing/recording at 22 kHz or higher.
Audio latency for playback and recording is not optimal and is most likely higher than a physical Sound Blaster 16. It should be adequate for casual use.

Shortcomings in Adlib/OPL3 FM Music Synthesizer

Rhythm instruments are not implemented.

Shortcomings in Audio Mixer Controls

Legacy/compatibility mixer controls are not implemented. Programs which pre-date the SB16 or do not recognize the sound card as an SB16 might be unable to adjust mixer levels.
PC Speaker level control is not implemented.
Bass/Treble controls are not implemented.
Hardware audio loopback is not implemented, so it is not possible to use the Sound Blaster 16 to record its own output.

New Feature: MIDI Output

This facility is double-super-duper-experimental and is disabled by default, but is also double-super-duper-cool. Remember that MIDI dongle that could plug into the Sound Blaster 16's Game Port? This is that. To try it out, edit a powered-off VM's configuration file to add

sound.mpu401.host = "TRUE"

Caveats:

Only output is supported; There is no capability for the emulated Sound Blaster 16 device's MIDI IN port to receive MIDI data from the host. Any MIDI SysEx messages originating from the VM are not forwarded to the host; They will be ignored. As a result, the MIDI output capability will be usable for music playback from games and other programs inside the VM, but is unlikely to meet more complex needs.
MPU-401 MIDI UART mode is the only supported output mode. Thankfully it is also by far the most widely-supported mode.
- The Sound Blaster 16's legacy SB-MIDI mode is not implemented.
- MPU-401 Intelligent mode is not available on a physical SB16 and is also not available in the SB16 emulation.

Behavior of MIDI Port during Connect/Disconnect, Suspend/Resume

The SB16 MIDI output will only attempt to connect to a host MIDI service at the moment that the virtual machine is powered on or resumed, or at the moment the Sound Card is toggled to Connected in the Workstation or Fusion user interface. If no host MIDI device is available at that time, the SB16 MIDI output will remain disconnected. If the host MIDI device becomes unavailable during use, the SB16 MIDI output will be disconnected and no attempt will be made to reconnect. As a result, if a software synthesizer (see below) is terminated and relaunched, it might be necessary to take additional actions (e.g. disconnecting and reconnecting the Sound Card, and/or running aconnect again on a Linux host) before MIDI output is active.

Suspending or powering off a VM will not perform any "cleanup" of the MIDI output; If the MIDI output is in active use, lingering notes are likely. It is therefore recommended that the VM be put into a state where it is not actively using its MIDI output before it is suspended or powered off. Similarly, resuming a VM will not attempt to restore the prior state of the host MIDI device. If the host MIDI device's state has been changed since the VM was suspended, results will be unpredictable.

Configuring your host to handle MIDI output

Using MIDI output with VMware Workstation on a Microsoft Windows host

VMware Workstation will send MIDI messages to the default host MIDI device, which is likely to be the Microsoft GS Wavetable Synthesizer. Recent versions of Windows appear to require a 3rd-party tool to direct the MIDI output to any other MIDI device.

Using MIDI output with VMware Workstation on a Linux host

VMware Workstation will send MIDI messages to an ALSA virtual rawmidi device created for that purpose. After the VM is powered on, you may need to use aconnect command on the host to direct the MIDI messages output by the virtual machine to a software synthesizer or external MIDI device. Refer to the manpage for aconnect for further details.

Other MIDI programming interfaces are not presently supported.

One option for rendering MIDI output into audible music is FluidSynth. As usual with Linux, you have an abundance of ways to configure things; You may need to refer to documentation from your Linux distribution or from the FluidSynth, ALSA or PulseAudio projects. You might even need to refer to the source...

Here is how it works on my Debian 9 amd64 host:

If you haven't already done so, install the fluidsynth and fluid-soundfont-gm packages as follows:

sudo apt-get install fluidsynth fluid-soundfont-gm
To launch the software synthesizer, retrieving its inputs from the ALSA sequencer and rendering audio to the host's PulseAudio sound server:

fluidsynth -m alsa_seq -a pulseaudio /usr/share/sounds/sf2/FluidR3_GM.sf2
Power on your VM.
Run aconnect -l to see which sequencer clients are running. In my case, it looks like this:

dariusd@host:~$ aconnect -l
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 128: 'TiMidity' [type=user,pid=622]
    0 'TiMidity port 0 '
    1 'TiMidity port 1 '
    2 'TiMidity port 2 '
    3 'TiMidity port 3 '
client 129: 'FLUID Synth (2143)' [type=user,pid=2143]
    0 'Synth input port (2143:0)'
client 130: 'Client-130' [type=user,pid=3127]
    0 'Virtual RawMIDI '
dariusd@host:~$

Client 129 is FluidSynth ready to receive MIDI input, and client 130 is the SB16 MIDI output from the virtual machine. To connect them, specify the VM's output port first and the synthesizer's input second in the following command:

aconnect 130 129
Run your SB16 MIDI program inside the virtual machine. FluidSynth will render the MIDI to audio.

Note that aconnect -l will show the current connections, so once things are connected successfully, it should look something like this:

client 129: 'FLUID Synth (2143)' [type=user,pid=2143]

0 'Synth input port (2143:0)'

Connected From: 130:0

client 130: 'Client-130' [type=user,pid=3127]

0 'Virtual RawMIDI '

Connecting To: 129:0

Note also that connections made by aconnect are not persistent; Each time the VM or the synthesizer are relaunched, the connection must be re-established. There's probably some way to make them connect automatically, but I haven't yet discovered it.

Using MIDI output with VMware Fusion on a macOS host

VMware Fusion will send MIDI messages to the macOS CoreMIDI service. There is no built-in facility for directing the MIDI messages to a particular device.

One option for rendering MIDI output into audible music is FluidSynth, which for example can be installed through HomeBrew:

Run the command: brew install fluid-synth
Fetch a SoundFont, e.g. from the page at https://github.com/urish/cinto/blob/master/media/FluidR3%20GM.sf2 , and put it in some shared location, e.g. /usr/local/share/fluidsynth would do nicely.
Launch the synthesizer with the command: fluidsynth -o midi.autoconnect=1 /usr/local/share/fluidsynth/FluidR3\ GM.sf2

The SB16's MIDI output should now be audible through the host's default audio output device. Refer to the FluidSynth documentation for further detail.

Configuring your guest to produce MIDI output

Using MIDI output with MS-DOS guest games and programs

Look for a SETUP.EXE or some other configuration program which can be used to select sound and music output. If possible, choose General MIDI or MPU-401 or Roland MT-32 for the output device. If an I/O port must be specified, use 330 – typically that is the default anyway. Using DOOM as an example, run SETUP.EXE, select Choose Music Sound Card, and choose General MIDI, and choose 330 as the MIDI port.

Some programs will use command-line arguments to specify the sound system, such as specifying m for MPU-401 or r for Roland MT-32. Using the LucasArts Day of the Tentacle demo as an example, run dottdemo r to launch the demo with MIDI music – versus dottdemo a to use Adlib/OPL3 music.

For further information, refer to your program's command-line help or documentation.

Using MIDI output with Microsoft Windows 95 as a guest OS

With the Creative Labs Sound Blaster 16 or AWE-32 driver installed in the Windows 95 virtual machine, go into the guest's Control Panel > Multimedia, and go to the MIDI tab. With Single Instrument selected, you should be able to choose between MIDI for External MIDI Port (which will use the Sound Blaster 16's MPU-401 interface and send MIDI to the host) and MIDI for Internal OPL2/OPL3 FM Synthesis (which will use the Sound Blaster 16's Adlib/OPL3 emulation to render MIDI into audio).

Windows Media Player will use the MIDI settings in Control Panel when playing back MIDI files. Try it out using the CANYON.MID and PASSPORT.MID files included with Windows.

Acknowledgements

These Sound Blaster 16 emulation improvements would not have been possible without the patient support of my sound-enthusiast colleagues, most notably Kamen – who helped with countless code reviews – and my manager Richard, who can finally play DOOM with sound and music. Many others provided quiet encouragement and feedback to help along the way.

workstation 15 pro running vm guest regularly crashes

MelodyHSU — Mon, 16 Sep 2019 05:47:37 GMT

my computer workstation 15 pro running guest os windows 2003 regularly crashes , log file list :

2019-09-16T00:17:20.051+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2019-09-16T00:17:20.076+08:00| mks| I125: SWBWindow: Window #0 validation failed: no valid host window or host surface.

2019-09-16T00:17:20.076+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #0 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:17:20.081+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.

2019-09-16T00:17:20.081+08:00| mks| I125: SWBWindow: Window #1 validation failed: no valid host window or host surface.

2019-09-16T00:17:20.081+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #1 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:17:20.083+08:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2019-09-16T00:17:20.083+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2019-09-16T00:17:22.563+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2019-09-16T00:17:22.563+08:00| mks| I125: GDI-Backend: successfully started by HWinMux to do window composition.

2019-09-16T00:17:22.575+08:00| mks| I125: MKS-HWinMux: Started GDI presentation backend

2019-09-16T00:17:22.576+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2019-09-16T00:17:38.770+08:00| vcpu-0| I125: VMMouse: CMD Read ID

2019-09-16T00:17:53.830+08:00| svga| I125: MKSScreenShotMgr: Taking a screenshot

2019-09-16T00:17:53.900+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2019-09-16T00:17:53.950+08:00| mks| I125: SWBWindow: Window #0 validation failed: no valid host window or host surface.

2019-09-16T00:17:53.950+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #0 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:17:53.958+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.

2019-09-16T00:17:53.959+08:00| mks| I125: SWBWindow: Window #1 validation failed: no valid host window or host surface.

2019-09-16T00:17:53.959+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #1 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:17:53.962+08:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2019-09-16T00:17:53.962+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2019-09-16T00:17:54.715+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-09-16T00:17:56.186+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2019-09-16T00:17:56.186+08:00| mks| I125: GDI-Backend: successfully started by HWinMux to do window composition.

2019-09-16T00:17:56.200+08:00| mks| I125: MKS-HWinMux: Started GDI presentation backend

2019-09-16T00:17:56.202+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2019-09-16T00:18:18.994+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-09-16T00:18:29.817+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-09-16T00:20:23.778+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-09-16T00:20:55.099+08:00| svga| I125: MKSScreenShotMgr: Taking a screenshot

2019-09-16T00:20:55.176+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2019-09-16T00:20:55.245+08:00| mks| I125: SWBWindow: Window #0 validation failed: no valid host window or host surface.

2019-09-16T00:20:55.245+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #0 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:20:55.253+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.

2019-09-16T00:20:55.253+08:00| mks| I125: SWBWindow: Window #1 validation failed: no valid host window or host surface.

2019-09-16T00:20:55.253+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #1 because an invalid MKSWindow definition is recevied from UI over VMDB.

2019-09-16T00:20:55.258+08:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2019-09-16T00:20:55.259+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2019-09-16T00:20:56.350+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2019-09-16T00:20:56.350+08:00| mks| I125: GDI-Backend: successfully started by HWinMux to do window composition.

2019-09-16T00:20:56.356+08:00| mks| I125: MKS-HWinMux: Started GDI presentation backend

2019-09-16T00:20:56.357+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2019-09-16T00:21:01.267+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-09-16T00:21:06.054+08:00| vmx| I125: VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOff without reset, soft, softOptionTimeout: 20000000.

2019-09-16T00:21:06.054+08:00| vmx| I125: Tools: sending 'OS_Halt' (state = 1) state change request

2019-09-16T00:21:06.054+08:00| vmx| I125: Tools: Changing running status: 1 => 2.

2019-09-16T00:21:06.054+08:00| vmx| I125: Tools: [RunningStatus] Last heartbeat value 1178070 (last received 0s ago)

2019-09-16T00:21:06.145+08:00| vmx| I125: TOOLS state change 1 returned status 0

2019-09-16T00:21:06.145+08:00| vmx| I125: Msg_Post: Error

2019-09-16T00:21:06.145+08:00| vmx| I125: [msg.tools.haltFailed] The request to Power off this virtual machine failed because the corresponding VMware Tools script did not run successfully. If you have configured a custom power-off script in this virtual machine, make sure that it contains no errors. Attempting the operation again will ignore the script failure. You can also submit a support request to report this issue.

2019-09-16T00:21:06.145+08:00| vmx| I125+

2019-09-16T00:21:06.145+08:00| vmx| I125: ----------------------------------------

2019-09-16T00:21:08.059+08:00| vmx| I125: Vix: [mainDispatch.c:4150]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

2019-09-16T00:21:08.065+08:00| vmx| I125: Tools: Changing running status: 2 => 1.

2019-09-16T00:21:08.065+08:00| vmx| I125: Tools: [RunningStatus] Last heartbeat value 1178071 (last received 0s ago)

2019-09-16T00:21:08.123+08:00| vmx| I125: sata0:0: Command *UNKNOWN (0x4a)* took 1.999 seconds (ok)

2019-09-16T00:21:08.126+08:00| vcpu-1| I125: Tools: Unable to send state change 1: TCLO error.

2019-09-16T00:21:16.124+08:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Workstation V15.1 has a trouble!

efa8888 — Mon, 12 Aug 2019 01:56:52 GMT

I have installed the Workstation Pro V15.1, and I want to create a new virtual machine. When the software worked at hardware configuration step, I modified the display memory size from 1GB to 3GB,then I push the enter button, the software give a message 'Unknown fault". I can not operate the software, can not close the fault message window and can not operate next step.

Win 10 18309.1000 和 VMware Workstation Pro 15.0.2兼容问题

zb9525 — Thu, 10 Jan 2019 15:26:05 GMT

你好

我发现在Win 10 18309.1000 使用VMware Workstation Pro 15.0.2时

拷贝文件到VMware Workstation中时，大概率会出现假死，VMware Workstation所有操作无反应。

故障多次出现。

谢谢

asyncsocket error when starting a shared vm in Workstation 14

H3X0X55AA — Sat, 01 Dec 2018 02:38:23 GMT

Can't start any share vm. Please help!

Recovering from error message during Workstation upgrade on Linux host when port 443 is unavailable.

yrona — Fri, 25 May 2018 13:26:08 GMT

The installer to upgrade from VMWare Workstation 14.0 to 14.1.12 hits a snag when the installer checks whether the port 443 is available on the local host for the service to listen to. It appears that the installer does not properly shutdown the process vmware-hostd earlier in the install, and so it prompts the user for a different port number.

The simple fix when encountering this error is first to check what is listening to that port:

Execute the command

sudo netstat -pan | grep 443

The first result will tell you what process is using that port:

tcp

0 0.0.0.0:443

0.0.0.0:*

LISTEN

3757/vmware-hostd

Obviously in this case we simply need to stop the vmware-hostd process. If something else is listening to that port, you can identify an open port and provide that value. Otherwise simply kill the offending process and then continue forward:

sudo kill -9 3757

crash when it works on fedora kernel 4.13.x

C0Jack — Sun, 03 Dec 2017 14:25:54 GMT

The vmware workstation will crash when it works on fedora kernel 4.13.x

Can't import OVA files anymore

baettiggroup — Tue, 28 Nov 2017 15:47:14 GMT

Hi all

Every time I want to import an ova file I get the message, that I need to contact support. Attached the pointed logfile.

I already have uninstall cleand and installed VMWare Workstation 14.0.0 build-6661328

Thanks in advance for any hint.

Best Markus

Broken_Chrome.PNG with running VMware Tools

yuriabele — Fri, 11 Aug 2017 16:30:46 GMT

Hello!

I have a problem with displaying of some applications if VMware tools are working.

For example a Google Chrome Tabs are not visible.

If I stop or uninstall a VMware tools they are visible again.

20170719_084214.jpg

Lev115 — Wed, 19 Jul 2017 17:16:30 GMT

Hello,

I found a bug: in the Stretch mode, when changing the resolution of the guest os, the image is cropped

vmsupport-2017-06-28-17-26.zip

nloehr — Wed, 28 Jun 2017 15:47:59 GMT

VMware Workstation 12 Pro 12.5.7 build-5813279 crashes after starting eCAD program. The behavior is reproducible with every start of the eCAD System Altium Designer. Please advice. Help urgently needed.

I am unable to start vmware workstation

moon_yon — Sat, 24 Jun 2017 12:59:09 GMT

I could not start service vmware on my fedora 26 beta ,run command "service vmware status" it says vmmon not loaded,vmnet not loaded.run command "vmware-modconfig --console --install-all" it says Failed to get gcc information.but my gcc is ok for other situations.