I have a problem on Windows 10. Yesterday I just closed virtual machines on my notebook as usual (I use Workstation 16 for some time already)
and today no any virtual machine is able to start. It shows all the time spinning logo of VMWare bios.
mksSandbox.log has old date and contents. Tail of vmware.log has new date/time and is below...
2020-09-24T10:27:08.047+02:00| vmx| I005: VMXAIOMGR: Using: simple=Compl
2020-09-24T10:27:08.049+02:00| vmx| I005: WORKER: Creating new group with maxThreads=1 (20)
2020-09-24T10:27:08.053+02:00| vmx| I005: WORKER: Creating new group with maxThreads=16 (36)
2020-09-24T10:27:08.056+02:00| vmx| I005: FeatureCompat: No VM masks.
2020-09-24T10:27:08.056+02:00| vmx| I005: TimeTracker host to guest rate conversion 699561783 @ 2592001000Hz -> 0 @ 2592001000Hz
2020-09-24T10:27:08.056+02:00| vmx| I005: TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + -699561783
2020-09-24T10:27:08.056+02:00| vmx| I005: Disabling TSC scaling since host does not support it.
2020-09-24T10:27:08.056+02:00| vmx| I005: TSC offsetting enabled.
2020-09-24T10:27:08.056+02:00| vmx| I005: timeTracker.globalProgressMaxAllowanceMS: 2000
2020-09-24T10:27:08.056+02:00| vmx| I005: timeTracker.globalProgressToAllowanceNS: 1000
2020-09-24T10:27:08.056+02:00| vmx| I005: MKS PowerOn
2020-09-24T10:27:08.058+02:00| mks| I005: VTHREAD 8580 "mks"
2020-09-24T10:27:08.058+02:00| mks| I005: MKS thread is alive
2020-09-24T10:27:08.058+02:00| svga| I005: VTHREAD 14744 "svga"
2020-09-24T10:27:08.058+02:00| svga| I005: SVGA thread is alive
2020-09-24T10:27:08.058+02:00| mks| I005: MKS: SSE2=1, SSSE3=1, SSE4_1=1
2020-09-24T10:27:08.062+02:00| mouse| I005: VTHREAD 14736 "mouse"
2020-09-24T10:27:08.062+02:00| mks| I005: MKS-HookKeyboard: RegQueryValueEx(LowLevelHooksTimeout) failed: The system cannot find the file specified (2)
2020-09-24T10:27:08.062+02:00| kbh| I005: VTHREAD 14732 "kbh"
2020-09-24T10:27:08.064+02:00| mks| I005: MKS Win32: Registering top level window (0x307a8) to receive session change notification.
2020-09-24T10:27:08.064+02:00| mks| I005: Current Display Settings:
2020-09-24T10:27:08.064+02:00| mks| I005: Display: 0 size: 1920x1080 position: (0, 0) name: \\.\DISPLAY1
2020-09-24T10:27:08.065+02:00| mks| I005: MKS Win32: MIL: 0x4000
2020-09-24T10:27:08.065+02:00| mks| I005: MKS-RenderMain: PowerOn allowed MKSBasicOps DX11Renderer DX11BasicRenderer ISBRenderer
2020-09-24T10:27:08.065+02:00| mks| I005: MKS-RenderMain: Collecting RenderOps caps from ISBRenderer
2020-09-24T10:27:08.066+02:00| mks| I005: MKS-RenderMain: Starting ISBRenderer
2020-09-24T10:27:08.067+02:00| mks| I005: ISBRendererComm: mksSandbox command-line: C:\Program Files (x86)\VMware\VMware Workstation\x64\mksSandbox.exe --logFile C:\VMWare\Manjaro\mksSandbox.log --pipeInfo \\.\pipe\vmware\mksSandbox\mksSandbox-52 6a e4 5e 3f 55 c8 b7-86 30 1e d7 5d 41 12 3a
I use Lenovo ThinkPad P53. It has
It has Windows 10 Pro, version 2004, build 19041.508, Experience pack 120.2212.31.0.
More info is below...
Operating System: Windows 10 Pro, 64-bit
DirectX version: 12.0
GPU processor: Quadro RTX 4000
Driver version: 443.17
Driver Type: DCH
Direct3D API version: 12
Direct3D feature level: 12_1
CUDA Cores: 2560
Core clock: 1380 MHz
Memory data rate: 12.00 Gbps
Memory interface: 256-bit
Memory bandwidth: 384.06 GB/s
Total available graphics memory: 24442 MB
Dedicated video memory: 8192 MB GDDR6
System video memory: 0 MB
Shared system memory: 16250 MB
Video BIOS version: 90.04.4D.00.2A
IRQ: Not used
Bus: PCI Express x16 Gen3
Device Id: 10DE 1EB6 229717AA
Part Number: 4914 0010
nvui.dll 188.8.131.5217 NVIDIA User Experience Driver Component
nvxdplcy.dll 184.108.40.20617 NVIDIA User Experience Driver Component
nvxdbat.dll 220.127.116.1117 NVIDIA User Experience Driver Component
nvxdapix.dll 18.104.22.16817 NVIDIA User Experience Driver Component
NVCPL.DLL 22.214.171.12417 NVIDIA User Experience Driver Component
nvCplUIR.dll 8.1.940.0 NVIDIA Control Panel
nvCplUI.exe 8.1.940.0 NVIDIA Control Panel
nvWSSR.dll 126.96.36.19917 NVIDIA Workstation Server
nvWSS.dll 188.8.131.5217 NVIDIA Workstation Server
nvViTvSR.dll 184.108.40.20617 NVIDIA Video Server
nvViTvS.dll 220.127.116.1117 NVIDIA Video Server
nvLicensingS.dll 18.104.22.16817 NVIDIA Licensing Server
nvDevToolS.dll 22.214.171.12417 NVIDIA 3D Settings Server
nvDispSR.dll 126.96.36.19917 NVIDIA Display Server
nvDispS.dll 188.8.131.5217 NVIDIA Display Server
NVCUDA.DLL 184.108.40.20617 NVIDIA CUDA 10.2.177 driver
nvGameSR.dll 220.127.116.1117 NVIDIA 3D Settings Server
nvGameS.dll 18.104.22.16817 NVIDIA 3D Settings Server
I also need the mksSandbox.log and vmware.log for further investigation. Please help to upload the full log file as attached.
BTW, what's your guest OS version?
unfortunately I have no any old log files anymore. I use Workstation for software development and I needed it working so I removed v.16 from my host and installed 15.6. To start virtual machines I changed hardware compatibility to 16 in *.vmx files and it started working. Of course I removed any log files to see what is the after a fresh start of vm's...
I was not able to start any virtual machines on my host. I was trying to start Win10 Pro and Manjaro Linux guests...
I can't do it at the moment because some set of updates is managed by corpo admins...
The question is why it was working for a few days already when no any updates were installed on notebook recently...
Since you mentioned Manjaro Linux guest, we has an internal bug to track it. Could u try to add below line to the VM 's .vmx file as a workaround?
cpuid.7.edx = "----:----:----:----:----:----:---0:----"
Another CU reports a similar issue to boot Manjaro guest on Workstation 16, and it has resolved: Cannot boot manjaro-20 on workstation 16?
I don't use WS 16 anymore (although I bought it ) so I will try this workaround
when I have some free time for additional experiments with WS 16 after work.
Sorry for late reply. I checked the attached log, it seems it is interrupted at line below, which the mksSandbox process is probably not started up normally.
ISBRendererComm: mksSandbox command-line: C:\Program Files (x86)\VMware\VMware Workstation\x64\mksSandbox-debug.exe --logFile C:\VMWare\Manjaro\mksSandbox.log --pipeInfo \\.\pipe\vmware\mksSandbox\mksSandbox-52 f2 3b d9 af 4f 4b 55-4a 79 b7 ed 9d be 20 1f
I have few questions. Please help me to make it clear.
1) What's the result if you manually run the cmd above on windows host?
C:\Program Files (x86)\VMware\VMware Workstation\x64\mksSandbox-debug.exe --logFile C:\VMWare\Manjaro\mksSandbox.log --pipeInfo \\.\pipe\vmware\mksSandbox\mksSandbox-52 f2 3b d9 af 4f 4b 55-4a 79 b7 ed 9d be 20 1f
2) You're saying the guest used to be working on WS 16.0, but stopped working suddenly after running few days ?
3) Is there mksSandbox dump file under %temp% folder?
4) What's your guest OS kernel version? Since we have a internal bug to power on linux guest when kernel version is 5.8.0-rc.
I just installed the latest version of Workstation (16.1) and it still doesn't work. It doesn't create mksSandbox.log file also again (15.7 works fine).
When I started mksSandbox-debug.exe from powershell (when Workstation was still spinning guest machine showing VMWare logo) it started booting the guest machine as a result (security access rights somewhere???). It produced log file and I'd like to share it with you - but this attachment stuff accepts jpg/gif/pdf/pptx files only (I have zip file). How to share it with you?
btw: I was booting Windows 10 guest machine this time.
When it started the guest machine (as a side effect of running mks from powershell) it was behaving very slowly (like waiting for very slowly rendering operations). What is going on with WS 16??? When it can be considered as a user/production ready and start working at all?