Re: VMWare Workstation 14.1.2 build-8497320, locks...

DickHinSC · ‎07-12-2018

VMWare Workstation 14.1.2 build-8497320, locks up "non-responsive"; "waiting on IO" so says vmware.exe service. Workstation window becomes faded (2 "vmware.DMP" files available). Host Can't Kill the app or the service, SO Only solution is complete Host CPU Poweroff then Restart. And often the VM Guests are damaged "beyond repair" So Win 10 Pro kills all apps, keeps user data and installs a very fresh copy (like out of the box) of Win 10 WITHOUT any settings for local environment. UGLY and Time Consuming.

Happens when switching to another Workstation VM tab, even when only one vm is powered on, others in shutdown mode. The powered on VM is damaged, as are all powered on VMs. See above.

Same VMs running GREAT on 3 active instances of VMPlayer. Easy to switch between VMs (and host)

Dell Precision Tower 5820, Intel Xenon W-2125, 64GB, MR9440-8i SCSI Disk Device Raid 5, Windows 10 Pro for Workstations 1803 17134.165 All Dell drivers and bios are current. All Dell's system tests pass.

I've been a workstation user since version 6 days. First time I've run into non-responsive lockups that require host poweroff.

Any help would be greatly appreciated.

DickHinSC · ‎07-13-2018

Well...too soon. VMPlayers misbehaved fading out and locking. Host lost windows explorer to lockup. But a shutdown was done via a command prompt. Hmmmm.

Juxxi · ‎07-15-2018

Hello.. it seems that there are at least three separate discussions of similar symptoms (14.1.2 build-8497320 wreaking havoc on HOST system). I noticed graphics in VM gets scrambled and soon after that, host OS becomes unstable (explorer freezing, task manager freezing etc.) and the only way to recover is host hard reset.

Any news from @vmware ?

DickHinSC · ‎07-16-2018

No news from @vmware yet. I hope they say something soon.

Susie201110141 · ‎07-17-2018

Sorry for late response.

Could you share more details about how to reproduce this problem ? If you could share the dmp files and collect support data, that would be more helpful.

BTW, did you meet same problem in previous workstation version?

DickHinSC · ‎07-17-2018

Thanks for contact Susie201110141.

As per original specs: Win10Host,WS14, 3 Guest Tabs (2x Win7Pro, 1x Win10Pro) all current and with current WS14 VM Tools. In Win7s: Chrome & FF Browsers open, several WinExplorers Open to local and NAS Files. All my std operations as per Other Older Machine(Win7Host, Ws12). Had to get newer Host as WS14 sait it wouldn't run on Older machine. Switching back and forth between WS Tabs. When switching away from a tab, the Frame would go pale and be unresponsive. Machine locked as per original description. After several Guest repairs and try-agains, I opened Task manager in host. VMware.exes said non-responsive, WinExplorer went non-responsive when I tried to start it in host. Task Manager stayed running. Cancelling VMware.exe tasks didn't work. Twice I was able to take a Dump. I'll attach them. WHOOPS: DMP Files Too Big. Zipped DMP Files Too Big. So Now What???

Not mentioned, but on Windows Network Trees, Guests only saw Win7s and Host, NOT NASs. After manually referencing NASs, they showed up in NetworkTree. but soon disappeared.

Then I tried WS14Player, with each of the 3 repaired VMs, individually and then in multiple simultaneous runs, Multiples too locked, going pale. I can't remember results of single player.

Next plan of action, after I catch up on much delayed (cashflow) work, will be to clean out WS 14 and install most recent WS 12, but I think I saw that VMWare doesn't think WS 12 will run on Win10Pro 1803. I do NOT wish to regress my new machine to Win7.

Any help you can provide would be most appreciated. Until I hear from you, I'll sit tight on WS14, while I go back to my old machine.

Susie201110141 · ‎07-17-2018

Could you upload your zipped DMP Files here ? I'll also try to reproduce this issue locally.

VMware ftp site:

FTP Server: ftpsite.vmware.com

User: inbound

Pwd: inbound

Port: 21

You can retrieve any file that is uploaded to this site via either http or ftp. Via http:

http://ftpsite.vmware.com/inbound/ftp/

DickHinSC · ‎07-17-2018

2 DMP files uploaded.

AND http://ftpsite.vmware.com/inbound/ftp/ gives 404s

Susie201110141 · ‎07-17-2018

Thanks so much for uploading the logs.

I saw two dmp files from the ftp: ( DMP-1.zip DMP-2.zip ), and then we will investigate this issue.

AngryNapkin · ‎07-20-2018

Im having the same issues described here but running in Linux.

Here is the output:

Jul 20 14:12:58 oldMan kernel: ------------[ cut here ]------------
Jul 20 14:12:58 oldMan kernel: kernel BUG at fs/xfs/xfs_aops.c:925!
Jul 20 14:12:58 oldMan kernel: invalid opcode: 0000 [#1] PREEMPT SMP PTI
Jul 20 14:12:58 oldMan kernel: Modules linked in: vmw_vsock_vmci_transport vsock vmnet(O) vmw_vmci vmmon(O) xfs jfs btrfs zstd_compress libcrc32c zstd_decompress xxhash xor raid6_pq sr_mod>
Jul 20 14:12:58 oldMan kernel: fat ttm dcdbas dell_smm_hwmon fuse rtsx_usb_ms ecdh_generic memstick snd_compress ac97_bus aesni_intel r8169 aes_x86_64 crypto_simd cryptd i2c_algo_bit glue>
Jul 20 14:12:58 oldMan kernel: ahci libahci xhci_pci libata xhci_hcd crc32c_intel scsi_mod usbcore usb_common i8042 serio
Jul 20 14:12:58 oldMan kernel: CPU: 3 PID: 5301 Comm: kworker/u8:0 Tainted: G O 4.17.6-1-ARCH #1
Jul 20 14:12:58 oldMan kernel: Hardware name: Dell Inc. Inspiron 5759/05NVNV, BIOS 1.4.1 12/08/2017
Jul 20 14:12:58 oldMan kernel: Workqueue: writeback wb_workfn (flush-8:0)
Jul 20 14:12:58 oldMan kernel: RIP: 0010:xfs_do_writepage+0x625/0x6b0 [xfs]
Jul 20 14:12:58 oldMan kernel: RSP: 0018:ffffa81587e13980 EFLAGS: 00010246
Jul 20 14:12:58 oldMan kernel: RAX: 02ffff0000000029 RBX: 00000000fa000000 RCX: 000000000000000c
Jul 20 14:12:58 oldMan kernel: RDX: 00000000000fa000 RSI: ffffa81587e13c90 RDI: fffffbb3c94faf00
Jul 20 14:12:58 oldMan kernel: RBP: ffffa81587e13c90 R08: 0000000000028000 R09: 0000000000000002
Jul 20 14:12:58 oldMan kernel: R10: ffffa04382ffa000 R11: 00000000000020ef R12: ffffa03f362edb78
Jul 20 14:12:58 oldMan kernel: R13: ffffa03f362edcf0 R14: fffffbb3c94faf00 R15: ffffa81587e13b38
Jul 20 14:12:58 oldMan kernel: FS: 0000000000000000(0000) GS:ffffa04382d80000(0000) knlGS:0000000000000000
Jul 20 14:12:58 oldMan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 20 14:12:58 oldMan kernel: CR2: 00007fef81e15000 CR3: 000000002500a004 CR4: 00000000003606e0
Jul 20 14:12:58 oldMan kernel: Call Trace:
Jul 20 14:12:58 oldMan kernel: ? clear_page_dirty_for_io+0x26d/0x320
Jul 20 14:12:58 oldMan kernel: write_cache_pages+0x1e6/0x450
Jul 20 14:12:58 oldMan kernel: ? xfs_aops_discard_page+0x130/0x130 [xfs]
Jul 20 14:12:58 oldMan kernel: xfs_vm_writepages+0x62/0xa0 [xfs]
Jul 20 14:12:58 oldMan kernel: do_writepages+0x41/0xd0
Jul 20 14:12:58 oldMan kernel: ? blk_start_plug+0x40/0x40
Jul 20 14:12:58 oldMan kernel: ? merge+0x59/0xb0
Jul 20 14:12:58 oldMan kernel: ? blk_start_plug+0x40/0x40
Jul 20 14:12:58 oldMan kernel: ? preempt_count_add+0x68/0xa0
Jul 20 14:12:58 oldMan kernel: __writeback_single_inode+0x3d/0x3d0
Jul 20 14:12:58 oldMan kernel: ? _raw_spin_lock+0x13/0x40
Jul 20 14:12:58 oldMan kernel: writeback_sb_inodes+0x1ec/0x460
Jul 20 14:12:58 oldMan kernel: __writeback_inodes_wb+0x5d/0xb0
Jul 20 14:12:58 oldMan kernel: wb_writeback+0x28f/0x340
Jul 20 14:12:58 oldMan kernel: ? get_nr_inodes+0x35/0x50
Jul 20 14:12:58 oldMan kernel: ? cpumask_next+0x16/0x20
Jul 20 14:12:58 oldMan kernel: wb_workfn+0x172/0x430
Jul 20 14:12:58 oldMan kernel: process_one_work+0x1d1/0x3b0
Jul 20 14:12:58 oldMan kernel: worker_thread+0x2b/0x3d0
Jul 20 14:12:58 oldMan kernel: ? process_one_work+0x3b0/0x3b0
Jul 20 14:12:58 oldMan kernel: kthread+0x112/0x130
Jul 20 14:12:58 oldMan kernel: ? kthread_flush_work_fn+0x10/0x10
Jul 20 14:12:58 oldMan kernel: ret_from_fork+0x35/0x40
Jul 20 14:12:58 oldMan kernel: Code: c2 04 75 48 85 d2 0f 84 b6 fd ff ff c6 00 00 f6 c2 02 0f 84 aa fd ff ff 31 c9 66 89 4c 10 fe e9 9e fd ff ff 0f 0b e9 57 fe ff ff <0f> 0b f0 80 4b 78 01>
Jul 20 14:12:58 oldMan kernel: RIP: xfs_do_writepage+0x625/0x6b0 [xfs] RSP: ffffa81587e13980
Jul 20 14:12:58 oldMan kernel: ---[ end trace 2196908f7c54a864 ]---
Jul 20 14:12:58 oldMan kernel: WARNING: CPU: 3 PID: 5301 at kernel/exit.c:771 do_exit+0x4f/0xac0
Jul 20 14:12:58 oldMan kernel: Modules linked in: vmw_vsock_vmci_transport vsock vmnet(O) vmw_vmci vmmon(O) xfs jfs btrfs zstd_compress libcrc32c zstd_decompress xxhash xor raid6_pq sr_mod>
Jul 20 14:12:58 oldMan kernel: fat ttm dcdbas dell_smm_hwmon fuse rtsx_usb_ms ecdh_generic memstick snd_compress ac97_bus aesni_intel r8169 aes_x86_64 crypto_simd cryptd i2c_algo_bit glue>
Jul 20 14:12:58 oldMan kernel: ahci libahci xhci_pci libata xhci_hcd crc32c_intel scsi_mod usbcore usb_common i8042 serio
Jul 20 14:12:58 oldMan kernel: CPU: 3 PID: 5301 Comm: kworker/u8:0 Tainted: G D O 4.17.6-1-ARCH #1
Jul 20 14:12:58 oldMan kernel: Hardware name: Dell Inc. Inspiron 5759/05NVNV, BIOS 1.4.1 12/08/2017
Jul 20 14:12:58 oldMan kernel: Workqueue: writeback wb_workfn (flush-8:0)
Jul 20 14:12:58 oldMan kernel: RIP: 0010:do_exit+0x4f/0xac0
Jul 20 14:12:58 oldMan kernel: RSP: 0018:ffffa81587e13ee8 EFLAGS: 00010206
Jul 20 14:12:58 oldMan kernel: RAX: ffffa81587e13d90 RBX: ffffa04370309e80 RCX: 0000000000000000
Jul 20 14:12:58 oldMan kernel: RDX: ffffa03f76897040 RSI: 0000000000000000 RDI: ffffffff95058c20
Jul 20 14:12:58 oldMan kernel: RBP: 000000000000000b R08: 0000000000000005 R09: 0000000000000444
Jul 20 14:12:58 oldMan kernel: R10: 0000000000000000 R11: ffffffff955eeeed R12: ffffa81587e138d8
Jul 20 14:12:58 oldMan kernel: R13: 0000000000000000 R14: 0000000000000004 R15: ffffa81587e138d8
Jul 20 14:12:58 oldMan kernel: FS: 0000000000000000(0000) GS:ffffa04382d80000(0000) knlGS:0000000000000000
Jul 20 14:12:58 oldMan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 20 14:12:58 oldMan kernel: CR2: 00007fef81e15000 CR3: 000000002500a004 CR4: 00000000003606e0
Jul 20 14:12:58 oldMan kernel: Call Trace:
Jul 20 14:12:58 oldMan kernel: ? process_one_work+0x3b0/0x3b0
Jul 20 14:12:58 oldMan kernel: ? kthread+0x112/0x130
Jul 20 14:12:58 oldMan kernel: rewind_stack_do_exit+0x17/0x20
Jul 20 14:12:58 oldMan kernel: Code: 8b 04 25 28 00 00 00 48 89 44 24 30 31 c0 e8 a9 6f 07 00 48 8b 83 e0 07 00 00 48 85 c0 74 0e 48 8b 10 48 39 d0 0f 84 49 04 00 00 <0f> 0b 65 44 8b 2d d7>
Jul 20 14:12:58 oldMan kernel: ---[ end trace 2196908f7c54a865 ]---

This happens all the time and its upsetting after about 15 minutes, vmware "locks" up tight.

Any logs or anything I can submit from a linux machine to try and help resolve this?

I have tried running these vm's on EXT4 ans XFS file systems and both produce this issue.

Susie201110141 · ‎07-22-2018

Dick,

We have gone through the logs and suspect it's related to "D:\VMs\Win7x64\Windows 7 x64.vmx".

Could you do following operations:

1. Close workstation if it's running and backup preference files: %appdata%\VMware\preferences.ini and preferences-private.ini .

2. Then delete above two preference files.

3. Re-launch workstation and don't touch "D:\VMs\Win7x64\Windows 7 x64.vmx".

4. Then collect support data from menu: "Help->Support->Collect support data..." and upload the log file here.

Thanks for the great support!

Susie201110141 · ‎07-22-2018

Hi AngryNapkin,

Did you meet this issue in Linux host or guest?
What's the version of host OS and guest OSes ?If possible, you could also upload the support data log onto the ftp and tell me the file name.
It looks like a kernel crash, which is different from the original post.

AngryNapkin · ‎07-23-2018

Did you meet this issue in Linux host or guest?
What's the version of host OS and guest OSes ?If possible, you could also upload the support data log onto the ftp and tell me the file name.
It looks like a kernel crash, which is different from the original post.

This is happening in a Linux Host. Arch Linux.(I know I know, not supported platform).

The guest OS's are Windows SBS2008, Server2016 Standard, and pfsense. All running at the same time. VMWare locked up when shutting down either of the two windows guests.

The host stays running and active, VMware Workstation just completely locks up and the Host is unable to do anything. I cant even shut down without hard power because vmware has a lock on the mounted disks. I posted here because it does seem to show the same symptoms of vmware locking up and host unable to do anything about it.

Could you assist in locating these support files? I dont know which files or where they are located.

Thanks.

DickHinSC · ‎07-23-2018

I followed your steps. Uploaded 2 files: 1) Start WS, Select W7x64 so there's a tab to reference the VM the support dump is for. the VM has not run yet. then 2) Poweron the VM W7x64, logon, didn't run any tasks, get support Dump.

Recently I became aware of Very slow Host ethernet transfer to NAS when VMWS has been running for a while. Without Wworkstation running Host task manager shows 970Mbits/sec. Later on, when Workstation has been running a while the same data file transfer was showing steady 17MBits/sec. That's quite a slow down.

With several VMs running on Workstation, and after a while, switching between their tabs gets slow and I've noted the clock on the switched-to tab's VM to be over an hour behind. This implies that WS is not switching to tasks if it's not the task with visible focus. And I've noted that mouse and keyboard aren't functioning for periods of time up to several minutes for the visible VM. The latter usually (but not always) happens when I've just selected the VM's tab.

In general I'd have to say that WS 14.1.2 responsiveness Deteriorates the longer it's been running. Note that just powering off all running VMs, then restarting them doesn't help. The workstation program has to exit and restart. Often, the host needs to be rebooted.

Confirming that everything is current, all Windows OSs - host and all VMs, Dell's Drivers and Dell's BIOS.

I sincerely hope that VM 14.x can become as stable, reliable and dependable as 12.5.9 has been.

Susie201110141 · ‎07-23-2018

You can collect support data from menu: "Help->Support->Collect support data..." and upload the log file here.

Susie201110141 · ‎07-23-2018

Could you share the two files' name in the directory: ftpsite.vmware.com/inbound/ftp/

I couldn't tell which files were uploaded by you.

For network performance issue, which nic type did you configure? More details are needed.

Thanks for continous support!

DickHinSC · ‎07-24-2018

Susie: Is #14 for AngryNapkin? or DickHinSC? if latter see my previous reply in #13 where I did upload support Data. Is there any way to separate these two issues into sepasrate streams? If not how about starting your replies with name of target (AN or DickHinSC):

Seems like more of your customers on different hardware but same OS are having very similar problems.

DickHinSC · ‎07-24-2018

I FTP'd both files.

Host NIC is Intel(R) Ethernet Connection (5) I219-LM

All VMs NIC Bridged Automatic. Intel(R) PRO/1000 MT Network Connection

AngryNapkin · ‎07-24-2018

I have uploaded the support data on the VM's.

Files name is:

vm-2018-07-24.4966.tgz

AngryNapkin · ‎07-24-2018

I have uploaded the files to the FTP.

The file name is

vm-2018-07-24.4966.tgz