zech02's Posts

Re: Update VM Workstation pro 16.1 to 16.2

by Contributor in VMware Workstation Pro Discussions
‎11-01-2021 12:41 AM
‎11-01-2021 12:41 AM
Ok I have cloned my VM's in different folders. Now I can work with 6.2. Thanks for the support.

Re: Update VM Workstation pro 6.1 to 6.2

by Contributor in VMware Workstation Pro Discussions
‎10-19-2021 11:57 PM
‎10-19-2021 11:57 PM
I tested with 3 VMs: three times - "Poweroff" of all VMs - each time a different VM was started, then the second and third generated this message. The commonality of all VMs is Ubuntu 20.0x and were ... See more...
I tested with 3 VMs: three times - "Poweroff" of all VMs - each time a different VM was started, then the second and third generated this message. The commonality of all VMs is Ubuntu 20.0x and were created with the same VM template. As I said with 16.1, all three VMs were running at the same time. In the meantime, I've uninstalled 16.2 and reinstalled 16.1. After the installation, I was able to use the VMs again. Now I could compare what has changed on the file system under 16.2. With version 16.2 an option "scoreboard" is activated and this option creates a file in the directory. If a second VM is started, this file appears to be accessible to the first VM. 2021-10-19T13:25:07.843Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1871, success=1 additionalError=0 2021-10-19T13:25:07.845Z In(05) vmx VMXSTATS: Successfully created statsfile: vm.scoreboard 2021-10-19T13:25:07.846Z In(05) vmx VMXSTATS: Update Product Information: VMware Workstation 16.2.0 build-18760230 Release TotalBlockSize: 64 2021-10-19T13:25:07.846Z In(05) vmx HOST Windows version 10.0, build 19043, platform 2, "" Now I am curious whether my assumption is correct!

Re: Update VM Workstation pro 16.1 to 16.2

by Contributor in VMware Workstation Pro Discussions
‎10-19-2021 07:58 AM
‎10-19-2021 07:58 AM
Excuse me -  INow  have adjusted the version number in the text.

Update VM Workstation pro 16.1 to 16.2

by Contributor in VMware Workstation Pro Discussions
‎10-19-2021 07:46 AM
‎10-19-2021 07:46 AM
Windows 10 pro - latest patches - Update VM Workstation Pro 16.1 to 16.2 After the update, I could only start one VM. When I start a second VM I get the message "Failed to start the virtual machine"... See more...
Windows 10 pro - latest patches - Update VM Workstation Pro 16.1 to 16.2 After the update, I could only start one VM. When I start a second VM I get the message "Failed to start the virtual machine". The following message is in the Vmware.log file: 2021-10-19T14:24:27.684Z In(05) vmx FILE: E:\Virtual Machines\vmware.log: rename of E:\Virtual Machines\vmware-0.log -> FileRotateByRename failed: The process cannot access the file because it is being used by another process 2021-10-19T14:24:27.698Z No(00) vmx ConfigDB: Setting floppy0.clientDevice = "FALSE" 2021-10-19T14:24:27.710Z Wa(03) vmx PowerOn 2021-10-19T14:24:27.710Z In(05) vmx VMX_PowerOn: VMX build 18760230, UI build 18760230 2021-10-19T14:24:27.710Z In(05) vmx HostWin32: WIN32 NUMA node 0, CPU mask 0x00000000000000ff 2021-10-19T14:24:27.715Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1871, success=1 additionalError=0 2021-10-19T14:24:27.717Z In(05) vmx FILE: FileRotateByRenumber: rename of vm.scoreboard -> E:\Virtual Machines/vm-2.scoreboard failed: The process cannot access the file because it is being used by another process 2021-10-19T14:24:27.717Z Wa(03) vmx FileIOCreateRetryEx: Unrecognized error code: 1224 2021-10-19T14:24:27.717Z Er(02) vmx VMXSTATS: Failed to open or create vm.scoreboard: The requested operation cannot be performed on a file with a user-mapped section open. 2021-10-19T14:24:27.717Z Er(02) vmx VMXSTATS: Failed to map, open, or create the file, vm.scoreboard. 2021-10-19T14:24:27.717Z In(05) vmx Module 'VmxStats' power on failed. 2021-10-19T14:24:27.717Z In(05) vmx VMX_PowerOn: ModuleTable_PowerOn = 0 2021-10-19T14:24:27.717Z In(05) vmx 2021-10-19T14:24:27.717Z In(05)+ vmx Power on failure messages: Failed to start the virtual machine. 2021-10-19T14:24:27.717Z In(05)+ vmx 2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0 2021-10-19T14:24:27.717Z In(05) vmx Transitioned vmx/execState/val to poweredOff 2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0 2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4244]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error 2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0 2021-10-19T14:24:27.717Z In(05) vmx Transitioned vmx/execState/val to poweredOff 2021-10-19T14:24:27.717Z In(05) vmx WQPoolFreePoll : pollIx = 3, signalHandle = 1080 2021-10-19T14:24:27.718Z In(05) vmx Vix: [mainDispatch.c:815]: VMAutomation_LateShutdown() 2021-10-19T14:24:27.718Z In(05) vmx Vix: [mainDispatch.c:770]: VMAutomationCloseListenerSocket. Closing listener socket. 2021-10-19T14:24:27.718Z In(05) vmx Flushing VMX VMDB connections 2021-10-19T14:24:27.718Z In(05) vmx VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/' 2021-10-19T14:24:27.718Z In(05) vmx VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0) 2021-10-19T14:24:27.718Z In(05) vmx VigorTransport_ServerDestroy: server destroyed. 2021-10-19T14:24:27.718Z In(05) vmx WQPoolFreePoll : pollIx = 2, signalHandle = 748 2021-10-19T14:24:27.718Z In(05) vmx WQPoolFreePoll : pollIx = 1, signalHandle = 756 2021-10-19T14:24:27.720Z In(05) vmx VMX exit (0). 2021-10-19T14:24:27.720Z In(05) vmx OBJLIB-LIB: ObjLib cleanup done. Why does a VM block all other VMs when starting? Up to 6 VMs were running in parallel before the update to 16.2. I deleted all VMs on the library and tested them with three VMs. How can I solve this problem?
Labels