The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,414 other followers

Archive for the ‘Fusion’ Category

Mac OS X beyond Yosemite: Ctrl-Click to add/remove an item from a selection fails in Windows on VMware Fusion

Posted by jpluimers on 2018/08/03

Somewhere after Yosemite, braindead Mac OS X forcibly maps “Ctrl+Click” to right-click. In past versions, you could disable but those days have gone.

This means that inside Windows on VMware Fusion, you cannot add/remove items to/from a selection any more (for instance in the Windows Explorer).

Various workarounds turned up in my Google Search, but only this one works:

Holding down CTRL + OPTION together and LEFT CLICKING will do this.

Source: [WayBackvmware fusion – How to use the control key in VM Ware? – Super User



Posted in Apple, Fusion, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, MacMini, macOS 10.12 Sierra, OS X 10.10 Yosemite, OS X 10.11 El Capitan, OS X 10.9 Mavericks, Power User, Virtualization, VMware | Leave a Comment »

When your Windows 8.1 mouse cursor is invisible in the screen center on VMware Fusion

Posted by jpluimers on 2017/10/02

Remove the

Remove the “VMware Pointing Device” using “devmgmt.msc”

Somehow I have it happen every now and then on Windows (usually 8.1 x64) VMs running inside a VMware (usually Fusion) that the mouse cursor is stuck.

VMware Tools were already at the latest version and a plain reboot didn’t help.

It doesn’t matter if I was running full screen or Windows and altering these mouse settings did not change the behaviour:

  • Enable pointer shadow
  • Display pointer trails (long or short: does not matter)

I did enable Show location of pointer when I press the CTRL key which then indicated the mouse pointer was static at the screen center.

The only thing to get the mouse respond to mouse movement were these steps:

  1. Start Device Manager using devmgmt.msc
  2. Switch to the Devices by Connection view from the View menu
  3. Open these sub-trees:
    1. Your machine in this case my machine W81ENTX64VS2015
    2. ACPI x64-based PC
    3. Microsoft ACPI-Compliant System
    4. PCI Bus
    5. Intel 82371AB/EB PCI to ISA bridge (ISA mode)
  4. Now delete the VMware Pointing Device
  5. Reboot after Device Manager ask you to do so

After that my mouse cursor works fine.

Just in case you bump into a similar thing, but the above steps don’t help, here are some links with different steps that might work in your situation:

Read the rest of this entry »

Posted in Fusion, Power User, Virtualization, VMware, Windows, Windows 8.1 | Leave a Comment »

use vmrun – via How do I find the IP address of a virtual machine using VMware Fusion? – Super User

Posted by jpluimers on 2017/04/20

Note this works only when the VMs have VMware Tools installed (more on that below):

VMWare provides, not surprisingly, a built in tool for this, vmrun. It’s under /Applications/VMware although it has moved around in other Fusion releases a bit.

🍺 vmrun list Total running VMs: 1 .docker/machine/machines/myvm.vmx
🍺 vmrun getGuestIPAddress ~/.docker/machine/machines/myvm.vmx

via: How do I find the IP address of a virtual machine using VMware Fusion? – Super User [WayBack]

vmrun [WayBack] is barely documented and most of is in PDF of which this is the most recent I could find: [WayBack]

Based on the above path, I added this to my ~/.bash_profile file:

alias vmrun='/Applications/VMware\'
alias vmrun-list-running-VMs='vmrun list | grep vmx'
  vmrun-list-running-VMs | while read line ; do echo $line && vmrun getGuestIPAddress $line; done

Now I can do this:

$ vmrun-list-ipv4-of-running-VMs
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
$ vmrun-list-ipv4-of-running-VMs
Error: Unable to get the IP address
$ vmrun-list-ipv4-of-running-VMs
Error: Unable to get the IP address
$ vmrun-list-ipv4-of-running-VMs
$ vmrun-list-ipv4-of-running-VMs

These are the messages I observed:

Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address

The first one means a machine is running but has no VMware Tools installed. For an OpenSuSE machine you can install it with zypper install open-vm-tools, for other Linux systems read VMware Tools auf Ubuntu, Mint, CentOS oder openSUSE installieren | ITrig [WayBack]

Some more examples of vmrun for VMware Fusion are at Control VMware Fusion from the Command Line | James Reuben Knowles [WayBack]


Posted in *nix, bash, Development, Fusion, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed, Virtualization, VMware | Leave a Comment »

SysInternals sdelete: zero wipe free space is called -z instead of -c

Posted by jpluimers on 2016/09/20

In the 2009 past, sdelete used the -c parameter to zero wipe clean a hard drive and -z would clean it with a random pattern.

That has changed. Somewhere along the lines, -c and -z has swapped meaning which I didn’t notice.

This resulted in many of my virtual machines image backups were a lot larger than they needed to be.

The reason is that now:

  • -c does a clean free space with a random DoD conformant pattern (which does not compress well)
  • -z writes zeros in the free space

Incidently, -c is a lot slower than -z as well.

TL;DR: use this command

sdelete -z C:

Where C: is the drive to zero clean the free space.


Posted in Batch-Files, Development, Fusion, Hyper-V, Power User, Proxmox, Scripting, sdelete, Software Development, SysInternals, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation, Windows | Leave a Comment »

Solving VMware Fusion 6 and Windows 7 VM performance issues |

Posted by jpluimers on 2016/03/21

Add these entries to your .vmx file:

MemTrimRate = "0"
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "TRUE"

Works in VMware Fusion 5, 6, and 7. Probably 8 too.


via Solving VMware Fusion 6 and Windows 7 VM performance issues |

Posted in Fusion, Power User, Virtualization, VMware | 2 Comments »

%d bloggers like this: