VMware Communities
avarakin
Contributor
Contributor
Jump to solution

Trouble starting Windows 10 guest under Ubuntu 20.04

Hi

I have Win 10 VM which was created about a year ago under Ubuntu 19.10 which worked fine.

I recently upgraded to Ubuntu 20.04 and unable to open this VM - VMWare window immediately disappears as soon as I start the VM.

My PC is based on Ryzen 7 3700 and I am using Player 16.

Here is the log I am getting:

2020-09-30T01:00:40.733-04:00| vmplayer| I005: HandleGuestTopologyChange: main UI rect: 3840x2160 @ 0,0

2020-09-30T01:00:40.733-04:00| vmplayer| I005: HandleGuestTopologyChange: Found 0 present screens

2020-09-30T01:00:40.733-04:00| vmplayer| I005: HandleGuestTopologyChange: Windows for extra guest monitors will not be shown

2020-09-30T01:00:40.760-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Reloading config state.

2020-09-30T01:00:40.769-04:00| vmplayer| I005: VMHS: Transitioned vmx/execState/val to poweredOff

2020-09-30T01:00:40.771-04:00| vigorCnx| I005: VigorOfflineGetToolsVersion: updated tools version to 2c00

2020-09-30T01:00:40.786-04:00| vmplayer| I005: Vix: [foundryVMPowerOps.c:984]: FoundryVMPowerStateChangeCallback: /data/VM/vmware/Win10/Windows 10 x64.vmx, vmx/execState/val = poweredOff.

2020-09-30T01:00:40.786-04:00| vmplayer| I005: VMMKS::OnMKSDeviceInfoChanged: reset pipe name now in offline.

2020-09-30T01:00:40.786-04:00| vmplayer| I005: VMMKS::OnMKSDeviceInfoChanged: reset pipe name now in offline.

2020-09-30T01:00:40.786-04:00| vmplayer| I005: Found vmx as /usr/lib/vmware/bin/vmware-vmx

2020-09-30T01:00:40.787-04:00| vmplayer| I005: Starting vmx as /usr/lib/vmware/bin/vmware-vmx

2020-09-30T01:00:40.787-04:00| vmplayer| I005: VigorExecVMXExCommon: VM /data/VM/vmware/Win10/Windows 10 x64.vmx in directory /data/VM/vmware/Win10

2020-09-30T01:00:40.787-04:00| vmplayer| I005: VigorExecVMXExCommon: Exec()'ing /usr/lib/vmware/bin/vmware-vmx /data/VM/vmware/Win10/Windows 10 x64.vmx.

2020-09-30T01:00:40.792-04:00| vmplayer| I005: VmdbAddConnection: cnxPath=/db/connection/#a/, cnxIx=1

2020-09-30T01:00:40.792-04:00| vmplayer| I005: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#a/

2020-09-30T01:00:40.796-04:00| vmplayer| I005: OnVMStateChanged: alive = 1

2020-09-30T01:00:40.796-04:00| vmplayer| I005: CUIMKS: cui::MKS::SetAttached (55C5EA472360): detach

2020-09-30T01:00:40.796-04:00| vmplayer| I005: CUIMKS: cui::MKS::OnSetAttachedCompleted (55C5EA472360)

2020-09-30T01:00:40.900-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Mounting VM begun.

2020-09-30T01:00:40.900-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Mounting virtual machine paths on connection: /db/connection/#a/.

2020-09-30T01:00:40.902-04:00| vmplayer| I005: VmdbCnxControlCb: registered SUBSCRIBE completion callback, cnx = /db/connection/#a/

2020-09-30T01:00:40.947-04:00| vmplayer| I005: VigorOnlineStartMountCb Succeeded

2020-09-30T01:00:40.947-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Mounting VM complete.

2020-09-30T01:00:40.947-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: VMHSStartVmxVigorCb: vmPath=/vm/#035ea56fdabf547c/ status=done

2020-09-30T01:00:40.947-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Mount VM completion for vm.

2020-09-30T01:00:40.974-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Mount VM Complete: False

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF (remote disconnect)

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#a/' (-32)

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VigorOnlineRpcDemux Deferring completion on /vm/#035ea56fdabf547c/vmx/vigor/cmd/##c/

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VigorOnlineCnxDemux: VmdbCnx failed: Lost a connection to the running VMX instance.

2020-09-30T01:00:40.999-04:00| vmplayer| I005+ Transport (VMDB) error -32: Pipe: Read failed.

2020-09-30T01:00:40.999-04:00| vmplayer| I005+

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VigorOnlineDisconnect: disconnect /vm/#035ea56fdabf547c/ via /db/connection/#a/

2020-09-30T01:00:40.999-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Unmounting VM begun.

2020-09-30T01:00:40.999-04:00| vmplayer| I005: VMDB unmount initiated for /vm/#035ea56fdabf547c/.

2020-09-30T01:00:41.005-04:00| vmplayer| I005: VigorOnlineUnmountCb: Mount state values have changed for /vm/#035ea56fdabf547c/.

2020-09-30T01:00:41.005-04:00| vmplayer| I005: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#a/'

2020-09-30T01:00:41.005-04:00| vmplayer| I005: VigorOnlineUnmountCb: Unmount complete for /vm/#035ea56fdabf547c/.

2020-09-30T01:00:41.005-04:00| vmplayer| I005: VigorOnlineUnmountCb unset Vigor path on vm unmount.

2020-09-30T01:00:41.005-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Unmounting VM complete.

2020-09-30T01:00:41.006-04:00| vmplayer| I005: /data/VM/vmware/Win10/Windows 10 x64.vmx: Reloading config state.

2020-09-30T01:00:41.012-04:00| vmplayer| I005: VMHS: Transitioned vmx/execState/val to poweredOff

2020-09-30T01:00:41.013-04:00| vigorCnx| I005: VigorOfflineGetToolsVersion: updated tools version to 2c00

2020-09-30T01:00:41.014-04:00| vmplayer| I005: vm power operation abort, error = This host supports AMD-V, but AMD-V is disabled.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ AMD-V might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (1) Verify that the BIOS/firmware settings enable AMD-V.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (2) Power-cycle the host if this BIOS/firmware setting has been changed.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (3) Power-cycle the host if you have not done so since installing VMware Player.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (4) Update the host's BIOS/firmware to the latest version.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ This host does not support "AMD RVI" hardware assisted MMU virtualization.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ VMware Player does not support the user level monitor on this host.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ Module 'MonitorMode' power on failed.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ Failed to start the virtual machine.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+  .

2020-09-30T01:00:41.031-04:00| vmplayer| I005: OnVMStateChanged: alive = 0

2020-09-30T01:00:41.031-04:00| vmplayer| I005: CUIMKS: cui::MKS::SetAttached (55C5EA472360): detach

2020-09-30T01:00:41.031-04:00| vmplayer| I005: CUIMKS: cui::MKS::OnSetAttachedCompleted (55C5EA472360)

2020-09-30T01:00:41.051-04:00| vmplayer| I005: Vix: [foundryVM.c:10412]: FoundryVMMountStateChangeCallback: remount complete, set flag, VM = /data/VM/vmware/Win10/Windows 10 x64.vmx

2020-09-30T01:00:41.052-04:00| vmplayer| I005: Vix: [foundryVMPowerOps.c:984]: FoundryVMPowerStateChangeCallback: /data/VM/vmware/Win10/Windows 10 x64.vmx, vmx/execState/val = poweredOff.

2020-09-30T01:00:41.052-04:00| vmplayer| I005: Cmd /host2/#_client/util/file/cmd/##e/op/stat/ failed: Invalid path

2020-09-30T01:00:41.053-04:00| vmplayer| I005: VMMKS::OnMKSDeviceInfoChanged: reset pipe name now in offline.

2020-09-30T01:00:41.053-04:00| vmplayer| I005: CUIMKS: Destroy cui::MKS (55C5EA472360)

2020-09-30T01:00:41.053-04:00| vmplayer| I005: CUIMKS: cui::MKS::SetAttached (55C5EA472360): detach

2020-09-30T01:00:41.053-04:00| vmplayer| I005: CUIMKS: cui::MKS::OnSetAttachedCompleted (55C5EA472360)

2020-09-30T01:00:41.053-04:00| vmplayer| I005: CUIMKS: Destroying cui::MKS (55C5EA472360) is done.

2020-09-30T01:00:41.053-04:00| vmplayer| I005: MKSWindowTrans: The current transaction 55C5EA461D40 has not been submitted.

2020-09-30T01:00:41.053-04:00| vmplayer| I005: MKSControlClient: Destroy mksControl client 55C5E990C1C0.

2020-09-30T01:00:41.053-04:00| vmplayer| I005: MKSControlClient: Disconnect is called (55C5E990C1C0) (current state 0).

2020-09-30T01:00:41.053-04:00| vmplayer| I005: MKSControlClient: Disconnect is done (55C5E990C1C0) (current state 0).

2020-09-30T01:00:41.053-04:00| vmplayer| I005: MKSControlClient: Destroying mksControl client 55C5E990C1C0 is done.

2020-09-30T01:00:41.055-04:00| vmplayer| I005: VMMgr::CloseVM: closing VM at /vm/#035ea56fdabf547c/

2020-09-30T01:00:41.065-04:00| vmplayer| I005: VMMgr::OnVMDestroyed: cleaning up after destroyed VM at /vm/#035ea56fdabf547c/

2020-09-30T01:00:41.066-04:00| vmplayer| I005: Cmd /host2/#_client/util/file/cmd/##10/op/stat/ failed: Invalid path

2020-09-30T01:00:41.073-04:00| vmplayer| I005: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Reply
0 Kudos
1 Solution

Accepted Solutions
bluefirestorm
Champion
Champion
Jump to solution

It is better to attach log files than pasting its contents. There is an "Attach" at the lower right hand side of the posting/reply box. Very long log contents pasted as text can make it difficult to navigate through the post.

Anyway, is the AMD-V or SVM or similar terminology setting enabled at the host motherboard BIOS/UEFI? From the looks of the log it looks to be disabled. So try to do what the log text is suggesting And here I am pasting parts of the log contents :smileylaugh:

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ AMD-V might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (1) Verify that the BIOS/firmware settings enable AMD-V.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (2) Power-cycle the host if this BIOS/firmware setting has been changed.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (3) Power-cycle the host if you have not done so since installing VMware Player.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (4) Update the host's BIOS/firmware to the latest version.

View solution in original post

Reply
0 Kudos
3 Replies
bluefirestorm
Champion
Champion
Jump to solution

It is better to attach log files than pasting its contents. There is an "Attach" at the lower right hand side of the posting/reply box. Very long log contents pasted as text can make it difficult to navigate through the post.

Anyway, is the AMD-V or SVM or similar terminology setting enabled at the host motherboard BIOS/UEFI? From the looks of the log it looks to be disabled. So try to do what the log text is suggesting And here I am pasting parts of the log contents :smileylaugh:

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ AMD-V might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (1) Verify that the BIOS/firmware settings enable AMD-V.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (2) Power-cycle the host if this BIOS/firmware setting has been changed.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (3) Power-cycle the host if you have not done so since installing VMware Player.

2020-09-30T01:00:41.014-04:00| vmplayer| I005+ (4) Update the host's BIOS/firmware to the latest version.

Reply
0 Kudos
avarakin
Contributor
Contributor
Jump to solution

Yes, I saw this piece in the logs and tried finding a switch in my BIOS and could not find it. I guess I need to dig deeper into it.

Reply
0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

The term might be AMD-V or SVM Mode or Secure Virtual Machine.

Here is a link to Asus FAQ

https://www.asus.com/support/FAQ/1038245/

Gigabyte boards seems to be (from a Reddit post)

M.I.T. -> Advanced Frequency Settings -> Advanced CPU Core Settings -> SVM mode -> Enabled

Anyway you can enter on a search engine

<your motherboard brand> SVM

That is how I got the to the Asus and Gigabyte results.

Reply
0 Kudos