Virtualbox vs VMware Player

There are many articles comparing Virtualbox and VMware products, but I could find none that would list the points important for my industrial automation tasks. So here is my list, still growing, of pros and cons of VMware Workstation Player v15.5.1 as compared to Virtualbox 6.1.4.
So far VMware Workstation Player better suits my purposes.

Pros:

  • Automatic installation for standard OS distributives.
  • Better shared folders (via Samba).
  • The command Compact Disk works and quite fast.
  • Defragment Disk command.
  • Splitting of disk images makes the archiving of VM more reliable.
  • No crashes when booting from network (e.g. virtualbox crashes when booting Kali Linux Live Gnome via netbootxyz).
  • Possible to add hard drive to a running VM (SCSI).
  • RAM is allocated at the host only when it is actually used in the guest, which allows to distribute the RAM between several guests dynamically, without restarting them.
  • Copied virtual machines are made unique automatically, no need to modify any ID in the config file.

Cons:

  • Not open source, forbidden for commercial usage.
  • Some keys (cursor arrow, Enter in the numeric keypad) don’t work over Anydesk or Teamviewer: Win10 – Anydesk/Teamviewer – Ubuntu 18 – VMware – Windows 10.
    Workaround: switch off Num Lock and use the numeric keypad.
  • Difficult to enter BIOS or boot menu. In order to delay, add to .vmx file:
    bios.bootDelay = "1000"
  • File vmem with the size of the guest’s RAM is create on host (for suspend, snapshots, add SCSI controllers etc). And these configs don’t help, neither in .vmx, nor in ~/.vmware/preferences :
    prefvmx.minVmMemPct = "100"
    MemTrimRate = "0"
    mainMem.useNamedFile = "FALSE"
    sched.mem.pshare.enable = "FALSE"
    prefvmx.useRecommendedLockedMemSize = "TRUE"
    
  • Renaming VM is more difficult: files need to be renamed manually.
  • The keyboard shortcuts Super + cursor arrows do not work in Ubuntu VM under Ubuntu host.

Leave a Reply

Your email address will not be published. Required fields are marked *