JessieZhang's Posts

@randybarth51  Thanks for reporting this issue. We reproduced this issue and sent the issue to the development team for investigation. Here is an interim workaround: 1. Open the macOS Big Sur VM's... See more...
@randybarth51  Thanks for reporting this issue. We reproduced this issue and sent the issue to the development team for investigation. Here is an interim workaround: 1. Open the macOS Big Sur VM's Advanced Settings, enable "Remote display over VNC" checkbox, set a VNC password and a VNC port 2. From another physical Mac machine, activate Finder, select Go > Connect to Server menu, input the following to connect to the macOS Big Sur VM by VNC: vnc://<the IP of the mac host where the macOS Big Sur VM is stored>:<VNC port set in step 1> 3. Click Connect button, when prompted for password, enter the VNC password set in step 1
I guess your question is that why the "Clean Up Virtual Machine" button is disabled for your VM. According to https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47... See more...
I guess your question is that why the "Clean Up Virtual Machine" button is disabled for your VM. According to https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9, the "Clean Up Virtual Machine" button can perform two functions: 1. For Windows VM, if you delete data inside the VM, then shut down the VM, the VM cannot release the disk space occupied by the deleted data. So you need to manually click the "Clean Up Virtual Machine" button to have the VM release that disk space. The "Clean Up Virtual Machine" button is always enabled for powered-off Windows VM 2. Fo all VM (Linux/Mac/Windows VM), if your previously executed snapshot operations on the VM causes any unconsolidated snapshot files left, clicking the "Clean Up Virtual Machine" button can consolidate these snapshot files. For Linux/Mac VM, if the unconsolidated snapshot files exists, the "Clean Up Virtual Machine" button will be enabled, if the unconsolidated snapshot files do NOT exist, the button will be disabled. From the above, you can see that the status of the "Clean Up Virtual Machine" button depends on the Guest OS type and existence of unconsolidated snapshot files. For your case, I guess your VM is not a Windows VM and there is no unconsolidated snapshot files in you VM bundle, so the "Clean Up Virtual Machine" button is disabled
@eliomartinezb, I don't quite understand your problem, could you please provide more details: 1) What are your steps? Do you mean the "Clean Up Virtual Machine" button on General Setting is disable... See more...
@eliomartinezb, I don't quite understand your problem, could you please provide more details: 1) What are your steps? Do you mean the "Clean Up Virtual Machine" button on General Setting is disabled for your VM? 2) What is the OS installed in your VM? According to https://docs.vmware.com/en/VMware-Fusion/12/com.vmware.fusion.using.doc/GUID-6BB29187-F47F-41D1-AD92-1754036DACD9.html#GUID-6BB29187-F47F-41D1-AD92-1754036DACD9, the "Clean Up Virtual Machine" feature works only for Windows VM
Pascal​, That seems to be a permission issue. Could you please provide more information? 1) What happens if you launch Fusion, then start up and shut down the same VM? Does the same error mes... See more...
Pascal​, That seems to be a permission issue. Could you please provide more information? 1) What happens if you launch Fusion, then start up and shut down the same VM? Does the same error message show up? 2) Open a Terminal window, run below command to see if there is any permission issue with the vmx file     ls -all /Users/pascal/Documents/Virtal Machine/Win 10 x64 iMac 2017.vmwarevm
PascalG​, Do not use 'sudo' in AppleScript, the permission can be escalated by using the following patthern:     do shell script "command" user name "username" password "pass" with administra... See more...
PascalG​, Do not use 'sudo' in AppleScript, the permission can be escalated by using the following patthern:     do shell script "command" user name "username" password "pass" with administrator privileges You can experiment by running the following lines in Apple Script: 1) do shell script "cat /etc/sudoers" 2) do shell script "cat /etc/sudoers" user name "username" password "pass" with administrator privileges My test with using vmrun in AppleScript works: do shell script "'/Applications/VMware Fusion.app/Contents/Library/vmrun' start '/Volumes/10.14/Users/Shared/Windows 10.vmwarevm/Windows 10 x64.vmx'" user name "username" password "pass" with administrator privileges
macadmin​, I could not reproduce this issue on my machine, so could you please provide more information so that we can identify what special configuration or steps cause this problem in your e... See more...
macadmin​, I could not reproduce this issue on my machine, so could you please provide more information so that we can identify what special configuration or steps cause this problem in your environment? From your description, I see that your machine is a MacBook Pro 13" (Late 2016 version) and you are using an Apple Bluetooth Magic Keyboard when this issue happens, does this issue happen when you use the built-in keyboard on your MacBook Pro? Does this issue happen only on the specific Windows 10 virtual machine or on all of your virtual machine other than the Windows 10 virtual machine?
macdamit​, It sounds like a problem with Fusion 10, but the problem had been solved since Fusion 10.1.2, see the first resolved issue in Fusion 10.1.2 release notes (VMware Fusion 10.1.2 Relea... See more...
macdamit​, It sounds like a problem with Fusion 10, but the problem had been solved since Fusion 10.1.2, see the first resolved issue in Fusion 10.1.2 release notes (VMware Fusion 10.1.2 Release Notes ). It is weird to know that the problem happens again in your environment. Please have a try with below steps to see if that can help solve your problem: Step 1: Quit Fusion Step 2: Create a file and name it as "config", make sure the file has no extension name Step 3: Add this line to the config file:         mks.keyboard.setHostLEDs="FALSE" Step 4: Copy the config file to ~/Library/Preferences/VMware Fusion/ folder Step 5: Launch Fusion and see if your problem still persists
Ted365​, Could you please check if VMware Tools is installed and running in your virtual machine and provide the vmware.log in '/Volumes/Promise Pegasus/Virtual Machines/Windows 10 x64 4.vmwa... See more...
Ted365​, Could you please check if VMware Tools is installed and running in your virtual machine and provide the vmware.log in '/Volumes/Promise Pegasus/Virtual Machines/Windows 10 x64 4.vmwarevm'?
There is a known issue that Windows 10 1903/19H1 build 18362 is stuck in the startup process if the VM's "Enable IOMMU in this virtual machine" settings is turned on, please see VMware Knowledge ... See more...
There is a known issue that Windows 10 1903/19H1 build 18362 is stuck in the startup process if the VM's "Enable IOMMU in this virtual machine" settings is turned on, please see VMware Knowledge Base . Is the "Enable IOMMU in this virtual machine" checkbox on your VM's "Processor & Memory" setting checked. If yes, please see if your VM can power on after unchecking the checkbox.
DirkToo​, This issue is fixed by Apple side, the panic can be observed for any Mac OS install image < 10.13.4, but the panic should be gone if you use a macOS install image which is >=10.13.4.... See more...
DirkToo​, This issue is fixed by Apple side, the panic can be observed for any Mac OS install image < 10.13.4, but the panic should be gone if you use a macOS install image which is >=10.13.4.
tjsoftworks​, This is a known issue in current Fusion release that we are tracking internally. We are very sorry for the inconvenience caused by this issue to you.
coogle​, Based on your description: "Now when I try vmrun enableSharedFolders for the .VMX it just hangs and seems to do nothing at all until I CTRL-C out of it?" My first thought is that y... See more...
coogle​, Based on your description: "Now when I try vmrun enableSharedFolders for the .VMX it just hangs and seems to do nothing at all until I CTRL-C out of it?" My first thought is that your tools might not be installed correctly. On my side, if tools is not installed in a 64bit Ubuntu 16.04.5 Desktop VM, when I run "vmrun enableSharedFolders" command on the VM, the command returns nothing until 5 minutes of timeout, that is, the command gave out below error after 5 minutes: "Error: The VMware Tools are not running in the virtual machine: /Users/Shared/Ubuntu 64-bit 16.04.5.vmwarevm/Ubuntu 64-bit 16.04.5.vmx" Could you please try running the command again on your side and wait 5 minutes to see if the command returns the same error on your side? If yes, please try re-installing VMware Tools.
donmontalvo, If you used VMware Fusion.app/Contents/Library/Deploy VMware Fusion.mpkg to deploy Fusion and any VM, the deployment will create /Users/Shared/Virtual Machines folder with below p... See more...
donmontalvo, If you used VMware Fusion.app/Contents/Library/Deploy VMware Fusion.mpkg to deploy Fusion and any VM, the deployment will create /Users/Shared/Virtual Machines folder with below permission:      ls -le /Users/Shared/      drwxr-xr-x  root wheel  Virtual Machines And the VM deployed into the "/Users/Shared/Virtual Machines" folder has below permission:     ls -le /Users/Shared/Virtual Machines/     drwxrwxrwx root wheel  <deployed VM bundle>
mortenjensen01​, There is a problem with the configuration of your VM Windows10-MBP2012.vmwarevm⁩, I suppose this VM is a 64bit Windows 10 VM, but I saw guestOS = "windows7" in the vmx of the ... See more...
mortenjensen01​, There is a problem with the configuration of your VM Windows10-MBP2012.vmwarevm⁩, I suppose this VM is a 64bit Windows 10 VM, but I saw guestOS = "windows7" in the vmx of the VM. So you configured your VM as a 32bit Windows 7 VM, while actually it is a 64bit Windows 10 VM. I am not sure if this causes the BSOD. But please give a try to correct the OS version by opening the VM' Settings => click General button => click the OS version field and change it's value to Windows 10 x64.
jaqsoo​, This is a behavior change after upgrading Fusion from version 10 to version 11. Sorry it makes thing that originally worked in your work environment no longer work. When Fusion 11 ... See more...
jaqsoo​, This is a behavior change after upgrading Fusion from version 10 to version 11. Sorry it makes thing that originally worked in your work environment no longer work. When Fusion 11 is launched, if you select a VM in VM Library or open Settings/Snapshot for a VM, there will be a vmx.lck file created inside the VM bundle. When the vmx.lck file exists, 'vmrun start vmx' without 'nogui' argument can run successfully, but 'vmrun start vmx' with 'nogui' argument fails to run with below message: A file access error occurred on the host or guest operating system To work around this issue, please make sure there is no .vmx.lck inside vm bundle when you run 'vmrun start' with nogui argument. That is: either Fusion is not launched or Fusion is launched, but the VM is not selected and does not have any window (settings, snapshot) open.
MoonMonkey6​, Inside the Sierra VM, If you click the "System Report" button on the "About this Mac" dialog to open the System Information, you can see ee below information under the "Hardware ... See more...
MoonMonkey6​, Inside the Sierra VM, If you click the "System Report" button on the "About this Mac" dialog to open the System Information, you can see ee below information under the "Hardware Overview":    Number of Processors: 2    Total Number of Cores: 6 That means the Sierra VM is configured with 2 multi-core processors, each processor has 3 cores, so that matches your hardware configuration on the VM. For the crash issue you mentioned, to help us diagnose the issue, could you please reproduce the vmx crash, then click Fusion menu "Help" > "Collect Support Information" to collect logs? Thanks
seanhig​ Sorry that such problem appears with Fusion. Could you please try removing below file and see if the issue still happens ~/Library/Preferences/com.apple.HIToolbox.plist
JohnD0406​, Could you please collect logs right after your virtual machine or Fusion crashes? You can select Fusion menu "Help"> "Collect Support Information" to collect all of the logs.
Hi jp4tey​ Does that problem still persist if you shut down your Mac host and start up it again? If yes, could you please provide Fusion support bundle which can be created by selecting Fus... See more...
Hi jp4tey​ Does that problem still persist if you shut down your Mac host and start up it again? If yes, could you please provide Fusion support bundle which can be created by selecting Fusion menu "Help" > "Collect Support Information"?
Hi plasticphyte​, If Fusion shows the "Application cannot run correctly" message every time you launch Fusion, it is very likely Fusion that you installed is not in a good state to work. Could... See more...
Hi plasticphyte​, If Fusion shows the "Application cannot run correctly" message every time you launch Fusion, it is very likely Fusion that you installed is not in a good state to work. Could you please confirm if your VM can power on properly in Fusion: 1) If you see this message and your VM cannot start up, please follow the text suggested by the message to set 'App Store and identified developers' in Security & Privacy system preferences and re-download Fusion 11 install image 2) If you see this message and your VM can start up properly, that should be a problem with Fusion. Please help collect Fusion UI log from ~/Library/Logs/VMware Fusion/vmware-vmfusion.log. Thanks