Vmx hacks - Revision history

Wila: Player - disable mitigations

2022-07-18T10:10:55Z

Player - disable mitigations

← Older revision		Revision as of 12:10, 18 July 2022
Line 235:		Line 235:

	More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]		More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

			=== VMware Player ===

			==== Disable mitigations ====

			A message about disabling side channel mitigations shows up only when the ULM is used instead of the ring 0 VMM as the hypervisor monitor.

			That means the Windows host has been detected to have Hyper-V enabled.

			https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html

			There is no advanced options in VMware Workstation Player.

			To disable the side channel mitigation, shut down the VM and add the following to the VM vmx configuration file.

			ulm.disableMitigations = "TRUE"

			from: [https://communities.vmware.com/t5/VMware-Workstation-Player/Poor-performance-after-update-with-message-about-side-channel/m-p/2811455/highlight/true#M35855 Poor performance after update with message about side channel mitigation]

	=== Fusion ===		=== Fusion ===

Wila: /* Linux Host - switch back from Vulkan to X11 */

2022-03-19T10:30:24Z

Linux Host - switch back from Vulkan to X11

← Older revision		Revision as of 12:30, 19 March 2022
Line 200:		Line 200:

	Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.		Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

			There's another switch to use the openGL renderer instead of Vulkan:

			mks.enableVulkanRenderer = "FALSE"
			mks.enableGLRenderer = "TRUE"

			and a switch to allow the Vulkan rendered use unsupported devices:

			mks.vk.allowUnsupportedDevices = "TRUE"

			There's even a way to force your VM to use a specific GPU, such as the discrete GPU instead of the integrated GPU.. if your host has both.

			mks.forceDiscreteGPU = "TRUE"

			See the tips from BlueFireStorm here: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-cannot-connect-to-the-virtual-machine-Vmware/m-p/2899481/highlight/true#M174703 VMware Workstation cannot connect to the virtual machine]

	==== Dark Mode ====		==== Dark Mode ====

Wila: /* Any platform */

2021-12-08T01:41:26Z

Any platform

← Older revision		Revision as of 03:41, 8 December 2021
Line 426:		Line 426:

	=== Any platform ===		=== Any platform ===

			==== Disable scoreboard files ====

			In VMware Fusion 12.2 and Workstation 16.2 new files have been introduced for keeping some sort of statistics.

			These are called scoreboard files.

			You can disable that feature.

			vmx.scoreboard.enabled = "FALSE"

			See: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-16-2-0-and-scoreboard-files-What-it-is/m-p/2881784/highlight/true#M172906 Suggestion by DaveP on VMware Workstation 16.2.0 and .scoreboard files. What is it?]

	==== Slow down time in guest ====		==== Slow down time in guest ====

Wila: Note about multiple GPU's when having issues with Vulkan

2021-11-17T12:07:24Z

Note about multiple GPU's when having issues with Vulkan

← Older revision		Revision as of 14:07, 17 November 2021
Line 198:		Line 198:

	Has a great explanation on the difference by banackm		Has a great explanation on the difference by banackm

			Beware that if you have this issue -and your host has more than one GPU- that it also might be because the wrong GPU was selected for Vulkan.

	==== Dark Mode ====		==== Dark Mode ====

Wila: Disable all USB devices

2021-11-17T12:05:09Z

Disable all USB devices

← Older revision		Revision as of 14:05, 17 November 2021
Line 199:		Line 199:
	Has a great explanation on the difference by banackm		Has a great explanation on the difference by banackm

	=== Dark Mode ===		==== Dark Mode ====

	In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.		In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.
Line 206:		Line 206:

	from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]		from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

			==== All USB devices are disabled ====

			Check your .vmx file for the following line:

			usb.restrictions.defaultAllow = "FALSE"

			If it has this then remove that line and try again.

			It seems that this line is automatically added for Workstation/Player 16.2.x when using "Easy Setup".

			More details here: [https://communities.vmware.com/t5/VMware-Workstation-Player/All-USB-devices-are-greyed-out/m-p/2878067#M37999 All USB devices are greyed out]

	=== Fusion ===		=== Fusion ===

Wila: /* Linux Host - switch back from Vulkan to X11 */

2021-11-12T10:24:20Z

Linux Host - switch back from Vulkan to X11

← Older revision		Revision as of 12:24, 12 November 2021
Line 185:		Line 185:

	==== Linux Host - switch back from Vulkan to X11 ====		==== Linux Host - switch back from Vulkan to X11 ====
	Workstation 16.x and higher		Workstation 16.2.0 and higher

	Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:		Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

Wila: /* Change thumbnail speed */

2021-11-12T10:21:06Z

Change thumbnail speed

← Older revision		Revision as of 12:21, 12 November 2021
Line 183:		Line 183:

	from: https://communities.vmware.com/message/2807350#2807350		from: https://communities.vmware.com/message/2807350#2807350

			==== Linux Host - switch back from Vulkan to X11 ====
			Workstation 16.x and higher

			Add to .vmx if changing for one VM, or ~/.vmware/config if you want to change this systemwide:

			mks.enableX11Presentation=TRUE
			mks.enableVulkanPresentation=FALSE

			That will force us to draw the window using X11 instead of Vulkan, which is normally less performant, but might work better on some setups?


			from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-16-2-1-Display-3D-acceleration-not-working-Windows-10/m-p/2877574#M172414 VMware 16.2.1 Display 3D acceleration not working Windows 10]

			Has a great explanation on the difference by banackm

	=== Dark Mode ===		=== Dark Mode ===

Wila: Add Dark Mode setting

2021-10-29T09:07:16Z

Add Dark Mode setting

← Older revision		Revision as of 11:07, 29 October 2021
Line 183:		Line 183:

	from: https://communities.vmware.com/message/2807350#2807350		from: https://communities.vmware.com/message/2807350#2807350

			=== Dark Mode ===

			In Workstation 16.2 Dark Mode had disappeared by accident, it was discovered that adding the following setting to the preferences.ini file makes it re-appear.

			wsFeatureDarkModeSupported = "TRUE"

			from: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-Workstation-16-2-dark-mode/m-p/2874723/highlight/true#M172025 forum user mrdow2000]

	=== Fusion ===		=== Fusion ===

Wila: typo

2021-10-07T16:23:25Z

typo

← Older revision		Revision as of 18:23, 7 October 2021
Line 431:		Line 431:
	If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).		If this line is not present, VMware Workstation will use the default graphic card of the Windows host system. This line is useful if the system has two graphic cards from two different vendors that are simultaneously active on the host machine (example: Intel integrated graphics in the CPU and a discrete graphics card from Nvidia or AMD).

	==== ~~ReflecHost~~ ====		==== ReflectHost ====
	Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]		Courtesy @bluefirestorm at [https://communities.vmware.com/message/2812499#2812499 setting *.vmx]

Wila: /* Open file with host OS application */

2021-04-21T14:48:13Z

Open file with host OS application

← Older revision		Revision as of 16:48, 21 April 2021
Line 368:		Line 368:
	proxyApps.publishToGuest = "TRUE"		proxyApps.publishToGuest = "TRUE"

	See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/~~2841051~~ Has there ever been a solution to opening a host application from a guest OS?]		See also: [https://communities.vmware.com/t5/VMware-Workstation-Pro/Has-there-ever-been-a-solution-to-opening-a-host-application/m-p/2841711/highlight/true#M169663 Has there ever been a solution to opening a host application from a guest OS?]

	==== Pass OS X host serial number ====		==== Pass OS X host serial number ====