I have a Win7 machine in Workstation 15 that is causing my host machine's network port to die.

I can ping a device on the network from the base machine and as the VM is powering up the pich request times out.  I've tried reinstalling VMWare, restoring an old VM (that I know used to work perfectly), changing to Bridged, reinstalling VMWare tools and nothing fixes the problem.  The WiFi connection stays working correctly; it's only the physical network port that's "passing away".  Any assistance would be greatly appreciated!

Thanks in advance!

-e-

I'm experiencing a triple-fault while booting an OS of my own creation.  I have "Gather debugging information" set to "full".  VMware is failing to generate the suspend and memory files needed to generate a debug core dump file via vmss2core.

According to dariusd's comment in VMWare workstation monitor.suspend_on_triplefau... |VMware Communities , two files of the form debug.guest should have been created.

I've attached my vmware.log file.

Hi,

I'm having some trouble with vmware, i'm running a nested hypervisor (one which i devloped) within vmware workstation, and sometimes i receive the following message

VMware Workstation unrecoverable error: (vcpu-0)

vcpu-0:ASSERT vmcore/vmm/cpu/segment.c:679 bugNr=19580

A log file is available in "/home/asaf/vmware/Ubuntu/vmware.log". 

You can request support. 

I know this is a bug in my hypervisor, but i was wondering if someone from the vmware team or anyone else who knows, could tell me what kind of assertion had faild.

thanks.

Just reporting a minor bug I've consistently noticed in the last several releases of VMware Workstation. From the Virtual Machine Settings page -> Network Adapter (any if multiple) -> Advanced. Dismissing the Network Adapter Advanced Settings dialogue always requires two clicks of the OK button. The first click is seemingly ignored, though the OK button does highlight on mouse-over, while the second click works as expected. I've not noticed this issue on any other VMware Workstation dialogue.

Like I said, minor, but hopefully an easy fix that can be implemented in a future release!

Hi all,

Certain applications use codec to receive images being streamed, decode video, and display video, which works normally on normal windows PCs. However, Windows , which is configured with the same environment in the vmware workplace, cannot read the codec or run normally. What is the cause?

My environment

Guest os : windows xp 32bit/ vmware workstation pro .

host os : windows 10

The computer the application is working correctly is also Windows xp 32bit

Hi,

Anyone have experience why the VM with Windows Server very slow during boot-up after reboot.

I have reboot total 250 VM servers in 2 hour.

I am using VMWare Workstation 15. Related to a project for some young people learning I would like to show a working version of Windows 3.1 and Window 95. Will this be possible with Workstation 15? Thanks

Hello,

I have a VM with Windows XP as guest on a linux host. The VM is connected to the parallel port, which I need, because I have a parallel dongle that some older software in the VM needs.

The VM crashes on startup with following error message:

VMware Workstation unrecoverable error: (vcpu-0)

Unexpected signal: 11.

A log file is available in "/var/local/vm/Windows XP Professional/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.

If I make the parallel port unavailable for the VM, with the command "sudo modprobe lp", before I start the VM, then the VM starts just fine. So it is definitely the parallel port that is the problem.

The VM worked (with access to the parallel port) with Workstation 12.

I have attached my vmware.log from the crash.

Any help is greatly appreciated.

Adam

hello

I would like to ask about the error(?) while using vmware workstation14

After vm has recognized the keyboard A (does not work on the host), under is compared when it is in unity mode and when it is not

not unity

cursor in host , A can typing!

in unity mode

cursor in host , A can`t typing!

Can I make the keyboard work even if the cursor is on the host in unity mode?

plz, help me

I think that there is something wrong in the installation of Workstation Server component. I'm trying to start it through services in Windows, but I am unable to do so (Service cannot start) because the configuration files are really not well-formed:

This is form the hostd log:

2018-11-07T11:15:42.354+01:00 panic hostd[04896] [Originator@6876 sub=Default] error: class Vmacore::Xml::XMLParseException(not well-formed (invalid token))

If I look into the files in ProgramData\hostd\*.xml . some of them are binary, so definitely not a correct format. I tried to reinstall (Workstation 14) and also upgrade to Workstation 15.

What can I do know?

Author : Andy Mann

URL : http:////docs.vmware.com/cn/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-47B91650-BCBE-49EE-997B-91AA0DBBAF04.html

Topic Name : 获取 Workstation Pro 软件和许可证密钥。

Publication Name : 使用 VMware Workstation Pro

Product/Version : VMware Workstation Pro/15.0

Question :

    单用户许可，更换电脑后如何注册                                                      How to register after changing a computer with a single user license?

Hi, I have a problem with VMware installation on my gentoo. Here's the log file

# cat vmware-5684.log

 

2018-11-07T17:29:35.969+01:00| host-5684| I125: Log for VMware Workstation pid=5684 version=15.0.0 build=build-10134415 option=Release

2018-11-07T17:29:35.969+01:00| host-5684| I125: The process is 64-bit.

2018-11-07T17:29:35.969+01:00| host-5684| I125: Host codepage=UTF-8 encoding=UTF-8

2018-11-07T17:29:35.969+01:00| host-5684| I125: Host is Linux 4.14.65-gentoo Gentoo Base System release 2.4.1

2018-11-07T17:29:35.969+01:00| host-5684| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-11-07T17:29:35.969+01:00| host-5684| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2018-11-07T17:29:35.969+01:00| host-5684| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": File o directory non esistente.

2018-11-07T17:29:35.969+01:00| host-5684| I125: PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2018-11-07T17:29:35.973+01:00| host-5684| W115: Logging to /tmp/vmware-root/vmware-5684.log

2018-11-07T17:29:36.026+01:00| host-5684| I125: Obtaining info using the running kernel.

2018-11-07T17:29:36.026+01:00| host-5684| I125: Created new pathsHash.

2018-11-07T17:29:36.026+01:00| host-5684| I125: Setting header path for 4.14.65-gentoo to "/lib/modules/4.14.65-gentoo/build/include".

2018-11-07T17:29:36.026+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.026+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.043+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.043+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:36.390+01:00| host-5684| I125: found symbol version file /lib/modules/4.14.65-gentoo/build/Module.symvers

2018-11-07T17:29:36.390+01:00| host-5684| I125: Reading symbol versions from /lib/modules/4.14.65-gentoo/build/Module.symvers.

2018-11-07T17:29:36.413+01:00| host-5684| I125: Read 15440 symbol versions

2018-11-07T17:29:36.414+01:00| host-5684| I125: Reading in info for the vmmon module.

2018-11-07T17:29:36.414+01:00| host-5684| I125: Reading in info for the vmnet module.

2018-11-07T17:29:36.414+01:00| host-5684| I125: Reading in info for the vmci module.

2018-11-07T17:29:36.414+01:00| host-5684| I125: Reading in info for the vsock module.

2018-11-07T17:29:36.414+01:00| host-5684| I125: Setting vsock to depend on vmci.

2018-11-07T17:29:36.414+01:00| host-5684| I125: Invoking modinfo on "vmmon".

2018-11-07T17:29:36.417+01:00| host-5684| I125: "/sbin/modinfo" exited with status 0.

2018-11-07T17:29:36.417+01:00| host-5684| I125: Invoking modinfo on "vmnet".

2018-11-07T17:29:36.419+01:00| host-5684| I125: "/sbin/modinfo" exited with status 0.

2018-11-07T17:29:36.419+01:00| host-5684| I125: Invoking modinfo on "vmci".

2018-11-07T17:29:36.422+01:00| host-5684| I125: "/sbin/modinfo" exited with status 256.

2018-11-07T17:29:36.422+01:00| host-5684| I125: Invoking modinfo on "vsock".

2018-11-07T17:29:36.425+01:00| host-5684| I125: "/sbin/modinfo" exited with status 256.

2018-11-07T17:29:36.441+01:00| host-5684| I125: to be installed: vmci status: 0

2018-11-07T17:29:36.441+01:00| host-5684| I125: to be installed: vsock status: 0

2018-11-07T17:29:36.457+01:00| host-5684| I125: Obtaining info using the running kernel.

2018-11-07T17:29:36.458+01:00| host-5684| I125: Setting header path for 4.14.65-gentoo to "/lib/modules/4.14.65-gentoo/build/include".

2018-11-07T17:29:36.458+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.458+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.475+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.476+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:36.823+01:00| host-5684| I125: found symbol version file /lib/modules/4.14.65-gentoo/build/Module.symvers

2018-11-07T17:29:36.823+01:00| host-5684| I125: Reading symbol versions from /lib/modules/4.14.65-gentoo/build/Module.symvers.

2018-11-07T17:29:36.845+01:00| host-5684| I125: Read 15440 symbol versions

2018-11-07T17:29:36.846+01:00| host-5684| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.14.65-gentoo/build/include

2018-11-07T17:29:36.846+01:00| host-5684| I125: Update kernel header path to /lib/modules/4.14.65-gentoo/build/include

2018-11-07T17:29:36.846+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.846+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.861+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.861+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:36.864+01:00| host-5684| I125: Found compiler at "/usr/bin/gcc"

2018-11-07T17:29:36.872+01:00| host-5684| I125: Got gcc version "7.3.0".

2018-11-07T17:29:36.872+01:00| host-5684| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-11-07T17:29:36.880+01:00| host-5684| I125: Got gcc version "7.3.0".

2018-11-07T17:29:36.880+01:00| host-5684| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-11-07T17:29:36.884+01:00| host-5684| I125: Trying to find a suitable PBM set for kernel "4.14.65-gentoo".

2018-11-07T17:29:36.884+01:00| host-5684| I125: No matching PBM set was found for kernel "4.14.65-gentoo".

2018-11-07T17:29:36.884+01:00| host-5684| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-11-07T17:29:36.884+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.884+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.907+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.907+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:36.916+01:00| host-5684| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-11-07T17:29:36.916+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.916+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.936+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.936+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:36.936+01:00| host-5684| I125: Using temp dir "/tmp".

2018-11-07T17:29:36.939+01:00| host-5684| I125: Obtaining info using the running kernel.

2018-11-07T17:29:36.939+01:00| host-5684| I125: Setting header path for 4.14.65-gentoo to "/lib/modules/4.14.65-gentoo/build/include".

2018-11-07T17:29:36.939+01:00| host-5684| I125: Validating path "/lib/modules/4.14.65-gentoo/build/include" for kernel release "4.14.65-gentoo".

2018-11-07T17:29:36.940+01:00| host-5684| I125: using /usr/bin/gcc for preprocess check

2018-11-07T17:29:36.958+01:00| host-5684| I125: Preprocessed UTS_RELEASE, got value "4.14.65-gentoo".

2018-11-07T17:29:36.959+01:00| host-5684| I125: The header path "/lib/modules/4.14.65-gentoo/build/include" for the kernel "4.14.65-gentoo" is valid.  Whoohoo!

2018-11-07T17:29:37.308+01:00| host-5684| I125: found symbol version file /lib/modules/4.14.65-gentoo/build/Module.symvers

2018-11-07T17:29:37.308+01:00| host-5684| I125: Reading symbol versions from /lib/modules/4.14.65-gentoo/build/Module.symvers.

2018-11-07T17:29:37.331+01:00| host-5684| I125: Read 15440 symbol versions

2018-11-07T17:29:37.331+01:00| host-5684| I125: Invoking modinfo on "vmci".

2018-11-07T17:29:37.334+01:00| host-5684| I125: "/sbin/modinfo" exited with status 256.

2018-11-07T17:29:37.334+01:00| host-5684| I125: Invoking modinfo on "vsock".

2018-11-07T17:29:37.337+01:00| host-5684| I125: "/sbin/modinfo" exited with status 256.

2018-11-07T17:29:38.068+01:00| host-5684| I125: Setting destination path for vmci to "/lib/modules/4.14.65-gentoo/misc/vmci.ko".

2018-11-07T17:29:38.068+01:00| host-5684| I125: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2018-11-07T17:29:38.081+01:00| host-5684| I125: Successfully extracted the vmci source.

2018-11-07T17:29:38.081+01:00| host-5684| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-Mi8eXo/vmci-only auto-build HEADER_DIR=/lib/modules/4.14.65-gentoo/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-11-07T17:29:41.024+01:00| host-5684| W115: Failed to build vmci.  Failed to execute the build command.

2018-11-07T17:29:41.028+01:00| host-5684| I125: Setting destination path for vsock to "/lib/modules/4.14.65-gentoo/misc/vsock.ko".

2018-11-07T17:29:41.028+01:00| host-5684| I125: Extracting the vsock source from "/usr/lib/vmware/modules/source/vsock.tar".

2018-11-07T17:29:41.041+01:00| host-5684| I125: Successfully extracted the vsock source.

2018-11-07T17:29:41.041+01:00| host-5684| I125: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2018-11-07T17:29:41.057+01:00| host-5684| I125: Successfully extracted the vmci source.

2018-11-07T17:29:41.057+01:00| host-5684| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-Mi8eXo/vmci-only auto-build HEADER_DIR=/lib/modules/4.14.65-gentoo/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-11-07T17:29:44.045+01:00| host-5684| W115: Failed to build vmci.  Failed to execute the build command.

 

Сделать это через параметры VMXили через настройки графического адаптера в виртуально машине.

To do this through the parameters of the VMX or through the settings of the graphics card in the virtual machine.

I am aware that the higher end products of vmware like vsphere etc have backup features or even there seems to be 3rd party products for such functions. I am however just a vmware workstation pro user user, only familiar with workstation & player, but I had been using these wonderful products for more than a decade since version 4 days.

My suggestion arose from my own needs, I run NAS & email servers in VMs, in a small business office, very reliable for many years.

My host machine is Linux, and I have crontab jobs, running every night to backup my servers. My scripts put each VM 1 by 1 to suspend mode, copy the whole folder to a backup volume and then restore it, before proceeding to the next VM. It is working fine for me especially the NAS has no user at the night time.

There is however a slight problem for the email server, obviously, during my backup period (few minutes), the server is down, and incoming emails are receiving no respond error from my server which got put in suspend mode for backup.

Hence, I am suggesting, a new feature for backup purpose, to allow VM to be continuously running non-stop, no disruption to their functions during their backup. In concept, alike a temporary snapshot being taken, and wholly duplicated to another folder location, just only without the new delta vmdk files containing changes after the snapshot point, and after duplication, this temporary snapshot is deleted, and the VM continues to function undisrupted.

In the duplicated folder, there should be a content of a full VM, in a snapshot state, still snapshot in power ON state. Freezing the state exactly at the moment of the backup time.

My suggestion is to have this feature added into the snapshot manager area, as a new option, call it SNAPSHOT-BACKUP or any more appropriate name anyone else better than me can think of. The UI need to prompt for user to specify a destination folder which backup will duplicate VM into.

At the same time, append a new command into the VMRUN command line utility, calling it by this same new name, so that e.g. we issue command to "vmrun snapshot-backup /home/vm/email/email.vmx /mnt/backup_vm/email" the last part specifies the destination folder for this backup VM to be copied into.

With this feature, I hope VMware Workstation Pro users can easily carryout UNDISRUPTED BACKUP of running VMs.

If this feature could be provided in new version Workstation Pro, it will be beneficial and meaningful, and what the users will get is very similar to what I am doing for the time being - got a duplicated VM in suspended power state, but during the time of backing up my VMs are temporary off-line, disrupting their users.

Thanks & regards.

tsxi

Hi,

I have Vmware Workstation 12 in windows 10 and gest Red Hat 7.0.

I don't have ping from guest to host and internet connection in brirdge mode.

These is my config:

any help please?

Thanks!

I have three usb external hard drives attached and only two appear. I have raw disks 0 through 4 and I need to add disk 5. Does anyone have a suggestion.

Hi,

I'm currently evaluating VM Workstation 15 Pro, and have some Performance Problems, espacially when I compare it to VMware Fusion on a older MacBook pro.

So here is the Setup:

1. A MacBook Pro (late 2015) with an Intel Core i7-4770HQ 2.2Ghz and no dedicated graphics Card (Intel Iris Pro)
2. A ThinkPad T580 with an Intel Core i7-8550U 1.8Ghz base frequency with an NVIdia Geforce MX150

So the MacBook pro does have the slighty faster CPU, while the ThinkPad's GPU is much faster.

While Windows 10 pro runs very smooth within VMware Fusion von the MBP (watching Videos on YouTube, playing older games such as Anno 1404) all of this does not really work within an Windows 10 VM on the ThinkPad using VMware Workstation pro.

I wonder if there is any way to improve the Performance VMs on Workstation pro 15.

Hi,

I have a big problem with the compatibilty of VMWare Workstation 15 and WIn10 1809, I don't know why but i can't see correctly then buttons in the bar. I try to reinstall a lot of times but al the time is the same result. Can anyone help me with this.

Thanks.

Best Regards,

I am installing a .vmdk file get the following  error message:

/home/ammas/Desktop/Android-x86 8.1-rc1 (64bit).vmdk:1: parser error : Start tag expected, '<' not found

KDMV

^

Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"

ATTENTION: default value of option force_s3tc_enable overridden by environment.

any options please

When building a large environment in Vmware Workstation, i always forget which ip adresses i used. So i add those in the name of the virtual client like DC01 10.10

Anyone who recognizes this problem and who can tell me a different(maybe easier) way to remember/find the used adresses?