Hi i have a problem with my virtual machine,

i have a host ubuntu 12.04

and a guest ubuntu 12.04.

The guest crash with this error :

2017-06-14T20:02:02+01:00[+78.702]| vmx| I120: Msg_Post: Error

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vmx)

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120+ Unexpected signal: 11.

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: [msg.panic.haveLog] A log file is available in "/home/gestore/vmware/server-proia/vmware.log".

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: [msg.panic.requestSupport.withoutLog] You can request support.

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120+ You can also run the "vm-support" script in the Workstation folder directly.

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: [msg.panic.response] We will respond on the basis of your support entitlement.

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: ----------------------------------------

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110: POST(no connection): msg.panic.response

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ VMware Workstation unrecoverable error: (vmx)

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ Unexpected signal: 11.

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ A log file is available in "/home/gestore/vmware/server-proia/vmware.log".

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ You can request support.

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ You can also run the "vm-support" script in the Workstation folder directly.

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110+ We will respond on the basis of your support entitlement.

2017-06-14T20:02:02+01:00[+78.703]| vmx| W110:

2017-06-14T20:02:02+01:00[+78.703]| vmx| I120: Exiting

Can you Help me?

I'm suffering from the condition where I updated my VM from Windows 8.1 to Windows 10 and am now getting a blank screen upon boot up.  I know from other articles that this is because the VMWare tools installed (specifically the video driver) is incompatible with Windows 10.  To solve this, I have to go into safe mode to remove the video driver and install the latest VMWare tools.

The problem I am having is that I can't get the VM booted into safe mode!  I have the Windows 10 installation ISO mounted to the drive, I've slowed down the bios so I can access the boot menu, and now easily access the boot menu...but when I choose CD-Rom, it continues to load into windows 10 main and present me with a blank screen.

Does anyone have any tips how to get Windows 10 into safe mode when it is in a VM? I've tried other .isos too...I even created an ISO from my USB recovery drive without luck.

Any assistance would be greatly appreciated!

-Spurk

(I'm going to apologize up-front for how long this is, but I appreciate any kind of help. I am not an advanced user of Vmware Workstation 12, so please take it easy on me haha. Thank you.)

Long story short, I have an 8tb WD Red internal hard drive. I had an Ubuntu 16.04.2 virtual machine stored on it which had a very important password list of mine. (I know, it's stupid to not have it backed up, but this is my issue.)

The hard drive became corrupt. Luckily, I was able to use both of my recovery software (EaseUS Recovery and Recuva) and it seems to be able to recover any file I need.

I downloaded every single file I could possibly find that started with Ubuntu 16.04.2 but the virtual machine will not start.

I'm starting to panick since this is extremely important, I would really appreciate anyone's help if at all possible. Thank you.

Below are all of the recovered files I recovered through EaseUS after reading an article on which files needed to start up the VM again, but I'm sure I'm missing something.

I don't know what anyone would need to possibly help me, so I'll also include the log text incase that helps.

Once again, thank you for any kind of help.

I keep getting prompted to change the keyboard hook timeout value even though I select the option to "Do not show this message again".  I've tick the do not show again box and then click cancel 'leave it unchanged' because I do not want to change the LowLevelHooksTimeout level value on my host machine.

I am having an issue where when I power on a client, one of 3 things will happen :

1) Client starts normally

2) I get a VMware initializing screen, that will stay forever. All options to this client will be greyed out, this is the most common.

3) Black Screen, I can't see what is going on, but inputs are available, rare

In 2) & 3), if I try to close the VMWare workstation window from taskbar, I get a "Virtual Machine is busy" message

If I kill the VM workstation from task manager, it will be killed and when I restart the VM workstation, I will see that client already powered on and running normal.

There is no time from the kill to restart of VM workstation for the client to have reached that stage of startup,

so the only conclusion is that the client runs fine when I initially power on, but the workstation GUI failed to connect to it properly.

Once the VM workstation GUI connects to the VM clients, it works fine even I reboot the client multiple times.

Host OS is responsive throughout.

Any idea what might be causing the issue ?

My host is Windows 10 Pro 1703, with 24GB ram.

VM Workstation Pro version is 12.5.6 build 5528349

Clients include windows 7 SP1, 10 1703, Server 2012 R2 and CentOS 7

Hi,

I have a similar problem as  "Out of Memory" errors after Windows 10 Creators Update .

I am running VMWare 12.5.5.5234757 on Win10 Build 16179 (Quadcore 3,3 GHz 16 GB Ram).

Since Build 16176 all guests (Win10, Server2003) crash after ~30-60 min without any error window. It makes no difference if I am working on the guest or not.

In the vmware.log I see the following lines:

2017-04-23T11:49:07.006+02:00| vcpu-1| E105: PANIC: Semaphore 984 wait failed: 257

2017-04-23T11:49:07.006+02:00| vcpu-1| I125: Panic: can't get userlevel lock.

2017-04-23T11:49:07.006+02:00| vcpu-1| W115: Win32 object usage: GDI 10, USER 19

2017-04-23T11:49:07.006+02:00| vcpu-1| I125: CoreDump_CoreDump: faking exception to get context

2017-04-23T11:49:07.011+02:00| vcpu-1| I125: CoreDump: Minidump file D:\Virtual Machines.VMWare\VM-Win10_x86_DE\vmware-vmx.dmp exists. Rotating ...

2017-04-23T11:49:07.032+02:00| vcpu-1| W115: CoreDump: Writing minidump to D:\Virtual Machines.VMWare\VM-Win10_x86_DE\vmware-vmx.dmp

Before the build 16176 I never had this problem.

I attached the logfile and vmcore-dump.

Virtual printing is disabled.

Edit: Link to logfiles Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

VMware Workstation unrecoverable error: (vcpu-0)

vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:386 bugNr=1036521

A log file is available in "D:\Virtual Machines\FraudFox\vmware.log". 

You can request support. 

To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

I get this error whenever i try to start any of my VMs, i have managed to make them run before on the same computer however i recently upgraded cpu gpu and motherboard and since then it didnt work ( i reinstalled os but its the same ( win10 ))

I got an i7 7700k 4.2ghz, a GTX 1070 and an asus z270-f, running on vmware workstation pro. thanks in advance

We have several Windows hosts running Workstation 12.  We have several VMs who's guest OS is Windows 10 (hereafter called just "Win10 VMs").  The Win10 VMs run fine on all hosts, except 1.

Please review the following and advise how we may successfully run Win10 VMs on this failing host?

When Win10 VMs are run on the failing host the error displayed by VMware Workstation is:

"A fault has occurred causing a virtual CPU to enter the shutdown state ... "   [See attachment for screen capture of full error message]

Attached is vmware.log from one such failure.  The attached vmware.log is from a Win10 VM with guest OS 32-bit Windows 10 Pro.

The problem host is running 64-bit Windows 7 Home Premium.  Processor: Intel Core i7 CPU.  VMware Workstation 12.1.0.  This host runs all other VMs fine.  The only problem (yet) known is when guest OS is Windows 10.

Any suggestions would be appreciated regarding how we may successfully run Win10 VMs on this failing host?

Thanks,

g

Some time ago I created a virtual machine on windows 7 under vmware workstation and configured it as a shared vm with autorun.

Now everything works, but the workstation does not show this working machine in Shared VMs.

Who can tell where to look, and what to correct to see again?

Hello,

I have workstation 12.5 Pro and all guests are very slow lately, even enetering the bios is slow. I have a powerful i7 CPU with 16GB RAM, Win7 Pro. It used to be very fast before and worked without any problems. But a few days ago it began to be slow just by itself and I don't know why. I already tried to reinstall vmware, run it under a different user, create new guests, change hw compatibility, change other hw related settings for the guest machine, turning off antivir but it makes no difference.

Here is the video https://sendvid.com/l6e624wa

any ideas what to do?

I have a question I am new to workstation. I have bridged vmnet1 and 2 to 2 interfaces on a server. Can you only use that bridge for 1 VM? I have it assigned to an adapter on 192.168.20.0/24 . I have one vm which I bridged and gave it IP 192.168.20.101 and I am trting to create a new one with the IP .102. It wont work. Before I screw with everything thought I would ask. THanks

Hi Team,

I have an issue with vmnet0, whereby vmnet0 is not showing up in "ifconfig -a". This is my environment:

Host: Ubuntu 14.04

VMware Workstation version 11.1.2

This started happening about 2 weeks ago: when starting a VM that uses the bridged interface, it comes up with the error message "The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down."

When looking at "vmware-netcfg", all settings are as they have always been. Specifically with respect to the bridged connection: it is bridged to "Automatic" and the "Automatic Settings..." have a tick for each interface on my system. The line item for vmnet0 shows:

Name: vmnet0

Type: bridged

External Connection: auto-bridging

Host Connection: ---

DHCP ---

Subnet IP Address: ---

I have also tried to force the bridging onto a specific interface, by changing the automatic settings to a specific interface. This does not resolve the issue.

I decided to upgrade VMware Workstation to version 12.5.6, hoping the issue would get resolved that way. This did not make a difference.

I then decided to wipe out my hard drive and install Ubuntu 16.04.2. After the installation, I installed VMware Workstation 12.5.6. Doing all this, also did not resolve the issue.

I found that the vmnet-bridge process is running:

$ ps aux  | grep vmnet-bridge

root     21321  0.0  0.0   7004   196 ?        Ss   13:25   0:00 /usr/bin/vmnet-bridge -s 12 -d /var/run/vmnet-bridge-0.pid -n 0

However, while researching this issue, I found that sometimes you have to manually run:

/usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet0.pid /dev/vmnet0 vmnet0

After running this, I can see the vmnet0 interface listed in the output of "ifconfig -a", however I cannot seem to use it.

BTW, I got the above from this link: networking - Bridged virtual interface is not available or visible to ifconfig - Server Fault

Some other info: /dev/vmnet0 exists.

Not sure what to do anymore at this stage. Any help is greatly appreciated.

Marc.

Hallo VMware-Community,

ich habe folgende technische Voraussetzungen:

ESXi Server:

Version: 1.8.0

Build-Nummer:4516221

ESXi-Version: 6.5.0

ESXi-Build-Nummer: 4887370

Workstation Windows Host: Windows 7 64 Bit

Workstation Linux Host: Kubuntu 17.04 (Kernel 4.10.0-21-generic) 64 Bit

Workstation: 12.5.6 build-5528349 (bei beiden)

Nun zu meinem Problem:

Unter dem Linux Host kann ich durch Workstation problemlos auf den ESXi Server zugreifen und vollumfänglich nutzen. Jedoch unter Windows funktioniert dies nicht vollständig. Ich kann die Verbindung aufbauen und sehe auch alle bereitgestellten VMs, kann diese auch starten und verwalten aber nicht mit Maus und Tastatur bedienen. Auch das „Upgrade auf VM-Kompatibilität“ und die Neuinstallation der VM-Ware Tools führte nicht zum Erfolg. Ich kann den Fehler leider nicht nachvollziehen, deshalb bitte ich hier um Unterstützung.

Grüße

Stefan

I installed two system "CentOs 7" as virtual systems on Vmware workstation , after I installed the second os I see the networking is not working on both machines, I guessed this issue happens because the both machines with the takes the same name of network card ex: ens33 , I was configured the network on first machine manually (IP address , Netmask, Gateway and DNS) , after the problem happen I reset all configuration to Automatic (DHCP), but also the network not working, but when I trying to ping another machine I see the packets are sent successfully

this current setting

Hello Community,

As i can't log a support ticket to VMware I am reporting this via the community.

I have a Lenovo P50 machine with 1TB SSD and 64GB DRAMM.

I am running for a long while some company specific linux based software (we have OVA files)
Since the upgrade to 12.5.6 build-5528349 I experience crashes of the VMware instances.

I have log files of that which I can only share with VMware direct and not to a forum like this.

However I would like to hear if others reported crash upgrading to 12.5.6 build-5528349.

I can from version 12.5.5

Brgds,

B

as.

I recently installed Workstation 12 on a Windows 10 workstation 64-bit running STAF (Software Testing Framework) to create a virtual 32-bit system.

I do realize the this is 3rd party open source software but this has been integrated into all our event driven systems.

Bottom-line VmWare will lose that battle if I cannot resolve this particular issue.   :-(

When the system is re-started the STAF program will no longer initialize and returns the following error:

Error on Interface definition line:

interface ssl library STAFTCP option Secure=Yes option Port=6550

Error code: 47

Reason    : Error creating interface.  STAFConnectionProviderConstruct: Could not determine logical/physical identifier.Error code: 22  Reason: Error getting hostent structure: gethostbyaddr() RC=11004

Error in configuration file: C:\staf\bin\STAF.cfg

Jimm

Has this issue be brought up? or are there any suggestions...

BTW: disabling the VM network interfaces on the Windows 10 host allows STAF to operate again correctly..

Recently, back in March 2017, I built a new computer and put Windows 10 Pro as the host OS.

Once I worked out the hardware and software issues of the build, I installed vmWare Workstation Pro 30 day trial.

I installed 3 OS's onto Workstation Pro, Windows 7 Pro, Windows XP Pro SP3 and Ubuntu Mate 16.04 LTS

I configured all the above OS's to suit my needs and used the bridged network mode because of of specific router needs I have in my home network.

Once I was comfortable with the above OS's configurations, I ran them to observe how stable vmWare would be over the duration of the 30 day trial period.

Everything ran stable as I had hoped for the duration of the trial period. Awesome.

However, I did not purchase a license until June 10, 2017, thereby activating vmWare but not using it until Yesterday, Sunday June 18, 2017.

In between the time of the trial period ending and the license activation, Windows 10 Pro updated at least 1 time, possibly 2 times. I would need to check the update logs.

When I finally fired up vmWare yesterday, I was given an error message (I don't recall exactly the pop up window's message) about the mouse/keyboard not being properly connected to the host, so it could possibly lead to delays in typing and/or poor mouse responses.

Another error occurred with the network interface. The host could not connect to the VMs in any case, bridged or NAT, the VMs would not recognize the network interface.

Immediately, I thought something was corrupted with vmWare and did a reinstall/repair of vmWare which solved all of the above problems. I did not install any programs during the interim that could have lead to vmWare's problem.

I did notice that the last Windows 10 update managed to completely stop the daily changing picture for the lock screen. It did change some privacy settings I had as well.

My question is: Is it possible that Windows 10 updates are corrupting programs such as vmWare, or is there some other reason for vmWare to have been corrupted in some way?

Добре!

Хотел обновиться с десятой vmware workstation на 12.5 pro на сайте пишут $149.99 и она ваша.. но не тут то было. Нажимаю на сайте "обновление", "приобрести", выбираю старую 10 версию из "плюсика", жму "добавить в корзину" и получаю радостное "валюта не поддерживается".

P.S. Замечу, что если нажать на приобрести полную за $249.99 то после нажатия "приобрести" открывается форма для ввода данных кредитки. такие дела.

Звонил в наше представительство, они сказали что не занимаются на сайтом вообще ни воркстейшеном в частности, "мы вам не поможем, напишите на форуме", вот пишу.

i was searching trying to solve this problem but nothing, the problem is that i cant copy any file from the guest and paste in the host.

I try to uninstall the vmware tools and install it again and nothing, reinstall vmware tools and nothing.

it happens when i try to copy text or files, any text and any size/type of files.

but, when i try to copy any file/text from de host to the guest it copy in the VM.

it is a problem of my host? vmwaretools? vmware workstation?

Host: Windows 7 64bits

Guest 1: Windows 7 64bits

Guest 2: Windows XP.

Yes. I have checked on Ubuntu 16.04.2 latest version and Windows 10 latest version. It just won't play videos (.mp4 and .avi at least i tried) can anybody please also confirm that? or maybe any suggestions on how to fix it will be greatly appreciated. thanks.

details: I have installed the official iso from msdn (March 2017 updated iso). This wasn't a result of any sort of upgrade. just clean install of 1703 version (OS Build: 15063.413) of windows.