Contributor
Contributor

Can't start virtual machine after upgrade to VMWare Workstation 16.x

I was using VMWare Workstation 15.x until yesterday on a openSuSE 15.1 Leap, wich was working fine. After upgrade to VMWare Workstation 16.x on the same host system I have problems with the virtual machines. No virtual machine (regardless if it is a Windows or a Linux system) is able to start. Every machine hangs at "waiting for connection".

Has anyone a suggestion what could be the problem?

Thanks in advanced

12 Replies
Contributor
Contributor

I have the same problem on Windows 10. Yesterday I just closed virtual machines on my notebook as usual 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

0 Kudos
VMware Employee
VMware Employee

ISBR shall not impact on Linux host. Could u upload the full vmware.log and mksSandbox.log to take a look?

Thanks

0 Kudos
Community Manager
Community Manager

> "ISBR"

My man, no one externally knows what that means Smiley Wink

- Michael Roy - Product Line Manager: Fusion & Workstation
VMware Employee
VMware Employee

Sorry, I mean the mksSandbox shall not impact on Linux host.

Looks like the issue is reported on Linux host, right? Given yes, please let me know the host OS version and the kernel version when the issue happened.

Thanks

Leadership
Leadership

Intel SandBox Renderer?

Internal Secret Background Recruiters?

Infused Signified Bunsing Response?

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
Leadership
Leadership

Topic Starter was on Suse Linux host.

Other user who reported the same or similar problem is apparently on Windows 10.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
Contributor
Contributor

I also have the same issue after upgrading to v16 from 15.

Running on openSUSE Leap 15.1

I created a fresh VM, with no disk, no usb, no sound, etc.  And it will hang with "Waiting for connection" .

Here is the last bit of the log:

2020-09-25T10:07:59.554-04:00| vmx| I005: VMMEM: Precise Reservation: 2276MB (MainMem=256MB)

2020-09-25T10:07:59.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck limits: ovhdText=22528(88.0MB) ovhdStatic=49152(192.0MB) ovhdMalloc=495237(1934.5MB)

2020-09-25T10:07:59.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck usage: ovhdText=8232(32.1MB) ovhdStatic=13100(51.1MB) ovhdMalloc=2591(10.1MB)

2020-09-25T10:07:59.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck: total=15691(61.2MB) arena=2590(10.1MB) maps=1(0.0MB) stacks=10490(40.9MB) data=2610(10.1MB)

2020-09-25T10:07:59.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck: malloc used=9274096 (2265 pgs) free=1334544 (326 pgs) tot=10608640 (2590 pgs)

2020-09-25T10:07:59.554-04:00| vmx| I005: Vix: [mainDispatch.c:1050]: VMAutomation_PowerOn. Powering on.

2020-09-25T10:07:59.555-04:00| vmx| I005: VMX_PowerOn: ModuleTable_PowerOn = 1

2020-09-25T10:07:59.555-04:00| vmx| A000: ConfigDB: Setting cleanShutdown = "FALSE"

2020-09-25T10:07:59.555-04:00| vmx| A000: ConfigDB: Setting softPowerOff = "FALSE"

2020-09-25T10:07:59.555-04:00| vmx| I006: ConfigDB: No data written - no change detected.

2020-09-25T10:07:59.555-04:00| vmx| I006: ConfigDB: VM config file was not updated with latest dictionary edits.

2020-09-25T10:07:59.555-04:00| vcpu-0| I005: VTHREAD 140035041580800 "vcpu-0" tid 9671

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(PassthruMgrLock)=0xff000000 lid=23

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(monTimer-vcpu0)=0x7cf lid=24

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MonTimer APIC:1/1 vec: 236

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: APIC: version = 0x15, max LVT = 6, LDR = 0x10, DFR = 0xffffffff

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(stopLock)=0x1 lid=25

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: BusMem_Init: vcpu=0

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: BUSMEM: vmm initialization

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_0)=0x320 lid=26

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_1)=0x321 lid=27

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_2)=0x322 lid=28

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_3)=0x323 lid=29

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_4)=0x324 lid=30

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_5)=0x325 lid=31

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_6)=0x326 lid=32

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_7)=0x327 lid=33

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_8)=0x328 lid=34

2020-09-25T10:07:59.566-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_9)=0x329 lid=35

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_10)=0x32a lid=36

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_11)=0x32b lid=37

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_12)=0x32c lid=38

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_13)=0x32d lid=39

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_14)=0x32e lid=40

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLock_15)=0x32f lid=41

2020-09-25T10:07:59.581-04:00| vcpu-0| I005: MX: init lock: rank(busMemLeafLock)=0x3e7 lid=42

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: BusMemTrace_Init: vcpu=0

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: MX: init lock: rank(BusMemSampleLock)=0x382 lid=43

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: BranchTracingInit: debugCtl before=0x1 after=0x1

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: MX: init lock: rank(mwaitLock)=0x18f lid=44

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: MX: init lock: rank(hyvMsrLock)=0x18f lid=45

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: MX: init lock: rank(smmBarrierLock)=0x6 lid=46

2020-09-25T10:07:59.583-04:00| vcpu-0| I005: Init modules.

2020-09-25T10:08:19.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck limits: ovhdText=22528(88.0MB) ovhdStatic=49152(192.0MB) ovhdMalloc=495237(1934.5MB)

2020-09-25T10:08:19.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck usage: ovhdText=8232(32.1MB) ovhdStatic=15147(59.1MB) ovhdMalloc=2624(10.2MB)

2020-09-25T10:08:19.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck: total=17771(69.4MB) arena=2623(10.2MB) maps=1(0.0MB) stacks=12537(48.9MB) data=2610(10.1MB)

2020-09-25T10:08:19.554-04:00| vmx| I005: OvhdMemVmx_SizeCheck: malloc used=8921008 (2178 pgs) free=1822800 (446 pgs) tot=10743808 (2623 pgs)

2020-09-25T10:08:29.428-04:00| vmx| I005: LOADAVG: 1.15 1.04 0.97

0 Kudos
Community Manager
Community Manager

Isolated Sand Box Renderer Smiley Wink

- Michael Roy - Product Line Manager: Fusion & Workstation
VMware Employee
VMware Employee

Thank you for posting your query in community.

Could you please try setting Gathering Debugging Information to "Full" and then power on the VM.  It will probably still fail, but the resulting vmware.log file might have more useful information in it.  If you could post that vmware.log (just use the Attach link in the bottom-right corner of the window when composing a reply), that'd be super helpful.

0 Kudos
Contributor
Contributor

I created zip file with log and vm config, but I don't see any Attach button. Maybe I need some access rights yet (I see @Mention button only in right-bottom corner). Toolbar contains possibility to attach picture & vide and nothing else.

0 Kudos
Contributor
Contributor

Sorry - I was using wrong editor - from messages preview.
Please find below attached zip file...

0 Kudos
Community Manager
Community Manager

Please stick to the thread you authored instead of hijacking another posters issue.

- Michael Roy - Product Line Manager: Fusion & Workstation
0 Kudos